)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"ae010f29c7b847bb5eb84960b54cb2a207538934","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Adam Young \u003cayoung@redhat.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2014-11-14 16:55:27 -0500"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fetch policy.json from server"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: I71f63eee8f88402bcefe276cf12546f722bae555"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5a890539_5e7c6fb5","line":7,"updated":"2014-11-15 11:18:00.000000000","message":"from Keystone server","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":8866,"name":"Raildo Mascena de Sousa Filho","email":"rmascena@redhat.com","username":"raildo"},"change_message_id":"2ab510565df71d719369404697775aaed071154a","unresolved":false,"context_lines":[{"line_number":5,"context_line":"CommitDate: 2014-11-14 16:55:27 -0500"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fetch policy.json from server"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: I71f63eee8f88402bcefe276cf12546f722bae555"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5a890539_7dec5ef4","line":8,"updated":"2014-11-27 20:31:32.000000000","message":"link for the BP?","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Adds to ``Keystone Middleware`` the capability to"},{"line_number":10,"context_line":"fetch the ``Dynamic Policy`` for the current"},{"line_number":11,"context_line":"endpoint and overlay the existing local policy"},{"line_number":12,"context_line":"file with it, using ``oslo.policy`` library."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Co-Authored-By: Samuel de Medeiros Queiroz \u003csamuel@lsd.ufcg.edu.br\u003e"},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":9,"id":"3a50d1a3_16159e47","line":12,"updated":"2015-07-22 17:35:07.000000000","message":"Commit messages are never, ever rendered using RestructuredText.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Adds to ``Keystone Middleware`` the capability to"},{"line_number":10,"context_line":"fetch the ``Dynamic Policy`` for the current"},{"line_number":11,"context_line":"endpoint and overlay the existing local policy"},{"line_number":12,"context_line":"file with it, using ``oslo.policy`` library."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Co-Authored-By: Samuel de Medeiros Queiroz \u003csamuel@lsd.ufcg.edu.br\u003e"},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":9,"id":"3a50d1a3_1a333cf7","line":12,"in_reply_to":"3a50d1a3_16159e47","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"}],"specs/backlog/dynamic-policies-fetch-cache.rst":[{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"9db9c16041199377bb17edad621b6a4bca50ac71","unresolved":false,"context_lines":[{"line_number":43,"context_line":"    HTTP/1.1 200 OK"},{"line_number":44,"context_line":"    Cache-Control: max-age\u003d300, must-revalidate, private"},{"line_number":45,"context_line":"    Expires: Fri, 30 Oct 1998 14:19:41 GMT"},{"line_number":46,"context_line":"    Last-Modified: Tue, 30 June 2015 13:00:00 GMT"},{"line_number":47,"context_line":"    Content-Length: 1040"},{"line_number":48,"context_line":"    Content-Type: application/json"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba3cc151_d65d477a","line":46,"updated":"2015-06-30 19:38:40.000000000","message":"That\u0027s funny to have this being modified in 2015 and expiring in 1998 (see line above). :)\n\nI will be fixing in the next patch set.","commit_id":"39eb0a634f5c1e7557044d6b6c8a53feff50dae1"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e7c1b6ff44b828b028a6296cf5407ea28ab24aa4","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":" Fetch and Cache Dynamic Policy"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp dynamic-policies-delivery \u003chttps://blueprints.launchpad.net/keystone/+spec/dynamic-policies-delivery\u003e`_"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_d23202f2","line":8,"updated":"2015-07-22 08:14:17.000000000","message":"I don\u0027t think it is fetching Dynamic Policy....it\u0027s just fetching a Policy from the keystone server","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"331637c8a7f6a0a79f5ff09242eb877c1553617b","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":" Fetch and Cache Dynamic Policy"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp dynamic-policies-delivery \u003chttps://blueprints.launchpad.net/keystone/+spec/dynamic-policies-delivery\u003e`_"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_7094df89","line":8,"in_reply_to":"3a50d1a3_9118d876","updated":"2015-07-23 18:55:49.000000000","message":"+1 the scope of this blueprint is just policy delivery and doesn\u0027t have dependency with the  policy file update (global or namespacing or whatever we decide) work.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":" Fetch and Cache Dynamic Policy"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp dynamic-policies-delivery \u003chttps://blueprints.launchpad.net/keystone/+spec/dynamic-policies-delivery\u003e`_"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_faee9020","line":8,"in_reply_to":"3a50d1a3_9118d876","updated":"2015-07-23 20:39:59.000000000","message":"I agree, let\u0027s call it \"Centralized Policy\". I think I had inherited that naming from the global subject title \u0027Dynamic Policies\u0027","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":" Fetch and Cache Dynamic Policy"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp dynamic-policies-delivery \u003chttps://blueprints.launchpad.net/keystone/+spec/dynamic-policies-delivery\u003e`_"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_9118d876","line":8,"in_reply_to":"3a50d1a3_d23202f2","updated":"2015-07-22 17:35:07.000000000","message":"+1 it\u0027s centralized policy","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"9ceace79879a2c86d4a50f0075c8032219364c18","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp dynamic-policies-delivery \u003chttps://blueprints.launchpad.net/keystone/+spec/dynamic-policies-delivery\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"`Dynamic Policies \u003chttps://wiki.openstack.org/wiki/DynamicPolicies\u003e`_ aims to"},{"line_number":14,"context_line":"improve access control in OpenStack by providing a better mechanism for"},{"line_number":15,"context_line":"defining and delivering policies to service endpoints."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_e254e9fe","line":13,"updated":"2015-07-22 20:01:12.000000000","message":"(nit) \"Dynamic Policies aims\" sounds weird.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp dynamic-policies-delivery \u003chttps://blueprints.launchpad.net/keystone/+spec/dynamic-policies-delivery\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"`Dynamic Policies \u003chttps://wiki.openstack.org/wiki/DynamicPolicies\u003e`_ aims to"},{"line_number":14,"context_line":"improve access control in OpenStack by providing a better mechanism for"},{"line_number":15,"context_line":"defining and delivering policies to service endpoints."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_1a549cc7","line":13,"in_reply_to":"3a50d1a3_e254e9fe","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e7c1b6ff44b828b028a6296cf5407ea28ab24aa4","unresolved":false,"context_lines":[{"line_number":15,"context_line":"defining and delivering policies to service endpoints."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"One step of dynamic delivery of policies is the fetch and cache of the"},{"line_number":18,"context_line":"``Dynamic Policy`` for the current service endpoint by ``Keystone Middleware``."},{"line_number":19,"context_line":"It will use ``oslo.policy`` library to properly cache the custom rules."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Problem Description"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_d21be271","line":18,"updated":"2015-07-22 08:14:17.000000000","message":"I don\u0027t think it is fetching Dynamic Policy....it\u0027s just fetching a policy JSON object.  Why is the policy stored in keystone more dynamic than the json file on the endpoint?  We don\u0027t know what kind of CMS system the cloud provider is using.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":15,"context_line":"defining and delivering policies to service endpoints."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"One step of dynamic delivery of policies is the fetch and cache of the"},{"line_number":18,"context_line":"``Dynamic Policy`` for the current service endpoint by ``Keystone Middleware``."},{"line_number":19,"context_line":"It will use ``oslo.policy`` library to properly cache the custom rules."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Problem Description"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_f0d8ef54","line":18,"in_reply_to":"3a50d1a3_3184645c","updated":"2015-07-23 20:39:59.000000000","message":"Calling it \u0027Centralized Policy\u0027...","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":15,"context_line":"defining and delivering policies to service endpoints."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"One step of dynamic delivery of policies is the fetch and cache of the"},{"line_number":18,"context_line":"``Dynamic Policy`` for the current service endpoint by ``Keystone Middleware``."},{"line_number":19,"context_line":"It will use ``oslo.policy`` library to properly cache the custom rules."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Problem Description"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_3184645c","line":18,"in_reply_to":"3a50d1a3_d21be271","updated":"2015-07-22 17:35:07.000000000","message":"++","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":25,"context_line":"------------------------"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Alice is the kind of person who loves new features and eagerly awaits for new"},{"line_number":28,"context_line":"OpenStack features like ``Dynamic Policies`` to enable them in her cloud."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_718e6c7a","line":28,"updated":"2015-07-22 17:35:07.000000000","message":"WTF kind of use case is this?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"331637c8a7f6a0a79f5ff09242eb877c1553617b","unresolved":false,"context_lines":[{"line_number":25,"context_line":"------------------------"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Alice is the kind of person who loves new features and eagerly awaits for new"},{"line_number":28,"context_line":"OpenStack features like ``Dynamic Policies`` to enable them in her cloud."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_f031cfa2","line":28,"in_reply_to":"3a50d1a3_6249b95f","updated":"2015-07-23 18:55:49.000000000","message":"++ lol","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":25,"context_line":"------------------------"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Alice is the kind of person who loves new features and eagerly awaits for new"},{"line_number":28,"context_line":"OpenStack features like ``Dynamic Policies`` to enable them in her cloud."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_d014d3a0","line":28,"in_reply_to":"3a50d1a3_6249b95f","updated":"2015-07-23 20:39:59.000000000","message":"So I changed it to be more precise as in the Keystone server side spec https://review.openstack.org/#/c/197980/6/specs/backlog/dynamic-policies-delivering-mechanism.rst","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"9ceace79879a2c86d4a50f0075c8032219364c18","unresolved":false,"context_lines":[{"line_number":25,"context_line":"------------------------"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Alice is the kind of person who loves new features and eagerly awaits for new"},{"line_number":28,"context_line":"OpenStack features like ``Dynamic Policies`` to enable them in her cloud."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_6249b95f","line":28,"in_reply_to":"3a50d1a3_718e6c7a","updated":"2015-07-22 20:01:12.000000000","message":"++","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":28,"context_line":"OpenStack features like ``Dynamic Policies`` to enable them in her cloud."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Behind the scenes, ``Keystone Middleware`` will fetch the ``Dynamic Policy``,"},{"line_number":34,"context_line":"which contains the custom policy rules, for the service it is serving and ask"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_31eb0415","line":31,"updated":"2015-07-22 17:35:07.000000000","message":"why is this a literal?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":28,"context_line":"OpenStack features like ``Dynamic Policies`` to enable them in her cloud."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Behind the scenes, ``Keystone Middleware`` will fetch the ``Dynamic Policy``,"},{"line_number":34,"context_line":"which contains the custom policy rules, for the service it is serving and ask"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_5029a3e4","line":31,"in_reply_to":"3a50d1a3_31eb0415","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Behind the scenes, ``Keystone Middleware`` will fetch the ``Dynamic Policy``,"},{"line_number":34,"context_line":"which contains the custom policy rules, for the service it is serving and ask"},{"line_number":35,"context_line":"``oslo.policy`` to overlay the ``Stock Policy``, which is the existing local"},{"line_number":36,"context_line":"policy file."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_71e50c36","line":33,"updated":"2015-07-22 17:35:07.000000000","message":"unnecessary literals","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":30,"context_line":"With that feature, she expects to be able to define her custom policy rules in"},{"line_number":31,"context_line":"``Keystone server`` and have those applied to service endpoints transparently."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Behind the scenes, ``Keystone Middleware`` will fetch the ``Dynamic Policy``,"},{"line_number":34,"context_line":"which contains the custom policy rules, for the service it is serving and ask"},{"line_number":35,"context_line":"``oslo.policy`` to overlay the ``Stock Policy``, which is the existing local"},{"line_number":36,"context_line":"policy file."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_7024df0b","line":33,"in_reply_to":"3a50d1a3_71e50c36","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":33,"context_line":"Behind the scenes, ``Keystone Middleware`` will fetch the ``Dynamic Policy``,"},{"line_number":34,"context_line":"which contains the custom policy rules, for the service it is serving and ask"},{"line_number":35,"context_line":"``oslo.policy`` to overlay the ``Stock Policy``, which is the existing local"},{"line_number":36,"context_line":"policy file."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed Change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_1144c818","line":36,"updated":"2015-07-22 17:35:07.000000000","message":"that detail is up to oslo.policy\u0027s implementation","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":33,"context_line":"Behind the scenes, ``Keystone Middleware`` will fetch the ``Dynamic Policy``,"},{"line_number":34,"context_line":"which contains the custom policy rules, for the service it is serving and ask"},{"line_number":35,"context_line":"``oslo.policy`` to overlay the ``Stock Policy``, which is the existing local"},{"line_number":36,"context_line":"policy file."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed Change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_70529f68","line":36,"in_reply_to":"3a50d1a3_1144c818","updated":"2015-07-23 20:39:59.000000000","message":"Removed from this section...","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e7c1b6ff44b828b028a6296cf5407ea28ab24aa4","unresolved":false,"context_lines":[{"line_number":38,"context_line":"Proposed Change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Add to ``Keystone Middleware`` the capability to fetch ``Dynamic Policy`` based"},{"line_number":42,"context_line":"on the ``endpoint_urls`` config option."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"This option can either be defined directly in the middleware config or be"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_477716d3","line":41,"updated":"2015-07-22 08:14:17.000000000","message":"I don\u0027t think it is fetching Dynamic Policy....it\u0027s just fetching a policy JSON object","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":38,"context_line":"Proposed Change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Add to ``Keystone Middleware`` the capability to fetch ``Dynamic Policy`` based"},{"line_number":42,"context_line":"on the ``endpoint_urls`` config option."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"This option can either be defined directly in the middleware config or be"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_90e64bae","line":41,"in_reply_to":"3a50d1a3_477716d3","updated":"2015-07-23 20:39:59.000000000","message":"We renamed to \u0027Centralized Policy\u0027, as the previous comments make clear :)","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"9ceace79879a2c86d4a50f0075c8032219364c18","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Add to ``Keystone Middleware`` the capability to fetch ``Dynamic Policy`` based"},{"line_number":42,"context_line":"on the ``endpoint_urls`` config option."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"This option can either be defined directly in the middleware config or be"},{"line_number":45,"context_line":"discovered automatically by using the HTTP information available at WSGI"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_62b7793a","line":42,"updated":"2015-07-22 20:01:12.000000000","message":"Is this still using endpoint URLs or is it now using IDs? I\u0027ve seen reference to both in IRC so I\u0027m not really sure where this decision landed. One of the reviews I just looked at was using a policy_id.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"b3e5f4c49027da20ba1a85957cc3e6bd02f39b4b","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Add to ``Keystone Middleware`` the capability to fetch ``Dynamic Policy`` based"},{"line_number":42,"context_line":"on the ``endpoint_urls`` config option."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"This option can either be defined directly in the middleware config or be"},{"line_number":45,"context_line":"discovered automatically by using the HTTP information available at WSGI"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_baffa864","line":42,"in_reply_to":"3a50d1a3_62b7793a","updated":"2015-07-23 18:06:04.000000000","message":"++","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Add to ``Keystone Middleware`` the capability to fetch ``Dynamic Policy`` based"},{"line_number":42,"context_line":"on the ``endpoint_urls`` config option."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"This option can either be defined directly in the middleware config or be"},{"line_number":45,"context_line":"discovered automatically by using the HTTP information available at WSGI"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_10a9db23","line":42,"in_reply_to":"3a50d1a3_baffa864","updated":"2015-07-23 20:39:59.000000000","message":"It should be ids ... I forgot to update this occurrence.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"331637c8a7f6a0a79f5ff09242eb877c1553617b","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Add to ``Keystone Middleware`` the capability to fetch ``Dynamic Policy`` based"},{"line_number":42,"context_line":"on the ``endpoint_urls`` config option."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"This option can either be defined directly in the middleware config or be"},{"line_number":45,"context_line":"discovered automatically by using the HTTP information available at WSGI"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_d0b853ca","line":42,"in_reply_to":"3a50d1a3_baffa864","updated":"2015-07-23 18:55:49.000000000","message":"last time I\u0027ve heard it is endpoint_id?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":45,"context_line":"discovered automatically by using the HTTP information available at WSGI"},{"line_number":46,"context_line":"pipeline level."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Once Middleware knows the ``endpoint_urls``, it requests ``Keystone server``"},{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_7153cce2","line":48,"updated":"2015-07-22 17:35:07.000000000","message":"``Keystone server`` should not be a literal. in addition, it\u0027s the identity service that you\u0027re talking to.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"331637c8a7f6a0a79f5ff09242eb877c1553617b","unresolved":false,"context_lines":[{"line_number":45,"context_line":"discovered automatically by using the HTTP information available at WSGI"},{"line_number":46,"context_line":"pipeline level."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Once Middleware knows the ``endpoint_urls``, it requests ``Keystone server``"},{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_70c85f55","line":48,"in_reply_to":"3a50d1a3_7153cce2","updated":"2015-07-23 18:55:49.000000000","message":"++","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":45,"context_line":"discovered automatically by using the HTTP information available at WSGI"},{"line_number":46,"context_line":"pipeline level."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Once Middleware knows the ``endpoint_urls``, it requests ``Keystone server``"},{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_4b057843","line":48,"in_reply_to":"3a50d1a3_7153cce2","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e7c1b6ff44b828b028a6296cf5407ea28ab24aa4","unresolved":false,"context_lines":[{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Once Middleware knows the ``endpoint_urls``, it requests ``Keystone server``"},{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"},{"line_number":52,"context_line":"policy extension."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_720c4e3b","line":50,"updated":"2015-07-22 08:14:17.000000000","message":"the respective policy JSON object","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Once Middleware knows the ``endpoint_urls``, it requests ``Keystone server``"},{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"},{"line_number":52,"context_line":"policy extension."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_a66f91c2","line":50,"in_reply_to":"3a50d1a3_3160e4a4","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Once Middleware knows the ``endpoint_urls``, it requests ``Keystone server``"},{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"},{"line_number":52,"context_line":"policy extension."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_3160e4a4","line":50,"in_reply_to":"3a50d1a3_720c4e3b","updated":"2015-07-22 17:35:07.000000000","message":"IDs*","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"9ceace79879a2c86d4a50f0075c8032219364c18","unresolved":false,"context_lines":[{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"},{"line_number":52,"context_line":"policy extension."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_420b5d8e","line":52,"updated":"2015-07-22 20:01:12.000000000","message":"So the logic is something like this? Seems like you can just have a single call for it.\n\n  keystone.get_endpoint_ids(request.headers[\u0027HTTP_HOST\u0027]....yada yada)\n  for _id in endpoint_ids:\n      policy \u003d keystone.fetch_policy_for_id(_id)\n      if policy:\n          break","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"},{"line_number":52,"context_line":"policy extension."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_115b68f7","line":52,"updated":"2015-07-22 17:35:07.000000000","message":"how are endpoint IDs sorted? otherwise this is a completely random selection method.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"},{"line_number":52,"context_line":"policy extension."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_26b86110","line":52,"in_reply_to":"3a50d1a3_115b68f7","updated":"2015-07-23 20:39:59.000000000","message":"Only one id should have a policy associated with it, since a single service endpoint can\u0027t have multiple policies associated with it. So we consider as valid the first we find. See dstanek\u0027s algorithm below.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":49,"context_line":"the ``endpoint_ids`` associated with them, and then asks for the"},{"line_number":50,"context_line":"``Dynamic Policy``. If multiple ids are in ``endpoint_ids``, it will be"},{"line_number":51,"context_line":"considered the first which has a policy associated with it through the endpoint"},{"line_number":52,"context_line":"policy extension."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_e6d59942","line":52,"in_reply_to":"3a50d1a3_420b5d8e","updated":"2015-07-23 20:39:59.000000000","message":"Yes something exactly like this.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"9ceace79879a2c86d4a50f0075c8032219364c18","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"},{"line_number":56,"context_line":"appropriate HTTP header values from server responses."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Thus, take the following response as example:"},{"line_number":59,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_62f0d991","line":56,"updated":"2015-07-22 20:01:12.000000000","message":"Why have a policy_cache_time at all if we have the HTTP headers?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"},{"line_number":56,"context_line":"appropriate HTTP header values from server responses."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Thus, take the following response as example:"},{"line_number":59,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_e63119a3","line":56,"in_reply_to":"3a50d1a3_5afb0479","updated":"2015-07-23 20:39:59.000000000","message":"++\nThere is no need to have a predefined value if there is no centralized policy a priori.\nSo the values of cache will come as the policies are received as server responses.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"331637c8a7f6a0a79f5ff09242eb877c1553617b","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"},{"line_number":56,"context_line":"appropriate HTTP header values from server responses."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Thus, take the following response as example:"},{"line_number":59,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_30ec17ba","line":56,"in_reply_to":"3a50d1a3_5afb0479","updated":"2015-07-23 18:55:49.000000000","message":"I like the idea, if we use the HTTP header, the cache time can be configured in keystone instead of each middleware.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"b3e5f4c49027da20ba1a85957cc3e6bd02f39b4b","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"After fetching the custom policy rules, they will be cached according to the"},{"line_number":55,"context_line":"``policy_cache_time`` option value, which is updated depending on the"},{"line_number":56,"context_line":"appropriate HTTP header values from server responses."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Thus, take the following response as example:"},{"line_number":59,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_5afb0479","line":56,"in_reply_to":"3a50d1a3_62f0d991","updated":"2015-07-23 18:06:04.000000000","message":"++","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":72,"context_line":""},{"line_number":73,"context_line":"This defines how long the cached policy is fresh for. This time delta is"},{"line_number":74,"context_line":"defined by ``policy_cache_time`` option, initially defined in the"},{"line_number":75,"context_line":"``Keystone Middleware`` config."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"The value of ``policy_cache_time`` is updated based on either ``Expires`` or"},{"line_number":78,"context_line":"``max-age`` HTTP headers from server response."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_b1fb94c0","line":75,"updated":"2015-07-22 17:35:07.000000000","message":"this should not be a literal as written. ``keystonemiddleware`` is a package, \"Keystone Middleware\" is just a proper noun.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":72,"context_line":""},{"line_number":73,"context_line":"This defines how long the cached policy is fresh for. This time delta is"},{"line_number":74,"context_line":"defined by ``policy_cache_time`` option, initially defined in the"},{"line_number":75,"context_line":"``Keystone Middleware`` config."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"The value of ``policy_cache_time`` is updated based on either ``Expires`` or"},{"line_number":78,"context_line":"``max-age`` HTTP headers from server response."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_26eb81dd","line":75,"in_reply_to":"3a50d1a3_b1fb94c0","updated":"2015-07-23 20:39:59.000000000","message":"Nice, thanks for all these tips.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":75,"context_line":"``Keystone Middleware`` config."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"The value of ``policy_cache_time`` is updated based on either ``Expires`` or"},{"line_number":78,"context_line":"``max-age`` HTTP headers from server response."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Validation and Refresh"},{"line_number":81,"context_line":"----------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_b1e954e8","line":78,"updated":"2015-07-22 17:35:07.000000000","message":"max-age is not a header. all you need to say here is that Expires and Cache-Control headers are to be respected.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":75,"context_line":"``Keystone Middleware`` config."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"The value of ``policy_cache_time`` is updated based on either ``Expires`` or"},{"line_number":78,"context_line":"``max-age`` HTTP headers from server response."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Validation and Refresh"},{"line_number":81,"context_line":"----------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_ff02fb08","line":78,"in_reply_to":"3a50d1a3_b1e954e8","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":80,"context_line":"Validation and Refresh"},{"line_number":81,"context_line":"----------------------"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Once ``Keystone Middleware`` identifies the freshness time is over, it requests"},{"line_number":84,"context_line":"the server for an update passing the following HTTP header."},{"line_number":85,"context_line":"::"},{"line_number":86,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_f1a83c8e","line":83,"updated":"2015-07-22 17:35:07.000000000","message":"freshness time?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":80,"context_line":"Validation and Refresh"},{"line_number":81,"context_line":"----------------------"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Once ``Keystone Middleware`` identifies the freshness time is over, it requests"},{"line_number":84,"context_line":"the server for an update passing the following HTTP header."},{"line_number":85,"context_line":"::"},{"line_number":86,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_5f120f5a","line":83,"in_reply_to":"3a50d1a3_f1a83c8e","updated":"2015-07-23 20:39:59.000000000","message":"removed \u0027time\u0027","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Once ``Keystone Middleware`` identifies the freshness time is over, it requests"},{"line_number":84,"context_line":"the server for an update passing the following HTTP header."},{"line_number":85,"context_line":"::"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"    If-Modified-Since: Tue, 30 June 2015 13:00:00 GMT"},{"line_number":88,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_b1ccf46a","line":85,"updated":"2015-07-22 17:35:07.000000000","message":"in this case, the double colons belong inline with the paragraph, because you have not written a complete sentence.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Once ``Keystone Middleware`` identifies the freshness time is over, it requests"},{"line_number":84,"context_line":"the server for an update passing the following HTTP header."},{"line_number":85,"context_line":"::"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"    If-Modified-Since: Tue, 30 June 2015 13:00:00 GMT"},{"line_number":88,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_e2c5820a","line":85,"in_reply_to":"3a50d1a3_b1ccf46a","updated":"2015-07-23 20:39:59.000000000","message":"Done","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":90,"context_line":"``Last-Modified`` header from the last received response for cache update."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"If the policy has changed since then, ``Keystone Middleware`` will call"},{"line_number":93,"context_line":"``oslo.policy`` to overlay the existing local policy file with the received"},{"line_number":94,"context_line":"``Dynamic Policy``. Otherwise, a ``304 Not Modified`` code will be received,"},{"line_number":95,"context_line":"and ``policy_cache_time`` will be updated according to the appropriate HTTP"},{"line_number":96,"context_line":"header, as specified in the subsection above."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_b1fab473","line":93,"updated":"2015-07-22 17:35:07.000000000","message":"does oslo.policy support this?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":90,"context_line":"``Last-Modified`` header from the last received response for cache update."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"If the policy has changed since then, ``Keystone Middleware`` will call"},{"line_number":93,"context_line":"``oslo.policy`` to overlay the existing local policy file with the received"},{"line_number":94,"context_line":"``Dynamic Policy``. Otherwise, a ``304 Not Modified`` code will be received,"},{"line_number":95,"context_line":"and ``policy_cache_time`` will be updated according to the appropriate HTTP"},{"line_number":96,"context_line":"header, as specified in the subsection above."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_bf7f9365","line":93,"in_reply_to":"3a50d1a3_b1fab473","updated":"2015-07-23 20:39:59.000000000","message":"yes, see https://review.openstack.org/#/c/196753/ and https://review.openstack.org/#/c/200257/","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e7c1b6ff44b828b028a6296cf5407ea28ab24aa4","unresolved":false,"context_lines":[{"line_number":91,"context_line":""},{"line_number":92,"context_line":"If the policy has changed since then, ``Keystone Middleware`` will call"},{"line_number":93,"context_line":"``oslo.policy`` to overlay the existing local policy file with the received"},{"line_number":94,"context_line":"``Dynamic Policy``. Otherwise, a ``304 Not Modified`` code will be received,"},{"line_number":95,"context_line":"and ``policy_cache_time`` will be updated according to the appropriate HTTP"},{"line_number":96,"context_line":"header, as specified in the subsection above."},{"line_number":97,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_3296c693","line":94,"updated":"2015-07-22 08:14:17.000000000","message":"s/Dynamic Policy/keystone server stored policy/ ?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":91,"context_line":""},{"line_number":92,"context_line":"If the policy has changed since then, ``Keystone Middleware`` will call"},{"line_number":93,"context_line":"``oslo.policy`` to overlay the existing local policy file with the received"},{"line_number":94,"context_line":"``Dynamic Policy``. Otherwise, a ``304 Not Modified`` code will be received,"},{"line_number":95,"context_line":"and ``policy_cache_time`` will be updated according to the appropriate HTTP"},{"line_number":96,"context_line":"header, as specified in the subsection above."},{"line_number":97,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_9f6c17d2","line":94,"in_reply_to":"3a50d1a3_3296c693","updated":"2015-07-23 20:39:59.000000000","message":"Centralized policy ... :)","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"9ceace79879a2c86d4a50f0075c8032219364c18","unresolved":false,"context_lines":[{"line_number":98,"context_line":"Alternatives"},{"line_number":99,"context_line":"------------"},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"Leave the Configuration Management System (such as Puppet) manage it."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"Security Impact"},{"line_number":104,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_e2570958","line":101,"updated":"2015-07-22 20:01:12.000000000","message":"What is the operator feedback on this proposal vs. the alternative?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":98,"context_line":"Alternatives"},{"line_number":99,"context_line":"------------"},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"Leave the Configuration Management System (such as Puppet) manage it."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"Security Impact"},{"line_number":104,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_1fbd6702","line":101,"in_reply_to":"3a50d1a3_7af60090","updated":"2015-07-23 20:39:59.000000000","message":"I think a thread in the operators list wouldn\u0027t be a bad idea :)","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"331637c8a7f6a0a79f5ff09242eb877c1553617b","unresolved":false,"context_lines":[{"line_number":98,"context_line":"Alternatives"},{"line_number":99,"context_line":"------------"},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"Leave the Configuration Management System (such as Puppet) manage it."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"Security Impact"},{"line_number":104,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_eb79e493","line":101,"in_reply_to":"3a50d1a3_7af60090","updated":"2015-07-23 18:55:49.000000000","message":"putting my operator hat (like what guang always say): I prefer this approach since it is easier and faster to deploy changes to the policy file and it doesn\u0027t interrupt the service.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"b3e5f4c49027da20ba1a85957cc3e6bd02f39b4b","unresolved":false,"context_lines":[{"line_number":98,"context_line":"Alternatives"},{"line_number":99,"context_line":"------------"},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"Leave the Configuration Management System (such as Puppet) manage it."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"Security Impact"},{"line_number":104,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_7af60090","line":101,"in_reply_to":"3a50d1a3_e2570958","updated":"2015-07-23 18:06:04.000000000","message":"++","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":104,"context_line":"---------------"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"This change touches policy rules, which are sensitive data since they define"},{"line_number":107,"context_line":"access control to service APIs in OpenStack."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Notifications Impact"},{"line_number":110,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_110fe888","line":107,"updated":"2015-07-22 17:35:07.000000000","message":"Please expand on this. By radically increasing the complexity of sourcing policy rules, there are several new attack vectors being introduced by this spec. Put some effort into enumerating and discussing them.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":104,"context_line":"---------------"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"This change touches policy rules, which are sensitive data since they define"},{"line_number":107,"context_line":"access control to service APIs in OpenStack."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Notifications Impact"},{"line_number":110,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_c523b0a6","line":107,"in_reply_to":"3a50d1a3_110fe888","updated":"2015-07-23 20:39:59.000000000","message":"I will mull it a bit more and enumerate the potential attack vectors.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e7c1b6ff44b828b028a6296cf5407ea28ab24aa4","unresolved":false,"context_lines":[{"line_number":125,"context_line":"Other Deployer Impact"},{"line_number":126,"context_line":"---------------------"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"A config switch called ``enable_dynamic_policy`` will allowg deployers to"},{"line_number":129,"context_line":"easily enable and disable the dynamic fetch and cache."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"If the URL that arrives in the service endpoint is the same used in the service"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_b2f096ff","line":128,"updated":"2015-07-22 08:14:17.000000000","message":"maybe enable_policy_from_keystone ?","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":125,"context_line":"Other Deployer Impact"},{"line_number":126,"context_line":"---------------------"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"A config switch called ``enable_dynamic_policy`` will allowg deployers to"},{"line_number":129,"context_line":"easily enable and disable the dynamic fetch and cache."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"If the URL that arrives in the service endpoint is the same used in the service"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_518010c0","line":128,"updated":"2015-07-22 17:35:07.000000000","message":"spelling","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":125,"context_line":"Other Deployer Impact"},{"line_number":126,"context_line":"---------------------"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"A config switch called ``enable_dynamic_policy`` will allowg deployers to"},{"line_number":129,"context_line":"easily enable and disable the dynamic fetch and cache."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"If the URL that arrives in the service endpoint is the same used in the service"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_1f6b2787","line":128,"in_reply_to":"3a50d1a3_518010c0","updated":"2015-07-23 20:39:59.000000000","message":"To be consistent with the naming we adopted, I think \u0027enable_centralized_policy\u0027 could be a good name.\n\nAlso, s/allowg/allow","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"1e276696594e38896ef5b585d90cc8170d960079","unresolved":false,"context_lines":[{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Otherwise, (for example, the URL is rewritten at some point in the"},{"line_number":135,"context_line":"communication) the deployer will have to configure the ``endpoint_urls`` in the"},{"line_number":136,"context_line":"`Keystone Middleware`` config. This need to be done for each service endpoint,"},{"line_number":137,"context_line":"as they have their own middleware process defined in their WSGI pipeline."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Developer Impact"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_71750cf8","line":136,"updated":"2015-07-22 17:35:07.000000000","message":"this first sentence, (especially with the awkward use of parens) makes no sense to me.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"d9c0b32251e687a0194506a7d71cca7dd553ba77","unresolved":false,"context_lines":[{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Otherwise, (for example, the URL is rewritten at some point in the"},{"line_number":135,"context_line":"communication) the deployer will have to configure the ``endpoint_urls`` in the"},{"line_number":136,"context_line":"`Keystone Middleware`` config. This need to be done for each service endpoint,"},{"line_number":137,"context_line":"as they have their own middleware process defined in their WSGI pipeline."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Developer Impact"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3a50d1a3_9f10975b","line":136,"in_reply_to":"3a50d1a3_71750cf8","updated":"2015-07-23 20:39:59.000000000","message":"I clarified it... what I meant is, if the URL matches the URL in the service catalog, we can do a look up and retrieve the ids.\n\nIf the URL arriving from the WSGI pipeline is different from what we have in the catalog, the automatic discovery can\u0027t happen.\n\nOne example of that is when the URL requested by the user get re-written at any point in the communication. For example, suppose URLs are re-written at the SSL termination in the network. This is something that was pointed out by Morgan.","commit_id":"2e6d5a4c1e5cf0eecc89dd86bf65e9581de2ff23"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"53e791a307a4194e7b007b03f4427c4304da2c5c","unresolved":false,"context_lines":[{"line_number":119,"context_line":"------------------"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"Performance will be slightly impacted when the cache has expired and Keystone"},{"line_number":122,"context_line":"Middleware needs to ask the Identity server to update it."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"Other Deployer Impact"},{"line_number":125,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"3a50d1a3_e5e7cc44","line":122,"updated":"2015-07-23 20:41:44.000000000","message":"Still need to address Dolph\u0027s concerns on this topic. From last patch set:\n\n\"Please expand on this. By radically increasing the complexity of sourcing policy rules, there are several new attack vectors being introduced by this spec. Put some effort into enumerating and discussing them.\"","commit_id":"6a43249c696bf430ab0bb8c1509e10db4ecbc36d"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"1b063203a72ed603e6dbd783e0e868c25767339a","unresolved":false,"context_lines":[{"line_number":143,"context_line":"---------------------"},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"A config switch called ``enable_centralized_policy`` will allow deployers to"},{"line_number":146,"context_line":"easily enable and disable the fetch and cache of Centralized Policies."},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"In addition, deployers can define the ``endpoint_ids`` config. Not defining it"},{"line_number":149,"context_line":"means that Keystone Middleware will try to automatically discover it by looking"}],"source_content_type":"text/x-rst","patch_set":11,"id":"3a50d1a3_66bac670","line":146,"updated":"2015-07-24 12:23:22.000000000","message":"Let\u0027s mark, that this will be optional, turned of by default and if disabled old policy management based on static files will be enforced.","commit_id":"6932d562378e0eca597e5f5aa2ca5e0724a75cb4"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"5b30296bb84512d0249bb2cbe1b1b12ac739f51f","unresolved":false,"context_lines":[{"line_number":143,"context_line":"---------------------"},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"A config switch called ``enable_centralized_policy`` will allow deployers to"},{"line_number":146,"context_line":"easily enable and disable the fetch and cache of Centralized Policies."},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"In addition, deployers can define the ``endpoint_ids`` config. Not defining it"},{"line_number":149,"context_line":"means that Keystone Middleware will try to automatically discover it by looking"}],"source_content_type":"text/x-rst","patch_set":11,"id":"3a50d1a3_895da5ee","line":146,"in_reply_to":"3a50d1a3_66bac670","updated":"2015-07-24 12:30:15.000000000","message":"Done","commit_id":"6932d562378e0eca597e5f5aa2ca5e0724a75cb4"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"5df72954c80b577f9e1d345ac1a139190aa72937","unresolved":false,"context_lines":[{"line_number":14,"context_line":"improve access control in OpenStack by providing a better mechanism for"},{"line_number":15,"context_line":"defining and delivering policies to service endpoints."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Custom policy rules will be defined in the Identity server as the Centralized"},{"line_number":18,"context_line":"Policy, which can be associated to endpoints using the endpoint policy API."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"After defined and associated, Centralized Policies will be fetched to"}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_a7da0516","line":17,"updated":"2015-07-24 14:12:15.000000000","message":"Why are these policies more \"custom\" than what\u0027s on the endpoints locally?","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"36961aa46c2afdf67472fd1dd8d38e0b23a24caf","unresolved":false,"context_lines":[{"line_number":14,"context_line":"improve access control in OpenStack by providing a better mechanism for"},{"line_number":15,"context_line":"defining and delivering policies to service endpoints."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Custom policy rules will be defined in the Identity server as the Centralized"},{"line_number":18,"context_line":"Policy, which can be associated to endpoints using the endpoint policy API."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"After defined and associated, Centralized Policies will be fetched to"}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_8d832dcc","line":17,"in_reply_to":"3a50d1a3_a7da0516","updated":"2015-07-27 20:31:41.000000000","message":"The point here isn\u0027t that it will become possible to define custom policy rules (as you pointed out, they can already be defined locally), it\u0027s that they will be defined in the *identity server* side.","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"5df72954c80b577f9e1d345ac1a139190aa72937","unresolved":false,"context_lines":[{"line_number":27,"context_line":"Alice the Cloud Deployer"},{"line_number":28,"context_line":"------------------------"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Alice is expert in deploying OpenStack clouds. As soon as she deploys a new"},{"line_number":31,"context_line":"cloud for her customers, she has to update Access Control rules for the"},{"line_number":32,"context_line":"services very often."},{"line_number":33,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_877d89e9","line":30,"updated":"2015-07-24 14:12:15.000000000","message":"Are we saying that someone has to be an expert to use this capability?  This seems an odd sentence.","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"36961aa46c2afdf67472fd1dd8d38e0b23a24caf","unresolved":false,"context_lines":[{"line_number":27,"context_line":"Alice the Cloud Deployer"},{"line_number":28,"context_line":"------------------------"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Alice is expert in deploying OpenStack clouds. As soon as she deploys a new"},{"line_number":31,"context_line":"cloud for her customers, she has to update Access Control rules for the"},{"line_number":32,"context_line":"services very often."},{"line_number":33,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_3f647ce3","line":30,"in_reply_to":"3a50d1a3_877d89e9","updated":"2015-07-27 20:31:41.000000000","message":"I agree with you, one can understand we are saying that. I am going to change this sentence","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"5df72954c80b577f9e1d345ac1a139190aa72937","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Alice would like to have an alternative to that distribution, where the custom"},{"line_number":40,"context_line":"policy could be defined without the use of an out-of-band mechanism, i.e using"},{"line_number":41,"context_line":"the API, and then those custom rules would be applied to service endpoints."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The feature Alice is looking for is the Centralized Policy definition and"},{"line_number":44,"context_line":"distribution. With that, she will be able to define her custom policy rules in"}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_a780c58c","line":41,"updated":"2015-07-24 14:12:15.000000000","message":"We need to say what the deficiencies are of a puppet based CMS (otherwise why would she change it if it ain\u0027t broke).  Ideas: Her topology changes frequently, or uses variable  numbers of nodes behind proxies....making it laborious to keep her puppet CMS in sync with such topology changes.","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"36961aa46c2afdf67472fd1dd8d38e0b23a24caf","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Alice would like to have an alternative to that distribution, where the custom"},{"line_number":40,"context_line":"policy could be defined without the use of an out-of-band mechanism, i.e using"},{"line_number":41,"context_line":"the API, and then those custom rules would be applied to service endpoints."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The feature Alice is looking for is the Centralized Policy definition and"},{"line_number":44,"context_line":"distribution. With that, she will be able to define her custom policy rules in"}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_9f0590c3","line":41,"in_reply_to":"3a50d1a3_a780c58c","updated":"2015-07-27 20:31:41.000000000","message":"Yes, this makes sense. I am going to add this missing bit. :)","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"5df72954c80b577f9e1d345ac1a139190aa72937","unresolved":false,"context_lines":[{"line_number":40,"context_line":"policy could be defined without the use of an out-of-band mechanism, i.e using"},{"line_number":41,"context_line":"the API, and then those custom rules would be applied to service endpoints."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The feature Alice is looking for is the Centralized Policy definition and"},{"line_number":44,"context_line":"distribution. With that, she will be able to define her custom policy rules in"},{"line_number":45,"context_line":"Identity Server and have those applied to service endpoints transparently."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_aab88c2b","line":43,"updated":"2015-07-24 14:12:15.000000000","message":"she isn\u0027t necessary looking for that...this is our proposal...and should be under the \"proposed change\" section/","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"36961aa46c2afdf67472fd1dd8d38e0b23a24caf","unresolved":false,"context_lines":[{"line_number":40,"context_line":"policy could be defined without the use of an out-of-band mechanism, i.e using"},{"line_number":41,"context_line":"the API, and then those custom rules would be applied to service endpoints."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The feature Alice is looking for is the Centralized Policy definition and"},{"line_number":44,"context_line":"distribution. With that, she will be able to define her custom policy rules in"},{"line_number":45,"context_line":"Identity Server and have those applied to service endpoints transparently."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_7f5be4f6","line":43,"in_reply_to":"3a50d1a3_aab88c2b","updated":"2015-07-27 20:31:41.000000000","message":"Done","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"5df72954c80b577f9e1d345ac1a139190aa72937","unresolved":false,"context_lines":[{"line_number":48,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Add to Keystone Middleware the capability to fetch and cache the Centralized"},{"line_number":51,"context_line":"Policy for the service endpoint it is serving."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":54,"context_line":"either be defined directly in the Middleware config or be automatically"}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_cae39832","line":51,"updated":"2015-07-24 14:12:15.000000000","message":"we need to say how/why this solves the problem outlined above.","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"36961aa46c2afdf67472fd1dd8d38e0b23a24caf","unresolved":false,"context_lines":[{"line_number":48,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Add to Keystone Middleware the capability to fetch and cache the Centralized"},{"line_number":51,"context_line":"Policy for the service endpoint it is serving."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":54,"context_line":"either be defined directly in the Middleware config or be automatically"}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_fffe14ad","line":51,"in_reply_to":"3a50d1a3_cae39832","updated":"2015-07-27 20:31:41.000000000","message":"Done","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"5df72954c80b577f9e1d345ac1a139190aa72937","unresolved":false,"context_lines":[{"line_number":97,"context_line":"------------"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"Leave the Configuration Management System (such as Puppet) manage it."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"Security Impact"},{"line_number":102,"context_line":"---------------"},{"line_number":103,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"3a50d1a3_0ae4200b","line":100,"updated":"2015-07-24 14:12:15.000000000","message":"The option suggested is you have a /policy API actually on each project on each endpoint, that provides a REST API that, say, Horizon , could talk to and even update.  WE should say what the drawback of that approach are (e.g. how on earth would Horizon know which endpoints to update....e.g. all nova endpoints, how would it cope with proxies etc.","commit_id":"98f260d2aab49800bc1316be72bd32bb17176c3b"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"4ba2c3159cc73cd906196720091570682e48e2d7","unresolved":false,"context_lines":[{"line_number":78,"context_line":"This mechanism will be controlled by Keystone server, as described in the spec"},{"line_number":79,"context_line":"`Centralized Policies Distribution Mechanism \u003chttps://review.openstack.org/#/c/197980/\u003e`_."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"}],"source_content_type":"text/x-rst","patch_set":15,"id":"3a50d1a3_b475db98","line":81,"updated":"2015-07-28 09:59:22.000000000","message":"I\u0027m not sure I follow what the endpoint_ids config is?  Is this a file with all endpoint IDs? (I hope not)","commit_id":"6f68c930dfdccf5254ade5af4b81c17c8d15c61c"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"0833630d15b287190148ce1d8ffd8e2f51cbd805","unresolved":false,"context_lines":[{"line_number":78,"context_line":"This mechanism will be controlled by Keystone server, as described in the spec"},{"line_number":79,"context_line":"`Centralized Policies Distribution Mechanism \u003chttps://review.openstack.org/#/c/197980/\u003e`_."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"}],"source_content_type":"text/x-rst","patch_set":15,"id":"3a50d1a3_2a8e3f2e","line":81,"in_reply_to":"3a50d1a3_b475db98","updated":"2015-07-28 12:56:54.000000000","message":"No, it is a config as any other, however it is represented as a list, i.e accepting multiple values :)","commit_id":"6f68c930dfdccf5254ade5af4b81c17c8d15c61c"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"49b79ead5b090abf45266dd0022c91b63f28cd66","unresolved":false,"context_lines":[{"line_number":78,"context_line":"This mechanism will be controlled by Keystone server, as described in the spec"},{"line_number":79,"context_line":"`Centralized Policies Distribution Mechanism \u003chttps://review.openstack.org/#/c/197980/\u003e`_."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_06533718","line":81,"updated":"2015-07-28 14:57:29.000000000","message":"is this documented somewhere in more detail?","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"bd9a082d54be53aedde99986a81586aebc625b09","unresolved":false,"context_lines":[{"line_number":78,"context_line":"This mechanism will be controlled by Keystone server, as described in the spec"},{"line_number":79,"context_line":"`Centralized Policies Distribution Mechanism \u003chttps://review.openstack.org/#/c/197980/\u003e`_."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_fc049a15","line":81,"in_reply_to":"3a50d1a3_06533718","updated":"2015-07-28 15:29:10.000000000","message":"I added more details on why it is a list of endpoint id..","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"49b79ead5b090abf45266dd0022c91b63f28cd66","unresolved":false,"context_lines":[{"line_number":79,"context_line":"`Centralized Policies Distribution Mechanism \u003chttps://review.openstack.org/#/c/197980/\u003e`_."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"},{"line_number":85,"context_line":"the endpoints in the cloud."}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_46b37f4d","line":82,"updated":"2015-07-28 14:57:29.000000000","message":"this is the keystone middleware config, yes?  Let\u0027s be specific","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"bd9a082d54be53aedde99986a81586aebc625b09","unresolved":false,"context_lines":[{"line_number":79,"context_line":"`Centralized Policies Distribution Mechanism \u003chttps://review.openstack.org/#/c/197980/\u003e`_."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The policy fetch will be based on the ``endpoint_ids`` config option. It can"},{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"},{"line_number":85,"context_line":"the endpoints in the cloud."}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_61030543","line":82,"in_reply_to":"3a50d1a3_46b37f4d","updated":"2015-07-28 15:29:10.000000000","message":"Done","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"49b79ead5b090abf45266dd0022c91b63f28cd66","unresolved":false,"context_lines":[{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"},{"line_number":85,"context_line":"the endpoints in the cloud."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"In addition, this feature will make use of the existing policy management API,"},{"line_number":88,"context_line":"opening the door for improvements in it, like adding the capability to validate"}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_263193ed","line":85,"updated":"2015-07-28 14:57:29.000000000","message":"does it? It feels like we\u0027ve just pushed the problem around....doesn\u0027t the cloud provider now have to keep the middleware config up to date with their topology?","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"bd9a082d54be53aedde99986a81586aebc625b09","unresolved":false,"context_lines":[{"line_number":82,"context_line":"either be defined directly in the Middleware config or be automatically"},{"line_number":83,"context_line":"discovered by using the HTTP information available at WSGI pipeline level. This"},{"line_number":84,"context_line":"solves the hardness to keep an external CMS tool in sync with the topology of"},{"line_number":85,"context_line":"the endpoints in the cloud."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"In addition, this feature will make use of the existing policy management API,"},{"line_number":88,"context_line":"opening the door for improvements in it, like adding the capability to validate"}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_3c6682bb","line":85,"in_reply_to":"3a50d1a3_263193ed","updated":"2015-07-28 15:29:10.000000000","message":"In the case it is automatically discovered, it does.\n\nIn the case it needs to be set directly, it makes the task easier, since multiple processes behind a proxy would get the same config.\n\nI clarified this point.","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"49b79ead5b090abf45266dd0022c91b63f28cd66","unresolved":false,"context_lines":[{"line_number":198,"context_line":"defaults to ``false``, meaning that the old policy mechanism will be used by"},{"line_number":199,"context_line":"default, since no policy will be fetched from the server."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"In addition, deployers can define the ``endpoint_ids`` config. This needs to be"},{"line_number":202,"context_line":"done for each service endpoint, as they have their own middleware filter"},{"line_number":203,"context_line":"defined in their WSGI pipeline."},{"line_number":204,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_c60a2f20","line":201,"updated":"2015-07-28 14:57:29.000000000","message":"can? must?","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"bd9a082d54be53aedde99986a81586aebc625b09","unresolved":false,"context_lines":[{"line_number":198,"context_line":"defaults to ``false``, meaning that the old policy mechanism will be used by"},{"line_number":199,"context_line":"default, since no policy will be fetched from the server."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"In addition, deployers can define the ``endpoint_ids`` config. This needs to be"},{"line_number":202,"context_line":"done for each service endpoint, as they have their own middleware filter"},{"line_number":203,"context_line":"defined in their WSGI pipeline."},{"line_number":204,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a50d1a3_7ccf2a56","line":201,"in_reply_to":"3a50d1a3_c60a2f20","updated":"2015-07-28 15:29:10.000000000","message":"they may define it.. in the case they don\u0027t, automatic discovery will happen, as speficied in the next paragraph\n\nI\u0027ve put them together in a single paragraph","commit_id":"ea129962edf85750253c77f119d28f90552dc599"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":20,"context_line":"assigned on them, and pass this token along to services in requests to perform"},{"line_number":21,"context_line":"actions on resources. The services check the roles and the scope from the token"},{"line_number":22,"context_line":"against the rules defined for the requested action on the policy.json file to"},{"line_number":23,"context_line":"determine if the user has enough privileges to execute it."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"In order to manage access control to services in an OpenStack cloud, operators"},{"line_number":26,"context_line":"need to use an out-of-band mechanism to update and distribute the policy.json"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_6bd67f50","line":23,"updated":"2015-07-28 16:35:47.000000000","message":"(nit) you\u0027re not really checking if the user has the privileges. it\u0027s checking that the token the user presented proves he has the privileges.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":20,"context_line":"assigned on them, and pass this token along to services in requests to perform"},{"line_number":21,"context_line":"actions on resources. The services check the roles and the scope from the token"},{"line_number":22,"context_line":"against the rules defined for the requested action on the policy.json file to"},{"line_number":23,"context_line":"determine if the user has enough privileges to execute it."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"In order to manage access control to services in an OpenStack cloud, operators"},{"line_number":26,"context_line":"need to use an out-of-band mechanism to update and distribute the policy.json"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_387a0089","line":23,"in_reply_to":"3a50d1a3_6bd67f50","updated":"2015-07-28 20:12:46.000000000","message":"that should be \"user\u0027s token\"","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":35,"context_line":"associated to service endpoints using the endpoint policy API."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"What this spec proposes is that, once the Centralized Policies are defined and"},{"line_number":38,"context_line":"associated, they will be fetched and cached to the associated service endpoints"},{"line_number":39,"context_line":"by Keystone Middleware."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_6b643fb8","line":38,"updated":"2015-07-28 16:35:47.000000000","message":"(nit) s/to the/by the/","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":35,"context_line":"associated to service endpoints using the endpoint policy API."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"What this spec proposes is that, once the Centralized Policies are defined and"},{"line_number":38,"context_line":"associated, they will be fetched and cached to the associated service endpoints"},{"line_number":39,"context_line":"by Keystone Middleware."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_d878bc80","line":38,"in_reply_to":"3a50d1a3_6b643fb8","updated":"2015-07-28 20:12:46.000000000","message":"Done","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":54,"context_line":""},{"line_number":55,"context_line":"* The rules definition process is very susceptible to human errors, which would"},{"line_number":56,"context_line":"  likely only be detected after the files are distributed to service endpoints"},{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_6b32ffa8","line":57,"updated":"2015-07-28 16:35:47.000000000","message":"how is this any different?","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"45bdfbd61b32220a534e2c99423d6a5e0b4154f1","unresolved":false,"context_lines":[{"line_number":54,"context_line":""},{"line_number":55,"context_line":"* The rules definition process is very susceptible to human errors, which would"},{"line_number":56,"context_line":"  likely only be detected after the files are distributed to service endpoints"},{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_fdb1eae0","line":57,"in_reply_to":"3a50d1a3_49a148f7","updated":"2015-07-28 19:48:45.000000000","message":"Agreed.  Remove this.  Does not apply for this BP.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"7cbb77270877a4e3456630062794104d08905615","unresolved":false,"context_lines":[{"line_number":54,"context_line":""},{"line_number":55,"context_line":"* The rules definition process is very susceptible to human errors, which would"},{"line_number":56,"context_line":"  likely only be detected after the files are distributed to service endpoints"},{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_49a148f7","line":57,"in_reply_to":"3a50d1a3_6b32ffa8","updated":"2015-07-28 18:01:41.000000000","message":"+1.  This only makes debugging policy issues more complicated.  I would expect deployers to test out changes with local policy before sending the policy file to keystone.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":54,"context_line":""},{"line_number":55,"context_line":"* The rules definition process is very susceptible to human errors, which would"},{"line_number":56,"context_line":"  likely only be detected after the files are distributed to service endpoints"},{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_b8c29083","line":57,"in_reply_to":"3a50d1a3_fdb1eae0","updated":"2015-07-28 20:12:46.000000000","message":"Done","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_2bdf173b","line":60,"updated":"2015-07-28 16:35:47.000000000","message":"is this a real problem? i would suspect that even if this change was made they\u0027d be dealing with this for the other configuration on this node.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"151292309220aa1757d897df710dda9ffefacf8c","unresolved":false,"context_lines":[{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_f80a581f","line":60,"in_reply_to":"3a50d1a3_1db7f6d8","updated":"2015-07-28 19:56:06.000000000","message":"L89-92 says how it is improved...\n\nI thought we were supposed to say what are the limitations of the current approach..","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"45bdfbd61b32220a534e2c99423d6a5e0b4154f1","unresolved":false,"context_lines":[{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_1db7f6d8","line":60,"in_reply_to":"3a50d1a3_2bdf173b","updated":"2015-07-28 19:48:45.000000000","message":"No.  Remove this.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"bfbafbd6773bb2eb0a23207c53c9c328839c0c66","unresolved":false,"context_lines":[{"line_number":57,"context_line":"  and authorization does not work as expected;"},{"line_number":58,"context_line":"* Keeping the CMS tools in sync becomes a laborious task when the topology"},{"line_number":59,"context_line":"  changes frenquently, for example when there is a variable number of service"},{"line_number":60,"context_line":"  nodes behind proxies."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_78e16829","line":60,"in_reply_to":"3a50d1a3_f80a581f","updated":"2015-07-28 20:00:26.000000000","message":"yeah, good point, I wonder if we can rewrite this to make it clearer.  Something along the lines of \"policy should be managed by the deployment, but since many packages include the stock policy files as code, they are not editable in the endpoints.  The result is that policy cannot be modified.\"","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":84,"context_line":""},{"line_number":85,"context_line":"This config option can either be defined directly in the Keystone Middleware"},{"line_number":86,"context_line":"config or be automatically discovered by using the HTTP information available"},{"line_number":87,"context_line":"at WSGI pipeline level."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"When automatically discovered, this solves the hardness to keep an external CMS"},{"line_number":90,"context_line":"tool in sync with the topology of the endpoints in the cloud. If set in the"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_2b007765","line":87,"updated":"2015-07-28 16:35:47.000000000","message":"This may be harder than you think. I\u0027m assuming that you will take the URL and try to match it against the URL in the database to find the correct endpoint_id.  Consider this case:\n\n  HTTP URL: http://server/path/more_path\n  URL in DB: http://server/path\n\nor worse yet:\n\n  HTTP URL: http://server/12345\n  URL in DB: http://server/$(tenant_id)s","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"45bdfbd61b32220a534e2c99423d6a5e0b4154f1","unresolved":false,"context_lines":[{"line_number":84,"context_line":""},{"line_number":85,"context_line":"This config option can either be defined directly in the Keystone Middleware"},{"line_number":86,"context_line":"config or be automatically discovered by using the HTTP information available"},{"line_number":87,"context_line":"at WSGI pipeline level."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"When automatically discovered, this solves the hardness to keep an external CMS"},{"line_number":90,"context_line":"tool in sync with the topology of the endpoints in the cloud. If set in the"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_3de3d2da","line":87,"in_reply_to":"3a50d1a3_2b007765","updated":"2015-07-28 19:48:45.000000000","message":"Agreed;  future work, not in this spec.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":84,"context_line":""},{"line_number":85,"context_line":"This config option can either be defined directly in the Keystone Middleware"},{"line_number":86,"context_line":"config or be automatically discovered by using the HTTP information available"},{"line_number":87,"context_line":"at WSGI pipeline level."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"When automatically discovered, this solves the hardness to keep an external CMS"},{"line_number":90,"context_line":"tool in sync with the topology of the endpoints in the cloud. If set in the"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_b81e100a","line":87,"in_reply_to":"3a50d1a3_3de3d2da","updated":"2015-07-28 20:12:46.000000000","message":"Done","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Once ``endpoint_ids`` config is known, Middleware requests the Identity server"},{"line_number":103,"context_line":"for the respective Centralized Policy. The server will be in charge of deciding"},{"line_number":104,"context_line":"what centralized policy should be returned for that list of IDs."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"After fetching the policy rules, they will be cached according to the"},{"line_number":107,"context_line":"appropriate HTTP header values from server responses."}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_2b0e378c","line":104,"updated":"2015-07-28 16:35:47.000000000","message":"You\u0027ll be passing in the endpoint_ids and the current URI right? That way the server can pick the best endpoint for the job?","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"45bdfbd61b32220a534e2c99423d6a5e0b4154f1","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Once ``endpoint_ids`` config is known, Middleware requests the Identity server"},{"line_number":103,"context_line":"for the respective Centralized Policy. The server will be in charge of deciding"},{"line_number":104,"context_line":"what centralized policy should be returned for that list of IDs."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"After fetching the policy rules, they will be cached according to the"},{"line_number":107,"context_line":"appropriate HTTP header values from server responses."}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_fde80ab5","line":104,"in_reply_to":"3a50d1a3_2b0e378c","updated":"2015-07-28 19:48:45.000000000","message":"one endpoint id.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Once ``endpoint_ids`` config is known, Middleware requests the Identity server"},{"line_number":103,"context_line":"for the respective Centralized Policy. The server will be in charge of deciding"},{"line_number":104,"context_line":"what centralized policy should be returned for that list of IDs."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"After fetching the policy rules, they will be cached according to the"},{"line_number":107,"context_line":"appropriate HTTP header values from server responses."}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_18a2a4ae","line":104,"in_reply_to":"3a50d1a3_fde80ab5","updated":"2015-07-28 20:12:46.000000000","message":"Done","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":144,"context_line":"1. Leave the Configuration Management System (such as Puppet) manage it;"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"This would keep the out-of-band mechanisms used today to update and distribute"},{"line_number":147,"context_line":"the policy files to endpoints."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"2. Add a policy management API on each OpenStack project"},{"line_number":150,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_cb555350","line":147,"updated":"2015-07-28 16:35:47.000000000","message":"Has anyone said that this is bad?","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"45bdfbd61b32220a534e2c99423d6a5e0b4154f1","unresolved":false,"context_lines":[{"line_number":144,"context_line":"1. Leave the Configuration Management System (such as Puppet) manage it;"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"This would keep the out-of-band mechanisms used today to update and distribute"},{"line_number":147,"context_line":"the policy files to endpoints."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"2. Add a policy management API on each OpenStack project"},{"line_number":150,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_dd318e5a","line":147,"in_reply_to":"3a50d1a3_cb555350","updated":"2015-07-28 19:48:45.000000000","message":"It means that there is no way to tie it back to management in Keystone proper.  Fetch from Keystone is the start of the Dynamic Policy approach; without this spec, we cannot continue on to the rest of Dynamic Policy.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":144,"context_line":"1. Leave the Configuration Management System (such as Puppet) manage it;"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"This would keep the out-of-band mechanisms used today to update and distribute"},{"line_number":147,"context_line":"the policy files to endpoints."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"2. Add a policy management API on each OpenStack project"},{"line_number":150,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_b893705a","line":147,"in_reply_to":"3a50d1a3_dd318e5a","updated":"2015-07-28 20:12:46.000000000","message":"Done","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":146,"context_line":"This would keep the out-of-band mechanisms used today to update and distribute"},{"line_number":147,"context_line":"the policy files to endpoints."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"2. Add a policy management API on each OpenStack project"},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"This alternative is opposed to the centralized policy management. The new API"},{"line_number":152,"context_line":"would be reflected on every service endpoint. There are many drawbacks in this"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_cbdc73e6","line":149,"updated":"2015-07-28 16:35:47.000000000","message":"Yeah, I agree that this isn\u0027t a reasonable alternative.","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":146,"context_line":"This would keep the out-of-band mechanisms used today to update and distribute"},{"line_number":147,"context_line":"the policy files to endpoints."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"2. Add a policy management API on each OpenStack project"},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"This alternative is opposed to the centralized policy management. The new API"},{"line_number":152,"context_line":"would be reflected on every service endpoint. There are many drawbacks in this"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_589cac69","line":149,"in_reply_to":"3a50d1a3_cbdc73e6","updated":"2015-07-28 20:12:46.000000000","message":"++","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7a6087158501d29d3c600bc3610b4042b7bd5175","unresolved":false,"context_lines":[{"line_number":170,"context_line":"control of any service endpoint using this feature in the cloud."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"Documentation exposing this security risk will be provided to warn deployers"},{"line_number":173,"context_line":"that access to the policies API must be very restrict."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Notifications Impact"},{"line_number":176,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_abdfa7d4","line":173,"updated":"2015-07-28 16:35:47.000000000","message":"s/restrict/restricted/","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"3b0dc9539e2ff3c9a586e3f85d6bb66556e146e5","unresolved":false,"context_lines":[{"line_number":170,"context_line":"control of any service endpoint using this feature in the cloud."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"Documentation exposing this security risk will be provided to warn deployers"},{"line_number":173,"context_line":"that access to the policies API must be very restrict."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Notifications Impact"},{"line_number":176,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a50d1a3_78996878","line":173,"in_reply_to":"3a50d1a3_abdfa7d4","updated":"2015-07-28 20:12:46.000000000","message":"Done","commit_id":"925829b0d31bba9f53e20e12f00464b0862476fb"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"4c4a459e8027b678cb866815bcd9b8f87bf3db50","unresolved":false,"context_lines":[{"line_number":107,"context_line":"Once Keystone Middleware identifies that the freshness is over, it queries the"},{"line_number":108,"context_line":"server for an update passing the ``If-Modified-Since`` HTTP header: ::"},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"    If-Modified-Since: Tue, 30 June 2015 13:00:00 GMT"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Notice that the value of ``If-Modified-Since`` is the value of the"},{"line_number":113,"context_line":"``Last-Modified`` header from the last received response for cache update."}],"source_content_type":"text/x-rst","patch_set":18,"id":"3a50d1a3_3ffda608","line":110,"updated":"2015-07-30 13:00:43.000000000","message":"One note here.....we don\u0027t actually need to implement this on the server side. We can have the server always just respond with the policy. The client will cached based on the cache control headers and get a new one every time it asks.","commit_id":"cd7a9e13fd5417fe7727ed1a73c4b38b45041cc4"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"6141a920ab8e813e5f03c61267cc3014492f7b58","unresolved":false,"context_lines":[{"line_number":107,"context_line":"Once Keystone Middleware identifies that the freshness is over, it queries the"},{"line_number":108,"context_line":"server for an update passing the ``If-Modified-Since`` HTTP header: ::"},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"    If-Modified-Since: Tue, 30 June 2015 13:00:00 GMT"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Notice that the value of ``If-Modified-Since`` is the value of the"},{"line_number":113,"context_line":"``Last-Modified`` header from the last received response for cache update."}],"source_content_type":"text/x-rst","patch_set":18,"id":"3a50d1a3_1fb9ca79","line":110,"in_reply_to":"3a50d1a3_3ffda608","updated":"2015-07-30 13:13:47.000000000","message":"Yes, this does make sense. Thanks","commit_id":"cd7a9e13fd5417fe7727ed1a73c4b38b45041cc4"}],"specs/backlog/policy-fetch.rst":[{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Fetch Policy for enforcement"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/example\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Fetch the policy.json file for the current endpoint from Keystone server."},{"line_number":14,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_68f81ce6","line":11,"updated":"2015-03-30 22:00:15.000000000","message":"Needs a real spec.","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":17,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Policy files today are maintained as part of the source code repository and"},{"line_number":20,"context_line":"deployed along with the Services.  Keystone now has the potential to assign a"},{"line_number":21,"context_line":"different policy file based on the endpoint id.  The services have no means to"},{"line_number":22,"context_line":"take advantage of this mechanism.  This mechamism will provide a single"},{"line_number":23,"context_line":"implementation that all of the services can consume Instead of having each"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_28db347e","line":20,"updated":"2015-03-30 22:00:15.000000000","message":"services","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"d9ec65990d2f72cca764a46407102bcb2c919e31","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Policy files today are maintained as part of the source code repository and"},{"line_number":20,"context_line":"deployed along with the Services.  Keystone now has the potential to assign a"},{"line_number":21,"context_line":"different policy file based on the endpoint id.  The services have no means to"},{"line_number":22,"context_line":"take advantage of this mechanism.  This mechamism will provide a single"},{"line_number":23,"context_line":"implementation that all of the services can consume Instead of having each"},{"line_number":24,"context_line":"service implement their own."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9aa53dc9_7753e239","line":22,"updated":"2015-04-10 09:00:11.000000000","message":"yes they do....there is an API they *could* call (and support in the keystoneclient lib).  The problem is that they have not yet taken advantage of this.","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":13063,"name":"WEI CHEN","email":"dave.jungler@gmail.com","username":"wei.d.chen"},"change_message_id":"c1d4f75f3154ac0a93695cdfeb4f338e9a60bece","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Policy files today are maintained as part of the source code repository and"},{"line_number":20,"context_line":"deployed along with the Services.  Keystone now has the potential to assign a"},{"line_number":21,"context_line":"different policy file based on the endpoint id.  The services have no means to"},{"line_number":22,"context_line":"take advantage of this mechanism.  This mechamism will provide a single"},{"line_number":23,"context_line":"implementation that all of the services can consume Instead of having each"},{"line_number":24,"context_line":"service implement their own."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3afb71cf_a17182aa","line":22,"in_reply_to":"9aa53dc9_7753e239","updated":"2015-06-08 09:56:13.000000000","message":"Is this supported in the keystoneclient already? I saw we have the API but no client supported.","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"5b79493fb8817f6467de7c904dbb519d59483246","unresolved":false,"context_lines":[{"line_number":20,"context_line":"deployed along with the Services.  Keystone now has the potential to assign a"},{"line_number":21,"context_line":"different policy file based on the endpoint id.  The services have no means to"},{"line_number":22,"context_line":"take advantage of this mechanism.  This mechamism will provide a single"},{"line_number":23,"context_line":"implementation that all of the services can consume Instead of having each"},{"line_number":24,"context_line":"service implement their own."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_54016803","line":23,"updated":"2015-02-13 00:22:40.000000000","message":"nit: Use \"instead\", small \"i\"","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"5b79493fb8817f6467de7c904dbb519d59483246","unresolved":false,"context_lines":[{"line_number":26,"context_line":"Proposed Change"},{"line_number":27,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Each endpoint will need to know its endpoint id.  The Keystoneclient will"},{"line_number":30,"context_line":"fetch the policy.json file during policy enforcement and cache it based on the"},{"line_number":31,"context_line":"appropriate HTTP header values."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_b459c4fe","line":29,"updated":"2015-02-13 00:22:40.000000000","message":"Does this refer to KSC or the service client?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":26,"context_line":"Proposed Change"},{"line_number":27,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Each endpoint will need to know its endpoint id.  The Keystoneclient will"},{"line_number":30,"context_line":"fetch the policy.json file during policy enforcement and cache it based on the"},{"line_number":31,"context_line":"appropriate HTTP header values."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_c8184887","line":29,"updated":"2015-03-30 22:00:15.000000000","message":"Shouldn\u0027t this be in keystonemiddleware instead of keystoneclient?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":13063,"name":"WEI CHEN","email":"dave.jungler@gmail.com","username":"wei.d.chen"},"change_message_id":"c1d4f75f3154ac0a93695cdfeb4f338e9a60bece","unresolved":false,"context_lines":[{"line_number":26,"context_line":"Proposed Change"},{"line_number":27,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Each endpoint will need to know its endpoint id.  The Keystoneclient will"},{"line_number":30,"context_line":"fetch the policy.json file during policy enforcement and cache it based on the"},{"line_number":31,"context_line":"appropriate HTTP header values."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3afb71cf_e1853a59","line":29,"in_reply_to":"da9b358b_c8184887","updated":"2015-06-08 09:56:13.000000000","message":"++ read from other relevant spec, this should keystonemiddleware that will cache the file instead of keystoneclient.\n\nor maybe it looks like, keystoneclient fetch the policy.json and cache it locally in each service.","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"5b182c806f134f23758e734385544d573534b72d","unresolved":false,"context_lines":[{"line_number":30,"context_line":"fetch the policy.json file during policy enforcement and cache it based on the"},{"line_number":31,"context_line":"appropriate HTTP header values."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Because different clients will want to cache in different mechanisms,  the"},{"line_number":34,"context_line":"cache will be allocated and managd by the calling program.  The initial"},{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dac4157f_51a9617a","line":33,"updated":"2015-04-21 17:39:56.000000000","message":"Do you mean different services?  I would think that servers want to cache policy data as well.","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":31,"context_line":"appropriate HTTP header values."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Because different clients will want to cache in different mechanisms,  the"},{"line_number":34,"context_line":"cache will be allocated and managd by the calling program.  The initial"},{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_287a1425","line":34,"updated":"2015-03-30 22:00:15.000000000","message":"managed","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":13063,"name":"WEI CHEN","email":"dave.jungler@gmail.com","username":"wei.d.chen"},"change_message_id":"c1d4f75f3154ac0a93695cdfeb4f338e9a60bece","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Because different clients will want to cache in different mechanisms,  the"},{"line_number":34,"context_line":"cache will be allocated and managd by the calling program.  The initial"},{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"},{"line_number":38,"context_line":"expected to be used by all services except Keystone.  Second is a python call"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3afb71cf_81032642","line":35,"updated":"2015-06-08 09:56:13.000000000","message":"1. \u0027Policy.json\u0027 is cached since the file may out of date so we need to fetch it periodically or via event driven mechanisms, so we may need to mention how to sync the file between service and keystone server?\n\n2. Any other mechanism beside Memcache? if we have, shall we also define a unified configuration for each service?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Because different clients will want to cache in different mechanisms,  the"},{"line_number":34,"context_line":"cache will be allocated and managd by the calling program.  The initial"},{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"},{"line_number":38,"context_line":"expected to be used by all services except Keystone.  Second is a python call"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_c88f2822","line":35,"updated":"2015-03-30 22:00:15.000000000","message":"implementation","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":33,"context_line":"Because different clients will want to cache in different mechanisms,  the"},{"line_number":34,"context_line":"cache will be allocated and managd by the calling program.  The initial"},{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"},{"line_number":38,"context_line":"expected to be used by all services except Keystone.  Second is a python call"},{"line_number":39,"context_line":"that will fetch the policy via a python API to be used when the client is"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_28a1f494","line":36,"updated":"2015-03-30 22:00:15.000000000","message":"Can you talk a little bit more about how the \u0027calling program\u0027 rigs up a cache?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"5b79493fb8817f6467de7c904dbb519d59483246","unresolved":false,"context_lines":[{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"},{"line_number":38,"context_line":"expected to be used by all services except Keystone.  Second is a python call"},{"line_number":39,"context_line":"that will fetch the policy via a python API to be used when the client is"},{"line_number":40,"context_line":"called from inside the Keystone Server."},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_9424c060","line":38,"updated":"2015-02-13 00:22:40.000000000","message":"Would there be a need to setup a service account to be able to authenticate to keystone to get the policy?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"5b182c806f134f23758e734385544d573534b72d","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"},{"line_number":38,"context_line":"expected to be used by all services except Keystone.  Second is a python call"},{"line_number":39,"context_line":"that will fetch the policy via a python API to be used when the client is"},{"line_number":40,"context_line":"called from inside the Keystone Server."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dac4157f_913b7938","line":39,"updated":"2015-04-21 17:39:56.000000000","message":"the client \u003d\u003d keystone-client?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"5b182c806f134f23758e734385544d573534b72d","unresolved":false,"context_lines":[{"line_number":38,"context_line":"expected to be used by all services except Keystone.  Second is a python call"},{"line_number":39,"context_line":"that will fetch the policy via a python API to be used when the client is"},{"line_number":40,"context_line":"called from inside the Keystone Server."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Alternatives"},{"line_number":43,"context_line":"------------"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dac4157f_114e4996","line":41,"updated":"2015-04-21 17:39:56.000000000","message":"Any thoughts on how keystoneclient is going to figure out its policy cache is dirty and needs to http fetch policy again?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"5b79493fb8817f6467de7c904dbb519d59483246","unresolved":false,"context_lines":[{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Does this change alter the API in a way that may impact security, such as"},{"line_number":62,"context_line":"  a new way to access sensitive information or a new way to login?"},{"line_number":63,"context_line":"* Yes, should allow for quicker deployment of poliucy rules, with the positive"},{"line_number":64,"context_line":"  and nagative aspects.  Positive is that responses to security issues will be"},{"line_number":65,"context_line":"  faster to address.  Negative is that, with more fluid oilicy rules, it will"},{"line_number":66,"context_line":"  be easier to deploy more broken rules."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_9455a0fb","line":63,"updated":"2015-02-13 00:22:40.000000000","message":"typo: poliucy to policy","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"5b79493fb8817f6467de7c904dbb519d59483246","unresolved":false,"context_lines":[{"line_number":61,"context_line":"* Does this change alter the API in a way that may impact security, such as"},{"line_number":62,"context_line":"  a new way to access sensitive information or a new way to login?"},{"line_number":63,"context_line":"* Yes, should allow for quicker deployment of poliucy rules, with the positive"},{"line_number":64,"context_line":"  and nagative aspects.  Positive is that responses to security issues will be"},{"line_number":65,"context_line":"  faster to address.  Negative is that, with more fluid oilicy rules, it will"},{"line_number":66,"context_line":"  be easier to deploy more broken rules."},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_5476c8a4","line":64,"updated":"2015-02-13 00:22:40.000000000","message":"typo: negative","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":62,"context_line":"  a new way to access sensitive information or a new way to login?"},{"line_number":63,"context_line":"* Yes, should allow for quicker deployment of poliucy rules, with the positive"},{"line_number":64,"context_line":"  and nagative aspects.  Positive is that responses to security issues will be"},{"line_number":65,"context_line":"  faster to address.  Negative is that, with more fluid oilicy rules, it will"},{"line_number":66,"context_line":"  be easier to deploy more broken rules."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"* Does this change involve cryptography or hashing?"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_287574ca","line":65,"updated":"2015-03-30 22:00:15.000000000","message":"policy","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":79,"context_line":"  single API interaction to consume significant server resources? Some examples"},{"line_number":80,"context_line":"  of this include launching subprocesses for each connection, or entity"},{"line_number":81,"context_line":"  expansion attacks in XML."},{"line_number":82,"context_line":"* Caching should  secure agains DOS attacks, as there is no remote way to"},{"line_number":83,"context_line":"  invalidate cache."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_0882b094","line":82,"updated":"2015-03-30 22:00:15.000000000","message":"extra space in there","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"c607b87ee8ca6c02986de0900d7b642cca083922","unresolved":false,"context_lines":[{"line_number":90,"context_line":"Other End User Impact"},{"line_number":91,"context_line":"---------------------"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"This is a client feature.  It will effect deployers,  but should not effect"},{"line_number":94,"context_line":"end users."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3afb71cf_4513da0d","line":93,"updated":"2015-06-08 21:19:13.000000000","message":"s/effect/affect\n\nextra space after comma","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e56f1e901b32eb1d3f11f208a91452ec7cec02ac","unresolved":false,"context_lines":[{"line_number":97,"context_line":"Performance Impact"},{"line_number":98,"context_line":"------------------"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"There should be no change in performance progile.  There will be an"},{"line_number":101,"context_line":"immeasurable impact on the initial fetch of the policy file and whenever a"},{"line_number":102,"context_line":"cache invalidation requires an additional fetch of the policy from Keystone"},{"line_number":103,"context_line":"server."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da9b358b_c84a8883","line":100,"updated":"2015-03-30 22:00:15.000000000","message":"profile","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"5b79493fb8817f6467de7c904dbb519d59483246","unresolved":false,"context_lines":[{"line_number":109,"context_line":"that have not already been mentioned, such as:"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"* Configuration will be done based on the endpoint_id value.  This is a new"},{"line_number":112,"context_line":"  configuiration value in the auth_token section of the endpoint API config"},{"line_number":113,"context_line":"  file.  Additionally, the activation of the policy fetch will require a"},{"line_number":114,"context_line":"  deliberate configuration value."},{"line_number":115,"context_line":"* Each of the services will need to modify"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_94f12003","line":112,"updated":"2015-02-13 00:22:40.000000000","message":"typo: configuration","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"},{"author":{"_account_id":13063,"name":"WEI CHEN","email":"dave.jungler@gmail.com","username":"wei.d.chen"},"change_message_id":"c1d4f75f3154ac0a93695cdfeb4f338e9a60bece","unresolved":false,"context_lines":[{"line_number":143,"context_line":"Work items or tasks -- break the feature up into the things that need to be"},{"line_number":144,"context_line":"done to implement it. Those parts might end up being done by different people,"},{"line_number":145,"context_line":"but we\u0027re mostly trying to understand the timeline for implementation."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"Dependencies"},{"line_number":149,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3afb71cf_8421f44f","line":146,"updated":"2015-06-08 09:56:13.000000000","message":"hmm, no work items here?","commit_id":"4bf13b5222d3a1b7528aff2298c6cb3e66891274"}],"specs/keystoneclient/policy-fetch.rst":[{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"48244c40b14fb7f93169c7d8385a5a5132047048","unresolved":false,"context_lines":[{"line_number":20,"context_line":"deployed along with the Services.  Keystone now has the potential to assign a"},{"line_number":21,"context_line":"different policy file based on the endpoint id.  The services have no means to"},{"line_number":22,"context_line":"take advantage of this mechanism.  This mechamism will provide a single"},{"line_number":23,"context_line":"implementation that all of the services can consume Instead of having each"},{"line_number":24,"context_line":"service implement their own."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_5ea54f45","line":23,"updated":"2014-11-15 11:17:30.000000000","message":"s/Instead/instead","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"48244c40b14fb7f93169c7d8385a5a5132047048","unresolved":false,"context_lines":[{"line_number":31,"context_line":"appropriate HTTP header values."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Because different clients will want to cache in different mechanisms,  the"},{"line_number":34,"context_line":"cache will be allocated and managd by the calling program.  The initial"},{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_7e65ab1c","line":34,"updated":"2014-11-15 11:17:30.000000000","message":"s/managd/managed","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"48244c40b14fb7f93169c7d8385a5a5132047048","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Because different clients will want to cache in different mechanisms,  the"},{"line_number":34,"context_line":"cache will be allocated and managd by the calling program.  The initial"},{"line_number":35,"context_line":"implmentaiton will have File based and Dogpile based Memcache caches."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Two different fetch mechanisms will be supported.  Foremost is the HTTP fetch,"},{"line_number":38,"context_line":"expected to be used by all services except Keystone.  Second is a python call"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_9e6a57ec","line":35,"updated":"2014-11-15 11:17:30.000000000","message":"implementation*\n\nMemcached*","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"48244c40b14fb7f93169c7d8385a5a5132047048","unresolved":false,"context_lines":[{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Let Puppet manage it"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Fetch from Congress"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_de705fde","line":49,"updated":"2014-11-15 11:17:30.000000000","message":"change to bullet points","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":8866,"name":"Raildo Mascena de Sousa Filho","email":"rmascena@redhat.com","username":"raildo"},"change_message_id":"894f8ce454a5d7c8de6fb04cab2c7c5ec5764f2f","unresolved":false,"context_lines":[{"line_number":47,"context_line":"Let Puppet manage it"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Fetch from Congress"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Security Impact"},{"line_number":53,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_1a7520cc","line":50,"updated":"2014-11-27 20:30:49.000000000","message":"Can you explain more about this alternatives? How this can work in Congress? How Puppet will do that?","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"48244c40b14fb7f93169c7d8385a5a5132047048","unresolved":false,"context_lines":[{"line_number":148,"context_line":"Dependencies"},{"line_number":149,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"* Dependon policy-enforce.rst"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":""},{"line_number":154,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_fe78bbc5","line":151,"updated":"2014-11-15 11:17:30.000000000","message":"Depends on*","commit_id":"1d5f83116d87c530d2281da103bd36219ec16356"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"880bdfb790e4f45ba0e059da2b2c1e9ecab88c7f","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Fetch Policy for enforcement"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/example\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Fetch the policy.json file for the current endpoint from Keystone server."},{"line_number":14,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_359692f0","line":11,"updated":"2015-01-19 11:45:30.000000000","message":"wrong link","commit_id":"23ca4858b7fb8e896f0f519351a2213320f3de8e"},{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"426ec1460f326c3de0e3db82c7f733605915375e","unresolved":false,"context_lines":[{"line_number":26,"context_line":"Proposed Change"},{"line_number":27,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Each endpoint will need to know its endpoint id.  The Keystoneclient will"},{"line_number":30,"context_line":"fetch the policy.json file during policy enforcement and cache it based on the"},{"line_number":31,"context_line":"appropriate HTTP header values."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_e928f587","line":29,"updated":"2014-12-22 17:42:40.000000000","message":"Shouldn\u0027t we make endpoint_id user generated besides being autogenerated to make it usable similar to region?","commit_id":"23ca4858b7fb8e896f0f519351a2213320f3de8e"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"880bdfb790e4f45ba0e059da2b2c1e9ecab88c7f","unresolved":false,"context_lines":[{"line_number":143,"context_line":"Work items or tasks -- break the feature up into the things that need to be"},{"line_number":144,"context_line":"done to implement it. Those parts might end up being done by different people,"},{"line_number":145,"context_line":"but we\u0027re mostly trying to understand the timeline for implementation."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"Dependencies"},{"line_number":149,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_9572e6e2","line":146,"updated":"2015-01-19 11:45:30.000000000","message":"this would be useful.","commit_id":"23ca4858b7fb8e896f0f519351a2213320f3de8e"}]}
