)]}'
{"specs/backlog/policy-unified.rst":[{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"c35fd3080148fed222c39a4bea2aa88ef04413b9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3acd31a7_b247774a","updated":"2015-05-04 17:11:05.000000000","message":"From the \u0027Dynamic Policy Overview\u0027:\n\nDoug Hellmann\t\tApr 30 2:20 PM\nWhere would that file live in git and how would it be updated as new projects come into the ecosystem?","commit_id":"a54d120041fe2fce30cf7e20ee38a7671e7b50ce"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"17b4715c4fb5e01945c3b999d08eee973306736c","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Unified default policy file"},{"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"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/policy-unified\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Unify all of the policy files from the known set of services into a single"}],"source_content_type":"text/x-rst","patch_set":5,"id":"da9b358b_de48025e","line":11,"updated":"2015-03-30 22:50:34.000000000","message":"s/bp example/...more descriptive name.../","commit_id":"a54d120041fe2fce30cf7e20ee38a7671e7b50ce"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"185aad7f4d5e4b229430b3c5aaa4c10c9f48cddd","unresolved":false,"context_lines":[{"line_number":36,"context_line":"service names. This pattern can be extended to all of the services.  This"},{"line_number":37,"context_line":"allows the unification of the policy rules into a single file, sharing common"},{"line_number":38,"context_line":"definition."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"While endpoint specific policy is supported, it can be written as"},{"line_number":42,"context_line":"a diff from the base policy file.  Building a merging mechanism to deal with"}],"source_content_type":"text/x-rst","patch_set":5,"id":"bab921fb_4f93235c","line":39,"updated":"2015-04-23 17:14:53.000000000","message":"A challenge I see in a big corporation is that the admin for service A needs to edit this unified policy file, but needs to wait until the admin for service B to finish first.  This assumes that policy changes goes to the unified policy file first, then the db.\n\nIn my opinion, once policies are stored in the db, there is no point of maintaining the physical policy file(s).  A tool should made available for admins to modify policies stored in the db.","commit_id":"a54d120041fe2fce30cf7e20ee38a7671e7b50ce"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"8a4a9911e0d7fb115ddccee0fc566a4d82084787","unresolved":false,"context_lines":[{"line_number":41,"context_line":"While endpoint specific policy is supported, it can be written as"},{"line_number":42,"context_line":"a diff from the base policy file.  Building a merging mechanism to deal with"},{"line_number":43,"context_line":"that use case is not part of this specification."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"},{"line_number":47,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5afe65bd_4eac87ed","line":44,"updated":"2015-06-01 16:40:43.000000000","message":"If I recall correctly, there is going to be a way for existing deployments to remain on the existing non-unified policy for sometime.  It might be a config flag or something else.  The idea needs to be captured somewhere.\n\nThis is to address a scenario where a deployment has customized non-unified policy files, and not ready to move to unified policy file.","commit_id":"a54d120041fe2fce30cf7e20ee38a7671e7b50ce"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"185aad7f4d5e4b229430b3c5aaa4c10c9f48cddd","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Leave it as is."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Build a mechanism to compose individual policy filkes out of component parts."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":5,"id":"bab921fb_ac7c0d73","line":51,"updated":"2015-04-23 17:14:53.000000000","message":"s/filkes/files\n\ns/\"component parts\"/\"each individual service\" or clarify component parts.","commit_id":"a54d120041fe2fce30cf7e20ee38a7671e7b50ce"},{"author":{"_account_id":13063,"name":"WEI CHEN","email":"dave.jungler@gmail.com","username":"wei.d.chen"},"change_message_id":"a4e542411234405b8c8a0b111edd51c5e6454652","unresolved":false,"context_lines":[{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/policy-unified\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Unify all of the policy files from the known set of services into a single"},{"line_number":15,"context_line":"file.  Use common definitions for what is meant by admin at the global, domain,"},{"line_number":16,"context_line":"and service level.  Deconflict between endpoints by the api-name"},{"line_number":17,"context_line":"(identity, compute) for each of the policy enforcement points."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5afe65bd_fbe9691b","line":14,"updated":"2015-06-03 08:26:26.000000000","message":"Echo David J Hu\u0027s comments in the previous patch, we need to consider how to slove the resource competition for this centralized policy file.\n- lock the file before updating.\n- prohibit update from each service, this seems more like a default policy.\n- this unified policy is also stored in the DB, so DB could manage it well.","commit_id":"9ff16abeebff968e78ff013415e2a3574846d687"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"2fb3e20dde8cab6870c0a9099e217e1f4247ac55","unresolved":false,"context_lines":[{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/policy-unified\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Unify all of the policy files from the known set of services into a single"},{"line_number":15,"context_line":"file.  Use common definitions for what is meant by admin at the global, domain,"},{"line_number":16,"context_line":"and service level.  Deconflict between endpoints by the api-name"},{"line_number":17,"context_line":"(identity, compute) for each of the policy enforcement points."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5afe65bd_5f84c9d2","line":14,"in_reply_to":"5afe65bd_fbe9691b","updated":"2015-06-03 20:25:35.000000000","message":"This is the default out of a git repo, not a dynamic policy.  There are no race conditions, as it is not modifiable.","commit_id":"9ff16abeebff968e78ff013415e2a3574846d687"},{"author":{"_account_id":13063,"name":"WEI CHEN","email":"dave.jungler@gmail.com","username":"wei.d.chen"},"change_message_id":"a4e542411234405b8c8a0b111edd51c5e6454652","unresolved":false,"context_lines":[{"line_number":26,"context_line":"between them.  Instead, they should all share a common definition."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Horizon currently attempts to maintain a policy file for each project in order"},{"line_number":29,"context_line":"to dymanically generate the UI.  This file would replace those individual"},{"line_number":30,"context_line":"policy files."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5afe65bd_6596f9f1","line":29,"updated":"2015-06-03 08:26:26.000000000","message":"s/This file/This unified policy file","commit_id":"9ff16abeebff968e78ff013415e2a3574846d687"},{"author":{"_account_id":13063,"name":"WEI CHEN","email":"dave.jungler@gmail.com","username":"wei.d.chen"},"change_message_id":"a4e542411234405b8c8a0b111edd51c5e6454652","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Leave it as is."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Build a mechanism to compose individual policy filkes out of component parts."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5afe65bd_852b3594","line":51,"updated":"2015-06-03 08:26:26.000000000","message":"s/filkes/file, typo?","commit_id":"9ff16abeebff968e78ff013415e2a3574846d687"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"2fb3e20dde8cab6870c0a9099e217e1f4247ac55","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Leave it as is."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Build a mechanism to compose individual policy filkes out of component parts."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5afe65bd_ff693526","line":51,"in_reply_to":"5afe65bd_852b3594","updated":"2015-06-03 20:25:35.000000000","message":"Done","commit_id":"9ff16abeebff968e78ff013415e2a3574846d687"}],"specs/kilo/policy-unified.rst":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"14c0394f6b396ef6caf92f27d45ac71d90284e51","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"While endpoint specific policy is supported, it can be written as"},{"line_number":42,"context_line":"a diff from the base policy file.  Building a merging mechanism to deal with"},{"line_number":43,"context_line":"that use case is not part of this specification."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_916a6e18","line":43,"updated":"2014-12-02 21:01:50.000000000","message":"As an alternative, couldn\u0027t a callback mechanism be put in place and the policy file is fetched again? \n\nWith always maintaining the diffs and merging them, the original policy file is only ever fetched once, right?","commit_id":"ee242dcbc8715b1e51d09449d6e1fc57aea2c9f8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"14c0394f6b396ef6caf92f27d45ac71d90284e51","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Leave it as is."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Build a mechanism to compose individual policy filkes out of component parts."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_91518e64","line":51,"updated":"2014-12-02 21:01:50.000000000","message":"filkes?","commit_id":"ee242dcbc8715b1e51d09449d6e1fc57aea2c9f8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"14c0394f6b396ef6caf92f27d45ac71d90284e51","unresolved":false,"context_lines":[{"line_number":142,"context_line":"Work items or tasks -- break the feature up into the things that need to be"},{"line_number":143,"context_line":"done to implement it. Those parts might end up being done by different people,"},{"line_number":144,"context_line":"but we\u0027re mostly trying to understand the timeline for implementation."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"Dependencies"},{"line_number":148,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_d1f5d651","line":145,"updated":"2014-12-02 21:01:50.000000000","message":"When new operations are added to services, is it on us to support adding those operations and permissions? \n\n    compute:server_sweet_new_feature \u003cpolicy mapping\u003e","commit_id":"ee242dcbc8715b1e51d09449d6e1fc57aea2c9f8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"14c0394f6b396ef6caf92f27d45ac71d90284e51","unresolved":false,"context_lines":[{"line_number":147,"context_line":"Dependencies"},{"line_number":148,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Depends on policy-fetch.rst"},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Documentation Impact"},{"line_number":153,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_713fc225","line":150,"updated":"2014-12-02 21:01:50.000000000","message":"this? \n\nhttps://review.openstack.org/#/c/134657/","commit_id":"ee242dcbc8715b1e51d09449d6e1fc57aea2c9f8"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"7ee72d70cb3313c09bc3dc1d04471e34f55735fd","unresolved":false,"context_lines":[{"line_number":54,"context_line":"Security Impact"},{"line_number":55,"context_line":"---------------"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Describe any potential security impact on the system.  Some of the items to"},{"line_number":58,"context_line":"consider include:"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"* Does this change touch sensitive data such as tokens, keys, or user data?"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_a35d7e17","line":57,"updated":"2014-12-18 14:39:28.000000000","message":"these questions are not intended to provide a question-answer format wherein you complete a questionnaire like it\u0027s some sort of doctor\u0027s office form. they\u0027re intended to motivate a thoughtful discussion and drive you to begin considering several angles on the subject. please put some thought into these specs, as they\u0027re all just incomplete thoughts, otherwise.","commit_id":"6e7f19eda62d2893b5d3af1ab9afbeb82a612302"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"10d9f75e262ca55a942484938fe7e8833bc5665f","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Unified default policy file"},{"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"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/policy-unified\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Unify all of the policy files from the known set of services into a single"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_c00bce20","line":11,"updated":"2015-01-19 13:34:47.000000000","message":"s/example/policy-unified\u003e","commit_id":"8ece0ff191b02cc1fc832717ec6a46f47bde86f7"}]}