)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"d04a1404b84c8e46700938884416cec313ea03f7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fdee5e7b_15ff00d4","updated":"2022-06-06 21:38:37.000000000","message":"The TC is making an effort to get operator feedback at the summit this week; it\u0027s possible that the community goal will be revised, which will cascade into a major revision of this spec.","commit_id":"8ec7213370f1d1b49c2181a1da9257f8514ac77a"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"728ba545d87ebba633bf0994003d2ae232bfd91b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"927f3c20_f2cdd853","updated":"2022-05-31 10:36:11.000000000","message":"looks good, one point missing regarding a volume (project scoped) containing attribute host (system scoped) and the spec should be moved to Zed directory.","commit_id":"8ec7213370f1d1b49c2181a1da9257f8514ac77a"}],"specs/yoga/s-rbac-ready.rst":[{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"728ba545d87ebba633bf0994003d2ae232bfd91b","unresolved":true,"context_lines":[{"line_number":1,"context_line":".."},{"line_number":2,"context_line":" This work is licensed under a Creative Commons Attribution 3.0 Unported"},{"line_number":3,"context_line":" License."},{"line_number":4,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"132f71e4_660c1a5c","line":1,"updated":"2022-05-31 10:36:11.000000000","message":"please change the directory from specs/yoga/s-rbac-ready.rst to specs/zed/s-rbac-ready.rst","commit_id":"8ec7213370f1d1b49c2181a1da9257f8514ac77a"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"728ba545d87ebba633bf0994003d2ae232bfd91b","unresolved":true,"context_lines":[{"line_number":57,"context_line":"how the policy changes made during the Xena cycle would be continued into"},{"line_number":58,"context_line":"Yoga.  Unfortunately, however, as services have begun implementing Consistent"},{"line_number":59,"context_line":"and Secure RBAC, some problems in the initial proposal have been identified,"},{"line_number":60,"context_line":"resulting in a direction change for the effort [2]_.  This means that the"},{"line_number":61,"context_line":"above-mentioned strategy for cinder in the Yoga cycle [3]_ must be completely"},{"line_number":62,"context_line":"revised."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"The direction change affects cinder in the following ways:"},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"431ff19f_0e4c3632","line":62,"range":{"start_line":60,"start_character":54,"end_line":62,"end_character":8},"updated":"2022-05-31 10:36:11.000000000","message":"I\u0027m confused here, does this mean\n1) the strategies/work items discussed during the yoga cycle should be revised in Zed\n2) we should revise the previously discussed strategies in the yoga cycle\n\n1 makes sense but 2 doesn\u0027t but again this spec was proposed for yoga and now we will repropose for zed without this line changing so not sure","commit_id":"8ec7213370f1d1b49c2181a1da9257f8514ac77a"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"728ba545d87ebba633bf0994003d2ae232bfd91b","unresolved":true,"context_lines":[{"line_number":94,"context_line":"  * The \"project-member\" and \"project-reader\" actions will likely be"},{"line_number":95,"context_line":"    unchanged from Yoga, though they will be explicitly \"project-scoped\""},{"line_number":96,"context_line":"    in Zed."},{"line_number":97,"context_line":"  * There will be some multiple scoped actions.  Both system- and project-"},{"line_number":98,"context_line":"    personas should be able to list volume types, for example (though"},{"line_number":99,"context_line":"    only a system-admin should be able to create a volume type)."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  There is a patch up addressing this:"},{"line_number":102,"context_line":"  https://review.opendev.org/c/openstack/cinder/+/835525"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1bed73b0_6d2074e3","line":99,"range":{"start_line":97,"start_character":0,"end_line":99,"end_character":64},"updated":"2022-05-31 10:36:11.000000000","message":"we should also mention about X scoped resource containing attributes of Y scope. Eg: volume being a project level resource contains the host attribute which belongs to system scope.","commit_id":"8ec7213370f1d1b49c2181a1da9257f8514ac77a"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"728ba545d87ebba633bf0994003d2ae232bfd91b","unresolved":true,"context_lines":[{"line_number":140,"context_line":"  implemented.  There is a patch up for this, however:"},{"line_number":141,"context_line":"  https://review.opendev.org/c/openstack/keystone/+/822601"},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"* Implement recognition of the \u0027service\u0027 role.  This has a Keystone"},{"line_number":144,"context_line":"  dependency (creation of the \u0027service\u0027 role during Keystone bootstrap),"},{"line_number":145,"context_line":"  but all we need on the cinder side is agreement that the role will be"},{"line_number":146,"context_line":"  named \u0027service\u0027.  That\u0027s because any of the service actions should also"}],"source_content_type":"text/x-rst","patch_set":1,"id":"57a4eb9b_35830e2b","line":143,"range":{"start_line":143,"start_character":32,"end_line":143,"end_character":39},"updated":"2022-05-31 10:36:11.000000000","message":"should we mention the spec for it as a reference? https://review.opendev.org/c/openstack/keystone-specs/+/818616","commit_id":"8ec7213370f1d1b49c2181a1da9257f8514ac77a"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"728ba545d87ebba633bf0994003d2ae232bfd91b","unresolved":true,"context_lines":[{"line_number":250,"context_line":""},{"line_number":251,"context_line":"* Continue to use the testing framework developed in Xena."},{"line_number":252,"context_line":""},{"line_number":253,"context_line":"* We continue to have the stretch goal (mentioned in the Xena spec) to have"},{"line_number":254,"context_line":"  testing for secure RBAC in the cinder-tempest-plugin, but we do not"},{"line_number":255,"context_line":"  consider it a requirement for successful completion of this spec."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"Documentation Impact"},{"line_number":258,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"2c945d97_26d7f71c","line":255,"range":{"start_line":253,"start_character":0,"end_line":255,"end_character":67},"updated":"2022-05-31 10:36:11.000000000","message":"Benny is working on it here https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/842954","commit_id":"8ec7213370f1d1b49c2181a1da9257f8514ac77a"}]}