)]}'
{"specs/keystone/ongoing/domains-projects-metadata.rst":[{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"eb7994345b0308e278aeb23ed69aa92c541f3883","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Ex: An administrator would like to assign a label a project or domain that"},{"line_number":30,"context_line":"they do not want other users to be able to view, or would only want certain"},{"line_number":31,"context_line":"user groups to have access to."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e3ac5537","line":31,"updated":"2016-04-13 16:29:30.000000000","message":"Can you provide a concrete example why the data needs to be private?\n\nI want to be sure if we\u0027re expanding extras/moving beyond extras we are doing it for the right reasons. This could be in an external system (as an alternative) that gates access as you described without needing keystone to learn how to do this.\n\nThis may very well belong in keystone, but having the whole picture is important to properly evaluate the proposal.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"ff16c1dc5c390d3ba91c0b9934f144ee13d7aa22","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Ex: An administrator would like to assign a label a project or domain that"},{"line_number":30,"context_line":"they do not want other users to be able to view, or would only want certain"},{"line_number":31,"context_line":"user groups to have access to."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_fef4ec87","line":31,"in_reply_to":"5a18252c_e3ac5537","updated":"2016-04-13 16:36:05.000000000","message":"yes, i\u0027m curious to see some use cases here.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"53c53545fdab5b3c419d2c1f6bafc62e35175dcf","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Ex: An administrator would like to assign a label a project or domain that"},{"line_number":30,"context_line":"they do not want other users to be able to view, or would only want certain"},{"line_number":31,"context_line":"user groups to have access to."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9abb7d3a_bc703673","line":31,"in_reply_to":"5a18252c_fef4ec87","updated":"2016-06-01 16:41:47.000000000","message":"++","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"eb7994345b0308e278aeb23ed69aa92c541f3883","unresolved":false,"context_lines":[{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Develop an extension for Keystone to allow API calls to store metadata for"},{"line_number":38,"context_line":"domains and/or projects that would be only be viewable to administrators."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_9e75f899","line":38,"updated":"2016-04-13 16:29:30.000000000","message":"Keystone does not do extensions anymore, the API is either part of keystone or not. \n\nA new API goes through a couple of phases:\n1) Experimental, where it is given a trial run. if the code works well and receives support and continued interest, after 1-2 cycles, the aPI can graduate to stable\n\n2) stable: this is like any other API with a contract and is not subject to backwards incompatible changes.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"53c53545fdab5b3c419d2c1f6bafc62e35175dcf","unresolved":false,"context_lines":[{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Develop an extension for Keystone to allow API calls to store metadata for"},{"line_number":38,"context_line":"domains and/or projects that would be only be viewable to administrators."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9abb7d3a_5c2f8a3e","line":38,"in_reply_to":"5a18252c_9e75f899","updated":"2016-06-01 16:41:47.000000000","message":"This would technically only really care about project metadata since domain are just special projects now.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"eb7994345b0308e278aeb23ed69aa92c541f3883","unresolved":false,"context_lines":[{"line_number":47,"context_line":"Security Impact"},{"line_number":48,"context_line":"---------------"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"None."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_fe922c9e","line":50,"updated":"2016-04-13 16:29:30.000000000","message":"I disagree, there is a security impact as you are adding a new level of authz logic (who can access these values) in keystone.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"ff16c1dc5c390d3ba91c0b9934f144ee13d7aa22","unresolved":false,"context_lines":[{"line_number":47,"context_line":"Security Impact"},{"line_number":48,"context_line":"---------------"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"None."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_5e4b60c9","line":50,"in_reply_to":"5a18252c_fe922c9e","updated":"2016-04-13 16:36:05.000000000","message":"I agree. We need to document why and how for the security of this new data.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"eb7994345b0308e278aeb23ed69aa92c541f3883","unresolved":false,"context_lines":[{"line_number":60,"context_line":"---------------------"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"This should only affect an administrator and/or users with specified roles as"},{"line_number":63,"context_line":"designated by the administrator."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Performance Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_fed98c84","line":63,"updated":"2016-04-13 16:29:30.000000000","message":"As a point, keystone does not have roles that are \"global\", all roles are currently assigned to a project(/tenant) or domain. Does this impact your design?","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"ff16c1dc5c390d3ba91c0b9934f144ee13d7aa22","unresolved":false,"context_lines":[{"line_number":66,"context_line":"Performance Impact"},{"line_number":67,"context_line":"------------------"},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"There will be an additional database connection, any performance impact will"},{"line_number":70,"context_line":"be the additional calls for read/write of metadata for any domains/projects."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"Other Deployer Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_9ec85824","line":69,"range":{"start_line":69,"start_character":17,"end_line":69,"end_character":47},"updated":"2016-04-13 16:36:05.000000000","message":"I\u0027m curious to know about this. Not using the existing DB connection? Are you planning on using backends that are not tied to the resource backends?","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"eb7994345b0308e278aeb23ed69aa92c541f3883","unresolved":false,"context_lines":[{"line_number":67,"context_line":"------------------"},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"There will be an additional database connection, any performance impact will"},{"line_number":70,"context_line":"be the additional calls for read/write of metadata for any domains/projects."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"Other Deployer Impact"},{"line_number":73,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_7e09fcdc","line":70,"updated":"2016-04-13 16:29:30.000000000","message":"Would the backend for this data be pluggable or baked into the resource subsystem (like extras work)?","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"eb7994345b0308e278aeb23ed69aa92c541f3883","unresolved":false,"context_lines":[{"line_number":75,"context_line":"To enable this extension:"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"1. Run the database migrations:"},{"line_number":78,"context_line":"   ``keystone-manage db_sync --extension metadata``"},{"line_number":79,"context_line":"2. Add a metadata section to the ``keystone-paste.ini``"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"   |  ``[filter:metadata]``"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_7ed45c46","line":78,"updated":"2016-04-13 16:29:30.000000000","message":"See above, No extensions.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"eb7994345b0308e278aeb23ed69aa92c541f3883","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"1. Run the database migrations:"},{"line_number":78,"context_line":"   ``keystone-manage db_sync --extension metadata``"},{"line_number":79,"context_line":"2. Add a metadata section to the ``keystone-paste.ini``"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"   |  ``[filter:metadata]``"},{"line_number":82,"context_line":"   |  ``use \u003d egg:keystone#metadata``"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"3. Include the metadata filter in the ``api_v3`` and ``admin_api``"},{"line_number":85,"context_line":"   pipeline. It should look something like this (notice that ``metadata``"},{"line_number":86,"context_line":"   extension was included before ``service_v3``)"},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"   |  ``[pipeline:api_v3]``"},{"line_number":89,"context_line":"   |  ``pipeline \u003d access_log sizelimit url_normalize token_auth``"},{"line_number":90,"context_line":"      ``admin_token_auth xml_body json_body ec2_extension s3_extension``"},{"line_number":91,"context_line":"      ``metadata service_v3``"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"   |  ``[pipeline:admin_api]``"},{"line_number":94,"context_line":"   |  ``pipeline \u003d access_log sizelimit url_normalize token_auth``"},{"line_number":95,"context_line":"      ``admin_token_auth xml_body json_body ec2_extension s3_extension``"},{"line_number":96,"context_line":"      ``crud_extension metadata admin_service``"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"4. Restart keystone"},{"line_number":99,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_de593000","line":96,"range":{"start_line":79,"start_character":0,"end_line":96,"end_character":47},"updated":"2016-04-13 16:29:30.000000000","message":"As outlined above, this should not be added as a filter, this should be baked into the correct routers (service_v3, admin_service) etc. Keystone does not do extensions in-tree.","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"53c53545fdab5b3c419d2c1f6bafc62e35175dcf","unresolved":false,"context_lines":[{"line_number":123,"context_line":"----------"},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Update existing code for changes since creation present in Newton and meet"},{"line_number":126,"context_line":"community standards."},{"line_number":127,"context_line":""},{"line_number":128,"context_line":""},{"line_number":129,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9abb7d3a_5ca4aab8","line":126,"updated":"2016-06-01 16:41:47.000000000","message":"Could this be broken down into a list of work items? How do you plan on tackling the work?","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"},{"author":{"_account_id":10046,"name":"Henrique Truta","email":"henrique@lsd.ufcg.edu.br","username":"henriquetruta"},"change_message_id":"66f3f9662b0a0f27798b28c671fdd360b03cbf35","unresolved":false,"context_lines":[{"line_number":437,"context_line":"\u0027\u0027204\u0027\u0027"},{"line_number":438,"context_line":""},{"line_number":439,"context_line":""},{"line_number":440,"context_line":"Tenants"},{"line_number":441,"context_line":"-------"},{"line_number":442,"context_line":""},{"line_number":443,"context_line":"Metadata related to Tenants of the OpenStack Identity API. v2.0"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a122d0e_8c2289b7","line":440,"updated":"2016-04-28 16:40:28.000000000","message":"should we have this? v2.0 is deprecated. If this is accepted, I suggest we only include it in domains and projects","commit_id":"b526c87359dc24d56e02dec232f6723b843bc077"}]}
