)]}'
{"doc/source/contributor/vision-reflection.rst":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"119998583aade30f34ac50ffe6bb65e7964c940b","unresolved":false,"context_lines":[{"line_number":2,"context_line":"Vision Reflection"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"In late-2018, the OpenStack Technical composed a"},{"line_number":6,"context_line":"`technical vision \u003chttps://governance.openstack.org/tc/reference/technical-vision.html\u003e`_"},{"line_number":7,"context_line":"of what OpenStack clouds should look like. This document compares the state of"},{"line_number":8,"context_line":"placement relative to that vision to provide some guidance on broad stroke ways"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_37c24887","line":5,"range":{"start_line":5,"start_character":28,"end_line":5,"end_character":37},"updated":"2019-01-11 16:41:34.000000000","message":"Technical Committee?","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0d438a66ff3fcedca8f892a612728f5571b965e8","unresolved":false,"context_lines":[{"line_number":2,"context_line":"Vision Reflection"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"In late-2018, the OpenStack Technical composed a"},{"line_number":6,"context_line":"`technical vision \u003chttps://governance.openstack.org/tc/reference/technical-vision.html\u003e`_"},{"line_number":7,"context_line":"of what OpenStack clouds should look like. This document compares the state of"},{"line_number":8,"context_line":"placement relative to that vision to provide some guidance on broad stroke ways"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_173e2429","line":5,"range":{"start_line":5,"start_character":28,"end_line":5,"end_character":37},"in_reply_to":"bfdaf3ff_37c24887","updated":"2019-01-11 16:47:46.000000000","message":"yeah, that\u0027s a pasto from the ironic version of this doc","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"119998583aade30f34ac50ffe6bb65e7964c940b","unresolved":false,"context_lines":[{"line_number":25,"context_line":"theory, anything can talk to it, enabling the self-service and application"},{"line_number":26,"context_line":"control that define a cloud. However, at the moment the data managed by"},{"line_number":27,"context_line":"placement is considered for administrators only. This policy could be changed,"},{"line_number":28,"context_line":"but doing so would be a dramatic adjustment in the scope of who placement is"},{"line_number":29,"context_line":"for and what it does. Since placement has not yet fully satisfied its original"},{"line_number":30,"context_line":"vision to clarify and ease cloud resource allocation such a change should be"},{"line_number":31,"context_line":"considered secondary to completing the original goals."}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_17738482","line":28,"range":{"start_line":28,"start_character":60,"end_line":28,"end_character":63},"updated":"2019-01-11 16:41:34.000000000","message":"\u0027whom\u0027, to be persnickety. (Don\u0027t fix this.)","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0d438a66ff3fcedca8f892a612728f5571b965e8","unresolved":false,"context_lines":[{"line_number":25,"context_line":"theory, anything can talk to it, enabling the self-service and application"},{"line_number":26,"context_line":"control that define a cloud. However, at the moment the data managed by"},{"line_number":27,"context_line":"placement is considered for administrators only. This policy could be changed,"},{"line_number":28,"context_line":"but doing so would be a dramatic adjustment in the scope of who placement is"},{"line_number":29,"context_line":"for and what it does. Since placement has not yet fully satisfied its original"},{"line_number":30,"context_line":"vision to clarify and ease cloud resource allocation such a change should be"},{"line_number":31,"context_line":"considered secondary to completing the original goals."}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_d74e5cc0","line":28,"range":{"start_line":28,"start_character":60,"end_line":28,"end_character":63},"in_reply_to":"bfdaf3ff_17738482","updated":"2019-01-11 16:47:46.000000000","message":"I considered it, and then decided since I was dangling the \"for\", I\u0027d stick with who and let it ride.","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"119998583aade30f34ac50ffe6bb65e7964c940b","unresolved":false,"context_lines":[{"line_number":42,"context_line":"useful. To some extent this is already done with the way nova requires specific"},{"line_number":43,"context_line":"placement microversions, and for placement to be upgraded in advance of nova."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"As yet, placement provides no dedicated for partitioning its resource providers"},{"line_number":46,"context_line":"amongst regions. Aggregates can be used for this purpose but this is"},{"line_number":47,"context_line":"potentially cumbersome in the face of multi-region use cases where a single"},{"line_number":48,"context_line":"placement service is used to manage resources in several clouds. This is an"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_17f864c2","line":45,"range":{"start_line":45,"start_character":30,"end_line":45,"end_character":43},"updated":"2019-01-11 16:41:34.000000000","message":"missing noun?","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0d438a66ff3fcedca8f892a612728f5571b965e8","unresolved":false,"context_lines":[{"line_number":42,"context_line":"useful. To some extent this is already done with the way nova requires specific"},{"line_number":43,"context_line":"placement microversions, and for placement to be upgraded in advance of nova."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"As yet, placement provides no dedicated for partitioning its resource providers"},{"line_number":46,"context_line":"amongst regions. Aggregates can be used for this purpose but this is"},{"line_number":47,"context_line":"potentially cumbersome in the face of multi-region use cases where a single"},{"line_number":48,"context_line":"placement service is used to manage resources in several clouds. This is an"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_d7209cfa","line":45,"range":{"start_line":45,"start_character":30,"end_line":45,"end_character":43},"in_reply_to":"bfdaf3ff_17f864c2","updated":"2019-01-11 16:47:46.000000000","message":"mechanism is what I was probably thinking","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"119998583aade30f34ac50ffe6bb65e7964c940b","unresolved":false,"context_lines":[{"line_number":48,"context_line":"placement service is used to manage resources in several clouds. This is an"},{"line_number":49,"context_line":"area that is already under consideration, and would bring placement closer to"},{"line_number":50,"context_line":"matching the \"partitioning\" aspect of the vision document."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Design Goals"},{"line_number":53,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_37e32808","line":51,"updated":"2019-01-11 16:41:34.000000000","message":"Is it worth mentioning that placement has potential usefulness outside of OpenStack, and such use cases should be considered before making architectural decisions whose purpose is purely closer alignment with OpenStack\u0027s vision?","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0d438a66ff3fcedca8f892a612728f5571b965e8","unresolved":false,"context_lines":[{"line_number":48,"context_line":"placement service is used to manage resources in several clouds. This is an"},{"line_number":49,"context_line":"area that is already under consideration, and would bring placement closer to"},{"line_number":50,"context_line":"matching the \"partitioning\" aspect of the vision document."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Design Goals"},{"line_number":53,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_f7728011","line":51,"in_reply_to":"bfdaf3ff_37e32808","updated":"2019-01-11 16:47:46.000000000","message":"I thought such things might fit better in the goals document, since this document is supposed to be \"how well does placement fit with openstack being openstack\".\n\n?","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"119998583aade30f34ac50ffe6bb65e7964c940b","unresolved":false,"context_lines":[{"line_number":55,"context_line":"Placement already maps well to several of the design goals in the vision"},{"line_number":56,"context_line":"document, adhering to fairly standard methods for scalability, reliability,"},{"line_number":57,"context_line":"customization, and flexible utilization models. It does this by being a simple"},{"line_number":58,"context_line":"web app over a database and not much more. We should strive to keep this."}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_77ba10df","line":58,"updated":"2019-01-11 16:41:34.000000000","message":"This would be a good place (instead of or in addition to L15) to reference the goals doc.","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0d438a66ff3fcedca8f892a612728f5571b965e8","unresolved":false,"context_lines":[{"line_number":55,"context_line":"Placement already maps well to several of the design goals in the vision"},{"line_number":56,"context_line":"document, adhering to fairly standard methods for scalability, reliability,"},{"line_number":57,"context_line":"customization, and flexible utilization models. It does this by being a simple"},{"line_number":58,"context_line":"web app over a database and not much more. We should strive to keep this."}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfdaf3ff_1755c450","line":58,"in_reply_to":"bfdaf3ff_77ba10df","updated":"2019-01-11 16:47:46.000000000","message":"sure","commit_id":"fdeac2b8bad06a9b1e2ee4ba484ad6d58707f8fa"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"47ec1d08d7b872ae6904cce7963753209c54b196","unresolved":false,"context_lines":[{"line_number":21,"context_line":"The Pillars of Cloud"},{"line_number":22,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"The sole interface to the placement service is an HTTP API, meaning that in"},{"line_number":25,"context_line":"theory, anything can talk to it, enabling the self-service and application"},{"line_number":26,"context_line":"control that define a cloud. However, at the moment the data managed by"},{"line_number":27,"context_line":"placement is considered for administrators only. This policy could be changed,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_02922aa0","line":24,"range":{"start_line":24,"start_character":4,"end_line":24,"end_character":8},"updated":"2019-02-08 01:20:24.000000000","message":"Well there is also PlacementDirect but yeah.","commit_id":"c254d48321e3c31731233bd56f6e09776c0ca7e8"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"a7a3f0d3d4a9e5107ec92140545e468930b82bf4","unresolved":false,"context_lines":[{"line_number":21,"context_line":"The Pillars of Cloud"},{"line_number":22,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"The sole interface to the placement service is an HTTP API, meaning that in"},{"line_number":25,"context_line":"theory, anything can talk to it, enabling the self-service and application"},{"line_number":26,"context_line":"control that define a cloud. However, at the moment the data managed by"},{"line_number":27,"context_line":"placement is considered for administrators only. This policy could be changed,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_ee590d5b","line":24,"range":{"start_line":24,"start_character":4,"end_line":24,"end_character":8},"in_reply_to":"9fdfeff1_02922aa0","updated":"2019-02-08 10:58:21.000000000","message":"My attitude there was that since nothing yet uses it, it doesn\u0027t really exist. We haven\u0027t proven it out. Also, what it does is allow people to use HTTP to talk to placement without having to \"turn the placement web server on\".\n\nSo effectively the it\u0027s still the HTTP interface...?","commit_id":"c254d48321e3c31731233bd56f6e09776c0ca7e8"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"47ec1d08d7b872ae6904cce7963753209c54b196","unresolved":false,"context_lines":[{"line_number":24,"context_line":"The sole interface to the placement service is an HTTP API, meaning that in"},{"line_number":25,"context_line":"theory, anything can talk to it, enabling the self-service and application"},{"line_number":26,"context_line":"control that define a cloud. However, at the moment the data managed by"},{"line_number":27,"context_line":"placement is considered for administrators only. This policy could be changed,"},{"line_number":28,"context_line":"but doing so would be a dramatic adjustment in the scope of who placement is"},{"line_number":29,"context_line":"for and what it does. Since placement has not yet fully satisfied its original"},{"line_number":30,"context_line":"vision to clarify and ease cloud resource allocation such a change should be"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_e2db667a","line":27,"range":{"start_line":27,"start_character":54,"end_line":27,"end_character":60},"updated":"2019-02-08 01:20:24.000000000","message":"Not to be confusing with the literal policy rules on the API which can be modified for non-admins, but sure, I get you.","commit_id":"c254d48321e3c31731233bd56f6e09776c0ca7e8"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"c7defd8d28377f92a3f4286476f66d185b3402ef","unresolved":false,"context_lines":[{"line_number":25,"context_line":"theory, anything can talk to it, enabling the self-service and application"},{"line_number":26,"context_line":"control that define a cloud. However, at the moment the data managed by"},{"line_number":27,"context_line":"placement is considered for administrators only. This policy could be changed,"},{"line_number":28,"context_line":"but doing so would be a dramatic adjustment in the scope of who placement is"},{"line_number":29,"context_line":"for and what it does. Since placement has not yet fully satisfied its original"},{"line_number":30,"context_line":"vision to clarify and ease cloud resource allocation such a change should be"},{"line_number":31,"context_line":"considered secondary to completing the original goals."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bfdaf3ff_259bd3c9","line":28,"range":{"start_line":28,"start_character":57,"end_line":28,"end_character":76},"updated":"2019-01-14 15:08:24.000000000","message":"\"who\"? A bit of an anthropomorphization, no?","commit_id":"c254d48321e3c31731233bd56f6e09776c0ca7e8"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"263297facaa2363eea367738097a84f8bd7aa768","unresolved":false,"context_lines":[{"line_number":25,"context_line":"theory, anything can talk to it, enabling the self-service and application"},{"line_number":26,"context_line":"control that define a cloud. However, at the moment the data managed by"},{"line_number":27,"context_line":"placement is considered for administrators only. This policy could be changed,"},{"line_number":28,"context_line":"but doing so would be a dramatic adjustment in the scope of who placement is"},{"line_number":29,"context_line":"for and what it does. Since placement has not yet fully satisfied its original"},{"line_number":30,"context_line":"vision to clarify and ease cloud resource allocation such a change should be"},{"line_number":31,"context_line":"considered secondary to completing the original goals."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bfdaf3ff_6807721e","line":28,"range":{"start_line":28,"start_character":57,"end_line":28,"end_character":76},"in_reply_to":"bfdaf3ff_259bd3c9","updated":"2019-01-14 16:13:49.000000000","message":"I did mean \"who\". It refers back to \"administrators\" and I intentionally separated \"who it is for\" and \"what it does\" in this clause.\n\nBut if you prefer I can change that. Don\u0027t want to hold this up on what is mostly inconsequentials.","commit_id":"c254d48321e3c31731233bd56f6e09776c0ca7e8"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"47ec1d08d7b872ae6904cce7963753209c54b196","unresolved":false,"context_lines":[{"line_number":36,"context_line":"Placement uses microversions to help manage interoperability and bi-directional"},{"line_number":37,"context_line":"compatibility. Because placement has used microversions from the very start a"},{"line_number":38,"context_line":"great deal of the valuable functionality is only available in an opt-in"},{"line_number":39,"context_line":"fashion. In fact, it would be accurate to say that a placement service at the"},{"line_number":40,"context_line":"default microversion is incapable of being a placement service. We may wish to"},{"line_number":41,"context_line":"evaluate (and publish) if there is a minimum microversion at which placement is"},{"line_number":42,"context_line":"useful. To some extent this is already done with the way nova requires specific"},{"line_number":43,"context_line":"placement microversions, and for placement to be upgraded in advance of nova."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_c2e0a229","line":40,"range":{"start_line":39,"start_character":9,"end_line":40,"end_character":63},"updated":"2019-02-08 01:20:24.000000000","message":"I\u0027m not really sure what this means - we have allocations and inventories and allocation candidates at 1.0 don\u0027t we?","commit_id":"c254d48321e3c31731233bd56f6e09776c0ca7e8"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"a7a3f0d3d4a9e5107ec92140545e468930b82bf4","unresolved":false,"context_lines":[{"line_number":36,"context_line":"Placement uses microversions to help manage interoperability and bi-directional"},{"line_number":37,"context_line":"compatibility. Because placement has used microversions from the very start a"},{"line_number":38,"context_line":"great deal of the valuable functionality is only available in an opt-in"},{"line_number":39,"context_line":"fashion. In fact, it would be accurate to say that a placement service at the"},{"line_number":40,"context_line":"default microversion is incapable of being a placement service. We may wish to"},{"line_number":41,"context_line":"evaluate (and publish) if there is a minimum microversion at which placement is"},{"line_number":42,"context_line":"useful. To some extent this is already done with the way nova requires specific"},{"line_number":43,"context_line":"placement microversions, and for placement to be upgraded in advance of nova."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_8227f5b6","line":40,"range":{"start_line":39,"start_character":9,"end_line":40,"end_character":63},"in_reply_to":"9fdfeff1_c2e0a229","updated":"2019-02-08 10:58:21.000000000","message":"Filtering by resources on /resource_providers was 1.4, aggregates 1.3.\n\nAllocation candidates is 1.10\n\nSo while you could write allocations in 1.0, you couldn\u0027t filter the resource providers in any useful way until 1.4, and until 1.10 you had to create the allocations yourself rather than using those provided by allocation_candidates.\n\n(never mind anything to do with traits or custom resource classes)","commit_id":"c254d48321e3c31731233bd56f6e09776c0ca7e8"}]}