)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"cbc5e341baf6440889f6fcf5dfb2beb0d35a65c0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"974f673a_b5f7a21b","updated":"2025-09-10 21:12:12.000000000","message":"@kajinamit@oss.nttdata.com","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":32919,"name":"kiran pawar","display_name":"Kiran Pawar","email":"kinpaa@gmail.com","username":"kpdev"},"change_message_id":"89ad1804370536a22404af0ea20974d5d4733995","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e5663565_0150fdb8","updated":"2025-09-12 04:57:24.000000000","message":"Hi @saikumar1016@gmail.com\nCan you please test this change applying on latest master ? Just share create NFS would suffice.","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":36179,"name":"Saikumar Pulluri","display_name":"Saikumar Pulluri","email":"saikumar1016@gmail.com","username":"pulluri"},"change_message_id":"1b3f0c09f6a373e4ad6ac46aa0478e6fac5c96f6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"93a3e370_016de623","updated":"2025-09-12 06:05:49.000000000","message":"Saikumar Pulluri\nPatchset 7\nSep 09\nTested the share encryption workflow by cherry-picking the changes https://review.opendev.org/c/openstack/manila/+/959104.\n\nDeployed latest DevStack\nCherry picked the changes from 959104\nConfigure all the required stuff required to execute encrypted share creation workflow\nRestart manila services\nCreate all OpenStack necessary things like share-network, keystore...etc as needed for share creation.\nExecute share encryption workflow\nTest below encrypted share creation workflows and I don\u0027t see any regression due to 959104 changes.\n\nNFS ZAPI\nCreate share\nDelete share\nDelete share server\nNFS REST\nCreate share\nDelete share\nDelete share server\nCIFS ZAPI\nCreate share\nDelete share\nDelete share server\nAs mentioned in last sync-up meeting, CIFS REST workflow has an issue and will come back with a triage soon, will have a bug raised if needed according to the RCA.","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":36179,"name":"Saikumar Pulluri","display_name":"Saikumar Pulluri","email":"saikumar1016@gmail.com","username":"pulluri"},"change_message_id":"1b3f0c09f6a373e4ad6ac46aa0478e6fac5c96f6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c8495d6d_1cd81da8","updated":"2025-09-12 06:05:49.000000000","message":"Tested !! \n\n1.Took latest master code, checked out the code from https://review.opendev.org/c/openstack/manila/+/960380\n2.Restarted manila services\n3.Configure all the required stuff required to execute encrypted share creation workflow\n4.Restart manila services\n5.Create all OpenStack necessary things like share-network, keystore...etc as needed for share creation.\n6.Execute share encryption workflow\n\nTested below encrypted share creation workflows and I don\u0027t see any regression due to 96030 changes.\n\n1.NFS ZAPI\n-Create share\n-Delete share\n-Delete share server\n2.NFS REST\n-Create share\n-Delete share\n-Delete share server\n3.CIFS ZAPI\n-Create share\n-Delete share\n-Delete share server\n\nAs mentioned in last sync-up meeting, CIFS REST workflow has an issue and will come back with a triage soon,\nwill have a bug raised if needed according to the RCA.\n\nCopied all the testing info here: https://paste.opendev.org/show/biv4vOWRJ9wqNTGwmviH/\n\nThanks!!","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":36179,"name":"Saikumar Pulluri","display_name":"Saikumar Pulluri","email":"saikumar1016@gmail.com","username":"pulluri"},"change_message_id":"1b3f0c09f6a373e4ad6ac46aa0478e6fac5c96f6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a25e2661_7b43d7fa","updated":"2025-09-12 06:05:49.000000000","message":"Tested the share encryption workflow by cherry-picking the changes https://review.opendev.org/c/openstack/manila/+/959104.\n\nDeployed latest DevStack\nCherry picked the changes from 959104\nConfigure all the required stuff required to execute encrypted share creation workflow\nRestart manila services\nCreate all OpenStack necessary things like share-network, keystore...etc as needed for share creation.\nExecute share encryption workflow\nTest below encrypted share creation workflows and I don\u0027t see any regression due to 959104 changes.\n\nNFS ZAPI\nCreate share\nDelete share\nDelete share server\nNFS REST\nCreate share\nDelete share\nDelete share server\nCIFS ZAPI\nCreate share\nDelete share\nDelete share server\nAs mentioned in last sync-up meeting, CIFS REST workflow has an issue and will come back with a triage soon, will have a bug raised if needed according to the RCA.","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":36179,"name":"Saikumar Pulluri","display_name":"Saikumar Pulluri","email":"saikumar1016@gmail.com","username":"pulluri"},"change_message_id":"71c0fa165adb86e93f41f74e8d92c5657fb94733","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ee1123d5_08029ea6","in_reply_to":"c8495d6d_1cd81da8","updated":"2025-09-12 06:09:28.000000000","message":"Please ignore the first 2 comments of testing info and refer only the last one.","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":36179,"name":"Saikumar Pulluri","display_name":"Saikumar Pulluri","email":"saikumar1016@gmail.com","username":"pulluri"},"change_message_id":"ed82d6201363399f699ced7131fb6ca332040966","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b32eb6fa_d8fccaec","in_reply_to":"ee1123d5_08029ea6","updated":"2025-09-12 06:10:38.000000000","message":"I meant refer only this one, which I replied to now! Apologies.","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"}],"manila/keymgr/barbican.py":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"cbc5e341baf6440889f6fcf5dfb2beb0d35a65c0","unresolved":true,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"BARBICAN_OPTS \u003d ["},{"line_number":41,"context_line":"    cfg.StrOpt(\u0027region_name\u0027,"},{"line_number":42,"context_line":"               help\u003d\u0027Region name for connecting to keystone for \u0027"},{"line_number":43,"context_line":"                    \u0027application credential management.\u0027),"},{"line_number":44,"context_line":"]"}],"source_content_type":"text/x-python","patch_set":1,"id":"881123c3_51cd54b6","line":41,"range":{"start_line":41,"start_character":16,"end_line":41,"end_character":27},"updated":"2025-09-10 21:12:12.000000000","message":"Tehre\u0027s a config opt called \"barbican_region_name\": \n\nhttps://opendev.org/openstack/castellan/src/commit/088cf8f40504bfea111f6a01eeced12f4f4cfbbb/castellan/key_manager/barbican_key_manager.py#L79-L81\n\nhttps://zuul.opendev.org/t/openstack/build/190eda8449684cc5abbd65c043fe1d32/log/manila.conf.sample#2490-2491\n\nWould this be equivalent?","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"f9ad6d8caa43d52a598defbbf7ed161905d22429","unresolved":true,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"BARBICAN_OPTS \u003d ["},{"line_number":41,"context_line":"    cfg.StrOpt(\u0027region_name\u0027,"},{"line_number":42,"context_line":"               help\u003d\u0027Region name for connecting to keystone for \u0027"},{"line_number":43,"context_line":"                    \u0027application credential management.\u0027),"},{"line_number":44,"context_line":"]"}],"source_content_type":"text/x-python","patch_set":1,"id":"9b4aa93c_3c7e2139","line":41,"range":{"start_line":41,"start_character":16,"end_line":41,"end_character":27},"in_reply_to":"26ddf6fb_22bd32dd","updated":"2025-09-11 05:10:14.000000000","message":"Hmm, ideally those would be the same?\n\nI\u0027ve no objections to sticking to the conventions around this.. just confused if they are different, and what use case that would solve","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"35ec44b65c473ef1d6751b8f95741e6deb3a2601","unresolved":true,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"BARBICAN_OPTS \u003d ["},{"line_number":41,"context_line":"    cfg.StrOpt(\u0027region_name\u0027,"},{"line_number":42,"context_line":"               help\u003d\u0027Region name for connecting to keystone for \u0027"},{"line_number":43,"context_line":"                    \u0027application credential management.\u0027),"},{"line_number":44,"context_line":"]"}],"source_content_type":"text/x-python","patch_set":1,"id":"26ddf6fb_22bd32dd","line":41,"range":{"start_line":41,"start_character":16,"end_line":41,"end_character":27},"in_reply_to":"881123c3_51cd54b6","updated":"2025-09-11 03:12:09.000000000","message":"No.\n\nbarbican_region_name determine the region of barbican endpoint while this region_name is used to determine the region of keystone endpoint used for application credential requests.","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"8059192748108c0857966e730dd0d4c3ce4ce293","unresolved":true,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"BARBICAN_OPTS \u003d ["},{"line_number":41,"context_line":"    cfg.StrOpt(\u0027region_name\u0027,"},{"line_number":42,"context_line":"               help\u003d\u0027Region name for connecting to keystone for \u0027"},{"line_number":43,"context_line":"                    \u0027application credential management.\u0027),"},{"line_number":44,"context_line":"]"}],"source_content_type":"text/x-python","patch_set":1,"id":"908f707e_72133475","line":41,"range":{"start_line":41,"start_character":16,"end_line":41,"end_character":27},"in_reply_to":"9b4aa93c_3c7e2139","updated":"2025-09-11 09:06:52.000000000","message":"I\u0027ve not seen this actually but I heard some users aim to have keystone in only core regions while the other services in multiple regions to avoid distributing auth info, and in that case you may want to use different regions for keystone and barbican.\n\nMaybe we can split keystoneauth options for keystone api access to a different section (I initially tried it but was not too sure about the appropriate section name and dropped that idea)","commit_id":"202621390100ed4e2262b92c6d46d78830d6a5bb"}]}