)]}'
{"reference/base-services.rst":[{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"118083513090bcddd08c8e2368627ee775f3c947","unresolved":false,"context_lines":[{"line_number":26,"context_line":"  other message queues are supported."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"**Etcd**"},{"line_number":29,"context_line":"  OpenStack components can use Etcd, a distributed reliable key-value store"},{"line_number":30,"context_line":"  for distributed key locking, storing configuration, keeping track of"},{"line_number":31,"context_line":"  service live-ness and other scenarios."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_03872664","line":29,"range":{"start_line":29,"start_character":23,"end_line":29,"end_character":26},"updated":"2017-05-24 10:40:29.000000000","message":"In keeping with the traditional distinction between \u0027may\u0027 and \u0027shall\u0027, (may is optional, shall is prescriptive), the use of the word \u0027can\u0027 is considered to be ambiguous.\n\nI would like to propose that this be changed to \u0027may\u0027.","commit_id":"7fc61ccbd37edc148b8d8928b5866f3f6f9bcebe"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"0206f62a3c9b9420844db749582de9621dd8fc2f","unresolved":false,"context_lines":[{"line_number":26,"context_line":"  other message queues are supported."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"**Etcd**"},{"line_number":29,"context_line":"  OpenStack components can use Etcd, a distributed reliable key-value store"},{"line_number":30,"context_line":"  for distributed key locking, storing configuration, keeping track of"},{"line_number":31,"context_line":"  service live-ness and other scenarios."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_87921b56","line":29,"range":{"start_line":29,"start_character":23,"end_line":29,"end_character":26},"in_reply_to":"ff0f0b1f_03872664","updated":"2017-05-24 14:45:02.000000000","message":"Done","commit_id":"7fc61ccbd37edc148b8d8928b5866f3f6f9bcebe"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"118083513090bcddd08c8e2368627ee775f3c947","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  OpenStack components can use Etcd, a distributed reliable key-value store"},{"line_number":30,"context_line":"  for distributed key locking, storing configuration, keeping track of"},{"line_number":31,"context_line":"  service live-ness and other scenarios."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"**Keystone**"},{"line_number":34,"context_line":"  Keystone handles AuthN/AuthZ for OpenStack components."},{"line_number":35,"context_line":"  Deployments can assume that Keystone will be present to perform that role."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_c3f12e03","line":32,"updated":"2017-05-24 10:40:29.000000000","message":"it would be beneficial if some clear indication on naming of directories is also provided here. we have got away without such a thing in oslo.db compatible database, but it would be good (for example) if the directory was named the same as the project or the oslo.db database with the explicit understanding that each directory is viewed as internal to a project. I would hate for tools (like say a service wellness tool) to assume that it can look at multiple directories and expect good things would happen.","commit_id":"7fc61ccbd37edc148b8d8928b5866f3f6f9bcebe"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"0206f62a3c9b9420844db749582de9621dd8fc2f","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  OpenStack components can use Etcd, a distributed reliable key-value store"},{"line_number":30,"context_line":"  for distributed key locking, storing configuration, keeping track of"},{"line_number":31,"context_line":"  service live-ness and other scenarios."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"**Keystone**"},{"line_number":34,"context_line":"  Keystone handles AuthN/AuthZ for OpenStack components."},{"line_number":35,"context_line":"  Deployments can assume that Keystone will be present to perform that role."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_a7975f48","line":32,"in_reply_to":"ff0f0b1f_43f2be9b","updated":"2017-05-24 14:45:02.000000000","message":"Agree with Bogdan","commit_id":"7fc61ccbd37edc148b8d8928b5866f3f6f9bcebe"},{"author":{"_account_id":6926,"name":"Bogdan Dobrelya","email":"bdobreli@redhat.com","username":"bogdando"},"change_message_id":"d83552efcc12f24fdf40c36c2a904216cb7b1d72","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  OpenStack components can use Etcd, a distributed reliable key-value store"},{"line_number":30,"context_line":"  for distributed key locking, storing configuration, keeping track of"},{"line_number":31,"context_line":"  service live-ness and other scenarios."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"**Keystone**"},{"line_number":34,"context_line":"  Keystone handles AuthN/AuthZ for OpenStack components."},{"line_number":35,"context_line":"  Deployments can assume that Keystone will be present to perform that role."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_43f2be9b","line":32,"in_reply_to":"ff0f0b1f_c3f12e03","updated":"2017-05-24 10:57:35.000000000","message":"This document appears to be a very high level overview. It would unlikely benefit from more details like that.","commit_id":"7fc61ccbd37edc148b8d8928b5866f3f6f9bcebe"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"372f4e16425c4fa00d82ab0ae0fc1035d472c1e3","unresolved":false,"context_lines":[{"line_number":28,"context_line":"**Etcd**"},{"line_number":29,"context_line":"  OpenStack components may use Etcd, a distributed reliable key-value store"},{"line_number":30,"context_line":"  for distributed key locking, storing configuration, keeping track of"},{"line_number":31,"context_line":"  service live-ness and other scenarios."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"**Keystone**"},{"line_number":34,"context_line":"  Keystone handles AuthN/AuthZ for OpenStack components."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff0f0b1f_6e66972c","line":31,"range":{"start_line":31,"start_character":10,"end_line":31,"end_character":19},"updated":"2017-05-25 17:20:15.000000000","message":"liveliness","commit_id":"9ad8f55ce8c8556fd702059fc8ad90d3b8b0de3f"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"34430af2a49990bd6566add0d09c578c61c29360","unresolved":false,"context_lines":[{"line_number":28,"context_line":"**Etcd**"},{"line_number":29,"context_line":"  OpenStack components may use Etcd, a distributed reliable key-value store"},{"line_number":30,"context_line":"  for distributed key locking, storing configuration, keeping track of"},{"line_number":31,"context_line":"  service live-ness and other scenarios."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"**Keystone**"},{"line_number":34,"context_line":"  Keystone handles AuthN/AuthZ for OpenStack components."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff0f0b1f_6549f45e","line":31,"range":{"start_line":31,"start_character":10,"end_line":31,"end_character":19},"in_reply_to":"ff0f0b1f_6e66972c","updated":"2017-05-26 14:42:52.000000000","message":"guess i was going for https://en.wikipedia.org/wiki/Liveness, will drop the \"-\" in another review","commit_id":"9ad8f55ce8c8556fd702059fc8ad90d3b8b0de3f"}]}