)]}'
{"specs/backlog/policy-by-url.rst":[{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"413168edd044536a0fc346525d4cb7cdebdb5524","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem Description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_502d9f44","line":21,"updated":"2015-06-16 20:26:17.000000000","message":"What about dual-homed IP-only environments? What about loopback addresses (for type\u003dinternal endpoints) vs. external interfaces? Other cases where hostname may not work as a unique ID for the endpoint?","commit_id":"7d3f8c8be08e0d6ad9aac4f2749dc4ec7353ae9b"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"26921bdac637ac4c690edc3baddade4707bdd8d7","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem Description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_32158048","line":21,"in_reply_to":"fa32b979_502d9f44","updated":"2015-06-16 20:56:51.000000000","message":"It is not just hostname.  For example, on an all-in-one localhost install, the keystone url will be http://127.0.0.1:5000/  and in a deconflicted URL case it could be https://10.1.1.1/keystone .  It is not just the Hostname that makes up the endpoibnt URL.","commit_id":"7d3f8c8be08e0d6ad9aac4f2749dc4ec7353ae9b"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"413168edd044536a0fc346525d4cb7cdebdb5524","unresolved":false,"context_lines":[{"line_number":49,"context_line":"`GET /OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"That returns only the single policy associated with the endpoint_url."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Alternatives"},{"line_number":55,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_b0c0ab2b","line":52,"updated":"2015-06-16 20:26:17.000000000","message":"need a DELETE as well, right?","commit_id":"7d3f8c8be08e0d6ad9aac4f2749dc4ec7353ae9b"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"26921bdac637ac4c690edc3baddade4707bdd8d7","unresolved":false,"context_lines":[{"line_number":49,"context_line":"`GET /OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"That returns only the single policy associated with the endpoint_url."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Alternatives"},{"line_number":55,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_b2019008","line":52,"in_reply_to":"fa32b979_b0c0ab2b","updated":"2015-06-16 20:56:51.000000000","message":"Yep,  good point","commit_id":"7d3f8c8be08e0d6ad9aac4f2749dc4ec7353ae9b"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"413168edd044536a0fc346525d4cb7cdebdb5524","unresolved":false,"context_lines":[{"line_number":71,"context_line":"Notifications Impact"},{"line_number":72,"context_line":"--------------------"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Any notifications that are currently emitted for endpoint policy will continue to be emitted unchanged."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Other End User Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_f078732d","line":74,"updated":"2015-06-16 20:26:17.000000000","message":"line too long?","commit_id":"7d3f8c8be08e0d6ad9aac4f2749dc4ec7353ae9b"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"413168edd044536a0fc346525d4cb7cdebdb5524","unresolved":false,"context_lines":[{"line_number":94,"context_line":"Other Deployer Impact"},{"line_number":95,"context_line":"---------------------"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Priamry change will be that, when creating an endpoint, the installer can"},{"line_number":98,"context_line":"add the URL to the Service configuration file prior to starting the service,"},{"line_number":99,"context_line":"and know that the value set therein will be used for policy fetches."},{"line_number":100,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_30afbb95","line":97,"updated":"2015-06-16 20:26:17.000000000","message":"s/Priamry/Primary/","commit_id":"7d3f8c8be08e0d6ad9aac4f2749dc4ec7353ae9b"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"413168edd044536a0fc346525d4cb7cdebdb5524","unresolved":false,"context_lines":[{"line_number":128,"context_line":"Documentation Impact"},{"line_number":129,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"API will need to be docuemtned"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"References"},{"line_number":134,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_90c9e77a","line":131,"updated":"2015-06-16 20:26:17.000000000","message":"s/docuemtned/documented/","commit_id":"7d3f8c8be08e0d6ad9aac4f2749dc4ec7353ae9b"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"78d3185c2555375c1b5ee1a509b4c8355e64a093","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem Description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_88b19749","line":21,"updated":"2015-06-17 14:54:51.000000000","message":"Does the server know its hostname, though? There could be a bunch of different ones for the same server... E.g. using 127.0.0.1, using ::1, using multiple different external IP addresses on a multi-homed system, using an actual hostname, using a proxy on one port, running directly on another port, etc... Yes, it knows all these, but does it know for which it should request the policy config from keystone?\n\nAnd a single keystone instance can only support one policy config. If that config is tied to url, and there are multiple endpoints in the catalog that point to the same keystone instance (typical with v3... e.g. \"type\u003dinternal\" endpoint using 127.0.0.1 and \"type\u003dpublic\" endpoint using a hostname or external ip), then this method would allow multiple policy configs because there are multiple urls... even though only one can actually be used.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem Description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_23973bed","line":21,"in_reply_to":"fa32b979_1abce604","updated":"2015-06-17 20:43:39.000000000","message":"That\u0027s actually a really good point. Is the URL just an arbitrary decision? Couldn\u0027t a deployer configure the url as \u0027rax-iad-compute\u0027 and then use that as the URL when storing the policy? Also, where is the URL configured?","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"f4c458ea9a49a567d29816430e608be7dc6eab24","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem Description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_48eb41dc","line":21,"in_reply_to":"fa32b979_23973bed","updated":"2015-06-18 23:53:25.000000000","message":"That\u0027s an interesting argument. A service can have multiple endpoints with different URLs. Public endpoint is likely an external VIP, along with some sort of API proxy (i.e. REPOSE, apigee, etc). In those cases, multiple services shared a same public URL. :) Similarly, internal endpoint is likely an internal VIP.\n\nFor the same reason we have endpoint_id to uniquely identity an endpoint as oppose to just the url.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"535374043ff374bef3152f8a9ab54c7a5e58ab7a","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem Description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_c4430312","line":21,"in_reply_to":"fa32b979_88b19749","updated":"2015-06-17 17:00:36.000000000","message":"No, the server does not know its hostname.  THe installer knows the hostname, and has to set the value prior to running the service.\n\nYes, a single Keystone instance, or any other service can only support a single policy file.  That is by design, and that is how they are all currently implemetned.  THere is no reason to split policy per `endpoint`;  policy is already per API","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"c051d9009cc1aee794d2647107a3b2025d6ee1df","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Problem Description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_1abce604","line":21,"in_reply_to":"fa32b979_c4430312","updated":"2015-06-17 17:35:15.000000000","message":"I wasn\u0027t suggesting that we split policy per endpoint. I\u0027m saying there isn\u0027t a single URL per service instance, yet this proposes we use the URL as if there is.  If the installer has to set the value somewhere (where? and shouldn\u0027t that be covered in this spec?), then why make it the URL... it can be anything at that point. Making it one of the URLs just seems confusing... People will think it\u0027s the URL, when it\u0027s not, really... it\u0027s whatever you configured in this place that we are *calling* a URL but could really be anything.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Since a server knows its Hostname, but not its assigned ID, prior to"},{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"When using the endpoint policy APIS to assign a policy for an endpoint, the"},{"line_number":26,"context_line":"current api associates that with the ID, not the URL.  However, there is no"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_639d4365","line":23,"updated":"2015-06-17 20:43:39.000000000","message":"endpoint","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":22,"context_line":"registering with Keystone, interacting with policy should be based on the URL"},{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"When using the endpoint policy APIS to assign a policy for an endpoint, the"},{"line_number":26,"context_line":"current api associates that with the ID, not the URL.  However, there is no"},{"line_number":27,"context_line":"uniqueness constraint on the URLs, so the policy could potentially be"},{"line_number":28,"context_line":"different for endpoint_ids that are all the same server."}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_039c775b","line":25,"updated":"2015-06-17 20:43:39.000000000","message":"APIs","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":23,"context_line":"of the Endpoint, and not the endpoint ID."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"When using the endpoint policy APIS to assign a policy for an endpoint, the"},{"line_number":26,"context_line":"current api associates that with the ID, not the URL.  However, there is no"},{"line_number":27,"context_line":"uniqueness constraint on the URLs, so the policy could potentially be"},{"line_number":28,"context_line":"different for endpoint_ids that are all the same server."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_63ab0376","line":26,"updated":"2015-06-17 20:43:39.000000000","message":"API","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"f4c458ea9a49a567d29816430e608be7dc6eab24","unresolved":false,"context_lines":[{"line_number":25,"context_line":"When using the endpoint policy APIS to assign a policy for an endpoint, the"},{"line_number":26,"context_line":"current api associates that with the ID, not the URL.  However, there is no"},{"line_number":27,"context_line":"uniqueness constraint on the URLs, so the policy could potentially be"},{"line_number":28,"context_line":"different for endpoint_ids that are all the same server."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Proposed Change"},{"line_number":31,"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":2,"id":"fa32b979_aedbf54d","line":28,"updated":"2015-06-18 23:53:25.000000000","message":"Why is that a problem?","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":31,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Change the policy endpoint binding to be per endpoint URL instead of endpoint"},{"line_number":34,"context_line":"id.  A call on the current API to Create association with endpoint"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoints/{endpoint_id}`"},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_83a88778","line":34,"updated":"2015-06-17 20:43:39.000000000","message":"ID and \u0027create an association\u0027","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"6139ee7260bc61c883f956ce8160e71c86873324","unresolved":false,"context_lines":[{"line_number":33,"context_line":"Change the policy endpoint binding to be per endpoint URL instead of endpoint"},{"line_number":34,"context_line":"id.  A call on the current API to Create association with endpoint"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoints/{endpoint_id}`"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Will instead modify the URL assignment.  If multiple calls are made"},{"line_number":39,"context_line":"against different endpoints that map to the same URL, the last call will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_0be8a5e1","line":36,"updated":"2015-06-29 18:28:46.000000000","message":"This got to be done at a per project or per domain basis for the reseller scenario.  For example, project_a got to be able to deploy its custom nova policy, and not affecting project_b.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"52de8d92dbb525d92f219b6434fb7b31e485dfa8","unresolved":false,"context_lines":[{"line_number":33,"context_line":"Change the policy endpoint binding to be per endpoint URL instead of endpoint"},{"line_number":34,"context_line":"id.  A call on the current API to Create association with endpoint"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoints/{endpoint_id}`"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Will instead modify the URL assignment.  If multiple calls are made"},{"line_number":39,"context_line":"against different endpoints that map to the same URL, the last call will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_4b95df3c","line":36,"in_reply_to":"ba3cc151_0be8a5e1","updated":"2015-07-01 16:15:22.000000000","message":"That is beyond the scope of what we are trying to accomplish here.  Project scoped policy is not even possible to discuss until we have a means to dynamically fetch and modify policy, but even then, we need to deal with the way that the policy would be fetched per project.  Project specific policy would probably not be per endpoint.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"4f4364e139d01a3e2b9fa30c637d2b1a0e510940","unresolved":false,"context_lines":[{"line_number":33,"context_line":"Change the policy endpoint binding to be per endpoint URL instead of endpoint"},{"line_number":34,"context_line":"id.  A call on the current API to Create association with endpoint"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoints/{endpoint_id}`"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Will instead modify the URL assignment.  If multiple calls are made"},{"line_number":39,"context_line":"against different endpoints that map to the same URL, the last call will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_e9c398eb","line":36,"in_reply_to":"ba3cc151_4b95df3c","updated":"2015-07-01 17:47:34.000000000","message":"I can draft a proposal, so we have something for discussion.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"b4e1cae18d28958b908c56b1f223d0be72e1d808","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Add a new API that is less surprising"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Add a new API for fetching the policy for an endpoint"},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_b408c32e","line":44,"updated":"2015-06-30 17:32:47.000000000","message":"1.  The newly uploaded policy needs to persist in a storage somewhere, and share among keystone nodes in an HA environment.\n\n2.  I like to see the ability to upload a policy for an endpoint for a project or a domain.\n\n3.  We need to define rules to enforce who gets to upload policy.  Can\u0027t let this be an administrative bottle neck where only the global admin gets to upload.  Perhaps, define an endpoint owner concept?","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Add a new API that is less surprising"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Add a new API for fetching the policy for an endpoint"},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_63f0e391","line":44,"updated":"2015-06-17 20:43:39.000000000","message":"It seems really strange that this would use a query parameter. If you have the endpoint ID and know the interface the API is on do you know the URL?","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"f4c458ea9a49a567d29816430e608be7dc6eab24","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Add a new API that is less surprising"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Add a new API for fetching the policy for an endpoint"},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_aea9b591","line":44,"in_reply_to":"fa32b979_63f0e391","updated":"2015-06-18 23:53:25.000000000","message":"Thought we don\u0027t do the extension namespace anymore so loose the \u0027OS\u003dENDPOINT-POLICY\u0027 stuff.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"b4e1cae18d28958b908c56b1f223d0be72e1d808","unresolved":false,"context_lines":[{"line_number":46,"context_line":"Add a new API for fetching the policy for an endpoint"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"`GET /OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"That returns only the single policy associated with the endpoint_url."},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_f15f6e0c","line":49,"updated":"2015-06-30 17:32:47.000000000","message":"Per project or domain here as well.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"f4c458ea9a49a567d29816430e608be7dc6eab24","unresolved":false,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Map from ID to URL in the client and call the old code."},{"line_number":64,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_4ec26954","line":61,"updated":"2015-06-18 23:53:25.000000000","message":"How about enhance endpoint groups to support URL filter? Then assign the policy to an endpoint group.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":71,"context_line":"---------------"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"These APIs themselves will have not effect on security.  Their use will"},{"line_number":74,"context_line":"enable the use of  Dynamic Policy in OpenStack, but that is out of the scope"},{"line_number":75,"context_line":"of this spec."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_8372c70f","line":74,"updated":"2015-06-17 20:43:39.000000000","message":"double spacing in there","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"0af949d50423fb716678150eeb14bf3dc392c19a","unresolved":false,"context_lines":[{"line_number":84,"context_line":"Other End User Impact"},{"line_number":85,"context_line":"---------------------"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"The Expected use of the PUT call is to set the policy for an endpoint."},{"line_number":88,"context_line":"This version is expected to become the default, and the old version will be"},{"line_number":89,"context_line":"deprecated."},{"line_number":90,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_e3571358","line":87,"updated":"2015-06-17 20:43:39.000000000","message":"expected","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"78d3185c2555375c1b5ee1a509b4c8355e64a093","unresolved":false,"context_lines":[{"line_number":135,"context_line":"Documentation Impact"},{"line_number":136,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"API will need to be documented"},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"References"},{"line_number":141,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_484cefc7","line":138,"updated":"2015-06-17 14:54:51.000000000","message":"that needs to include here: http://developer.openstack.org/api-ref-identity-v3-ext.html\n\nnot just here: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-os-endpoint-policy.html","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"535374043ff374bef3152f8a9ab54c7a5e58ab7a","unresolved":false,"context_lines":[{"line_number":135,"context_line":"Documentation Impact"},{"line_number":136,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"API will need to be documented"},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"References"},{"line_number":141,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_4415b3e2","line":138,"in_reply_to":"fa32b979_484cefc7","updated":"2015-06-17 17:00:36.000000000","message":"I think we are merging them, but, yes.","commit_id":"7e57c124a59dca4b28944fbe7be9573f9020d916"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"082cb72569f0547237838e1e694ce25d8b9ca5eb","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Add a new API that associates a policy with and endpoint URL:"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Add a new API for fetching the policy for an endpoint that returns only the single policy associated with the endpoint_url:"},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_158774d8","line":35,"updated":"2015-07-05 14:29:07.000000000","message":"Is this is the first example of using query parameters for anything other than a GET ?","commit_id":"926bbfcf6a1f66b71fc9f6b79f44b87a0eebad8c"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"3d232ff77a45ba83c8bbea40bed1a306bb5efcba","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Add a new API that associates a policy with and endpoint URL:"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoint?endpoint_url\u003d\u003cencodedURL\u003e`"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Add a new API for fetching the policy for an endpoint that returns only the single policy associated with the endpoint_url:"},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_eab07b45","line":35,"in_reply_to":"ba3cc151_158774d8","updated":"2015-07-08 03:22:39.000000000","message":"I think so, but it is well supported by the HTTP spec;  we need to keep the parameter outside the payload in this case.","commit_id":"926bbfcf6a1f66b71fc9f6b79f44b87a0eebad8c"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"082cb72569f0547237838e1e694ce25d8b9ca5eb","unresolved":false,"context_lines":[{"line_number":52,"context_line":""},{"line_number":53,"context_line":"A call on the current API to Create association with endpoint_id:"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoints/{endpoint_id}`"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"will instead modify the URL assignment.  If multiple calls are made"},{"line_number":58,"context_line":"against different endpoints that map to the same URL, the last call will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_95738415","line":55,"updated":"2015-07-05 14:29:07.000000000","message":"I wonder if we simply don\u0027t allow this if there is a policy set for the url?","commit_id":"926bbfcf6a1f66b71fc9f6b79f44b87a0eebad8c"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"3d232ff77a45ba83c8bbea40bed1a306bb5efcba","unresolved":false,"context_lines":[{"line_number":52,"context_line":""},{"line_number":53,"context_line":"A call on the current API to Create association with endpoint_id:"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"`PUT /policies/{policy_id}/OS-ENDPOINT-POLICY/endpoints/{endpoint_id}`"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"will instead modify the URL assignment.  If multiple calls are made"},{"line_number":58,"context_line":"against different endpoints that map to the same URL, the last call will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_2a5503c1","line":55,"in_reply_to":"ba3cc151_95738415","updated":"2015-07-08 03:22:39.000000000","message":"It unfortunate, but I think we need to have the vagaries here to allow people to fix changes that surprise them.  Not allowing it would make things harder for people that wanted the old behavior and messed it up.","commit_id":"926bbfcf6a1f66b71fc9f6b79f44b87a0eebad8c"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"082cb72569f0547237838e1e694ce25d8b9ca5eb","unresolved":false,"context_lines":[{"line_number":57,"context_line":"will instead modify the URL assignment.  If multiple calls are made"},{"line_number":58,"context_line":"against different endpoints that map to the same URL, the last call will"},{"line_number":59,"context_line":"set it for all the endpoint_ids."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_35edd88e","line":60,"updated":"2015-07-05 14:29:07.000000000","message":"We probably also need a version of:\n\nGET /endpoints/{endpoint_id}/OS-ENDPOINT-POLICY/policy\n\nthat works for a url.\n\nQuestion: by definition, are all the endpoints associated with a url guaranteed to be in the same region and/or of a given service type?","commit_id":"926bbfcf6a1f66b71fc9f6b79f44b87a0eebad8c"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"3d232ff77a45ba83c8bbea40bed1a306bb5efcba","unresolved":false,"context_lines":[{"line_number":57,"context_line":"will instead modify the URL assignment.  If multiple calls are made"},{"line_number":58,"context_line":"against different endpoints that map to the same URL, the last call will"},{"line_number":59,"context_line":"set it for all the endpoint_ids."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_8a644fb9","line":60,"in_reply_to":"ba3cc151_35edd88e","updated":"2015-07-08 03:22:39.000000000","message":"Dn\u0027t know that we need it, as it is pretty well covered by the above API.  If we find we do need it, we can add it later.\n\nThe URL has to be handled buy code;  there would be no way the exact same URL could be both a Nova and a Glance endpoint.\n\nAll endpoints for the same URL will be in the same region, but even if they were not, the code would work:  the endpoint+_policy spec already states the order of resolution, and this would not change any of that.  Endpoint would trump region anyway.","commit_id":"926bbfcf6a1f66b71fc9f6b79f44b87a0eebad8c"}]}
