)]}'
{"proposals/base-services.rst":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8ad3eb53b23e18d8cd67424e6328e43e378314bd","unresolved":false,"context_lines":[{"line_number":51,"context_line":"  databases are supported."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* An oslo.messaging-compatible message queue (RabbitMQ)"},{"line_number":54,"context_line":"  OpenStack components communicate between each other using message queues,"},{"line_number":55,"context_line":"  though oslo.messaging as an indirection layer. While most OpenStack"},{"line_number":56,"context_line":"  deployments use RabbitMQ, other message queues are supported."},{"line_number":57,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_a462bcab","line":54,"updated":"2016-12-08 11:34:22.000000000","message":"This could be read and inter project communication being via message queues (which is sometimes true) and not include components within projects (e.g, api\u003c-\u003econductor\u003c-\u003ecompute in nova).\n\nAlso it is a bit prescriptive; there is also communication that happens via other methods, including HTTP.\n\nSo it might make more sense to be a bit more explicit:\n\nSome inter-process and inter-service communication in OpenStack components is accomplished using message queues.","commit_id":"bf3ff38c4f363fd907d8897ad8b0067c16851120"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8ad3eb53b23e18d8cd67424e6328e43e378314bd","unresolved":false,"context_lines":[{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* An oslo.messaging-compatible message queue (RabbitMQ)"},{"line_number":54,"context_line":"  OpenStack components communicate between each other using message queues,"},{"line_number":55,"context_line":"  though oslo.messaging as an indirection layer. While most OpenStack"},{"line_number":56,"context_line":"  deployments use RabbitMQ, other message queues are supported."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_c41fb859","line":55,"updated":"2016-12-08 11:34:22.000000000","message":"through?","commit_id":"bf3ff38c4f363fd907d8897ad8b0067c16851120"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8ad3eb53b23e18d8cd67424e6328e43e378314bd","unresolved":false,"context_lines":[{"line_number":58,"context_line":"* Keystone"},{"line_number":59,"context_line":"  OpenStack Keystone handles AuthN/AuthZ for OpenStack components. Those can"},{"line_number":60,"context_line":"  therefore assume that Keystone will be present to handle that role for them"},{"line_number":61,"context_line":"  and validate authentication tokens that are presented to them."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Narrow or wide base services"},{"line_number":64,"context_line":"----------------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_0420d048","line":61,"updated":"2016-12-08 11:34:22.000000000","message":"This second sentence is overly complex. maybe:\n\nDeployments can assume that Keystone will be present to perform that role.","commit_id":"bf3ff38c4f363fd907d8897ad8b0067c16851120"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8ad3eb53b23e18d8cd67424e6328e43e378314bd","unresolved":false,"context_lines":[{"line_number":80,"context_line":"featureful options are supported in mainline code, and only to the point"},{"line_number":81,"context_line":"where they provide useful choice. As a result of this, untested or"},{"line_number":82,"context_line":"non-functional or useless options are getting pruned, to focus on a"},{"line_number":83,"context_line":"limited set of options. That allows to give deployers some choice while"},{"line_number":84,"context_line":"keeping development cost/distraction under control."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_c4aa5885","line":83,"updated":"2016-12-08 11:34:22.000000000","message":"s/allows to give/gives/","commit_id":"bf3ff38c4f363fd907d8897ad8b0067c16851120"}]}
