)]}'
{"guidelines/terms.rst":[{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"dd32fa36621b20406ca4e68e89d34e43d82bc030","unresolved":false,"context_lines":[{"line_number":33,"context_line":"  API Microversions) need to expose each project in a request/response."},{"line_number":34,"context_line":"  The project should be represented with **generic name** because"},{"line_number":35,"context_line":"  **project name** is possibly changed like Neutron and **generic name**"},{"line_number":36,"context_line":"  is more stable."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_6d6efb30","line":36,"updated":"2015-06-30 15:14:28.000000000","message":"The generic name should come from the guidelines for the service catalog naming, namely the \"type\" indicated in the \"endpoints\" for each service catalog entry. Those guidelines are being developed in https://review.openstack.org/#/c/181393.","commit_id":"6d3f575b85c8dc349628418b716842e6ce7958a6"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"e2f2a08f390b6378c988050be6d6df5fcdb6f572","unresolved":false,"context_lines":[{"line_number":33,"context_line":"  API Microversions) need to expose each project in a request/response."},{"line_number":34,"context_line":"  The project should be represented with **generic name** because"},{"line_number":35,"context_line":"  **project name** is possibly changed like Neutron and **generic name**"},{"line_number":36,"context_line":"  is more stable."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_059cc967","line":36,"in_reply_to":"ba3cc151_6d6efb30","updated":"2015-07-01 02:04:53.000000000","message":"Hi Anne,\n\nThank you very much, that is really good feedback for me.\nI\u0027d like to make this patch dependent for the above patch of openstack-specs.","commit_id":"6d3f575b85c8dc349628418b716842e6ce7958a6"},{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"f6bfb608794c4cad70341235454640cebfd47ec5","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* **project name** vs. **generic name**"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"  Each OpenStack project has both project name(Nova, Keystone, etc.) and"},{"line_number":32,"context_line":"  generic name(Compute, Identity, etc.). Some REST API features(JSON-Home,"},{"line_number":33,"context_line":"  API Microversions) need to expose each project in a request/response."},{"line_number":34,"context_line":"  The project should be represented with **generic name** because"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_e153b937","line":31,"updated":"2015-07-01 14:58:43.000000000","message":"Can we do this:\n\n     Each OpenStack project has both a \"project name\" (e.g., Nova, Keystone, etc.) and\n     \"generic name\" (e.g., Compute, Identity, etc.). Some REST API features (e.g., JSON-Home,\n     API Microversions, etc.) need to expose ...\n     The project *should* be represented with its **generic name** because its\n     project name is subect to change (e.g., Neutron was Quantum)\n     and its generic name is more stable. The generic name ...\n     ...","commit_id":"715a9bfc17c2b5761ff506c1e75baa8cde6cfd01"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"ee003f0126bec895bcaa0edbe6f65f84f7ae16fb","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* **project name** vs. **generic name**"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"  Each OpenStack project has both project name(Nova, Keystone, etc.) and"},{"line_number":32,"context_line":"  generic name(Compute, Identity, etc.). Some REST API features(JSON-Home,"},{"line_number":33,"context_line":"  API Microversions) need to expose each project in a request/response."},{"line_number":34,"context_line":"  The project should be represented with **generic name** because"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_018a441b","line":31,"in_reply_to":"ba3cc151_e153b937","updated":"2015-07-01 23:49:55.000000000","message":"Hi Ian,\n\nThank you so much for your suggestion!\nThat is really nice for me, very readable.\n\nI will apply it soon.","commit_id":"715a9bfc17c2b5761ff506c1e75baa8cde6cfd01"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"966e997dc57437e00184deb4dd63b55a631aad95","unresolved":false,"context_lines":[{"line_number":26,"context_line":"  describe a virtual machine, should *not* be used in OpenStack REST"},{"line_number":27,"context_line":"  APIs."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* **project name** vs. **generic name**"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"  Each OpenStack project has both a \"project name\" (e.g., Nova, Keystone, etc.)"},{"line_number":32,"context_line":"  and a \"generic name\" (e.g., Compute, Identity, etc.). Some REST API features"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba3cc151_54ddde6e","line":29,"updated":"2015-07-06 15:51:33.000000000","message":"s/generic name/service type/g","commit_id":"fc6ae37462883d13c7b7d100c92dabc874dd9cfd"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"34074a8071cdd6526894e863e54f2b9dc5b385a8","unresolved":false,"context_lines":[{"line_number":26,"context_line":"  describe a virtual machine, should *not* be used in OpenStack REST"},{"line_number":27,"context_line":"  APIs."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* **project name** vs. **generic name**"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"  Each OpenStack project has both a \"project name\" (e.g., Nova, Keystone, etc.)"},{"line_number":32,"context_line":"  and a \"generic name\" (e.g., Compute, Identity, etc.). Some REST API features"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba3cc151_670384b9","line":29,"in_reply_to":"ba3cc151_54ddde6e","updated":"2015-07-06 23:35:19.000000000","message":"Done","commit_id":"fc6ae37462883d13c7b7d100c92dabc874dd9cfd"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"966e997dc57437e00184deb4dd63b55a631aad95","unresolved":false,"context_lines":[{"line_number":34,"context_line":"  request/response."},{"line_number":35,"context_line":"  The project *should* be represented with its **generic name** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its generic"},{"line_number":37,"context_line":"  name is more stable. The generic name should come from \"type\" of each service"},{"line_number":38,"context_line":"  catalog entry."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba3cc151_146c369b","line":37,"updated":"2015-07-06 15:51:33.000000000","message":"s/each service catalog/the corresponding Keystone service catalog/","commit_id":"fc6ae37462883d13c7b7d100c92dabc874dd9cfd"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"34074a8071cdd6526894e863e54f2b9dc5b385a8","unresolved":false,"context_lines":[{"line_number":34,"context_line":"  request/response."},{"line_number":35,"context_line":"  The project *should* be represented with its **generic name** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its generic"},{"line_number":37,"context_line":"  name is more stable. The generic name should come from \"type\" of each service"},{"line_number":38,"context_line":"  catalog entry."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba3cc151_c7f4d0d0","line":37,"in_reply_to":"ba3cc151_146c369b","updated":"2015-07-06 23:35:19.000000000","message":"Done","commit_id":"fc6ae37462883d13c7b7d100c92dabc874dd9cfd"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"51aaae49daee82c9338eba8ea382012830d2f818","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding Keystone service catalog entry."}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba3cc151_f6816b4e","line":38,"updated":"2015-07-07 12:20:34.000000000","message":"Small issue: in a section emphasizing the need to use the service type instead of the project name, it probably isn\u0027t a good idea to use \u0027Keystone\u0027 here.","commit_id":"97e350c41d3c942bffd0a19df0ab4f995bb7ab84"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"a1f07244bf801335f84d24cf6c6b4728d5571700","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a50d1a3_ee1e8b5e","line":38,"updated":"2015-07-31 08:28:55.000000000","message":"Note that this completely ignores the fact that project might (and Ironic does) have several API services.","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"d70f446b8589bc4aed53222f3e56972fcb0fdb1d","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a50d1a3_ce714fe0","line":38,"in_reply_to":"3a50d1a3_0e85f7cd","updated":"2015-07-31 08:54:17.000000000","message":"\u003e Some projects start to implement microversions in liberty, maybe these projects do it based on current implementations of ironic and nova\n\nironic-inspector did this as well, hence my question (though yeah, it\u0027s a bit too late)","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"2e030834712927ab4ce931f8c61c82b9ca3122e8","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a50d1a3_a9d07df8","line":38,"in_reply_to":"3a50d1a3_29b9cdec","updated":"2015-07-31 09:07:44.000000000","message":"Sorry for typo.\n\ns/contain it/not contain it/","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"365da433299d6d7aac07e2cb49e1dd749a55df49","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a50d1a3_ae1f2308","line":38,"in_reply_to":"3a50d1a3_8e66e7b9","updated":"2015-07-31 08:39:23.000000000","message":"I realize, but now people ask me how we should apply this to ironic-inspector. I have no idea :)\n\nAnd I think we need this suggestion to have a good coverage to justify changing existing projects as well.\n\nOr at least a TODO item to cover this direction, before you tell all projects to move.","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"f5cc8785ec8f957801bb1ab9a31167bac31920f8","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a50d1a3_0e85f7cd","line":38,"in_reply_to":"3a50d1a3_ae1f2308","updated":"2015-07-31 08:49:44.000000000","message":"yeah, I also don\u0027t have any idea for getting the corresponding service type for ironic-inspector.\n\nBut as yo know, ironic-inspector has been renamed from ironic-discoverd. So I guess this guideline is not so far from you.\n\nSome projects start to implement microversions in liberty, maybe these projects do it based on current implementations of ironic and nova. so it is better to avoid renaming headers on these projects in the future by referring this guideline.","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"b7fcf91b1767d80cd5948659dbf4813cfcb5a9a5","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a50d1a3_29b9cdec","line":38,"in_reply_to":"3a50d1a3_ce714fe0","updated":"2015-07-31 09:06:09.000000000","message":"ah, I see.\n\nThat should be discussed on microversions api-wg guideline[1].\nbecause we have some options(contain service type name, or not) for microversions header naming.\n\nI guess if project doesn\u0027t have the corresponding service type, it seems acceptable to contain it in the header name until getting it.\nbut yeah, that should be another topic from this.\n\n[1]: https://review.openstack.org/#/c/187112/","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"bb80e2fa1308f94184566d2b3a6d7d4a6083c8eb","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"ba15a1d1_3e301401","line":38,"in_reply_to":"3a50d1a3_ee1e8b5e","updated":"2015-09-15 16:32:38.000000000","message":"I think the fact that a project may have several services reinforces the point that the service type should be primary, rather than the project. If Ironic had to change its name, or if another baremetal project wanted to offer a different implementation, a name like \u0027ironic-inspector\u0027 would not be a good choice.","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"83d4a9875a643513969f9c56461585e60536601b","unresolved":false,"context_lines":[{"line_number":35,"context_line":"  The project *should* be represented with its **service type** because its"},{"line_number":36,"context_line":"  project name is subject to change (e.g., Neutron was Quantum) and its service"},{"line_number":37,"context_line":"  type is more stable. The service type should come from \"type\" of the"},{"line_number":38,"context_line":"  corresponding OpenStack Identity service catalog entry."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a50d1a3_8e66e7b9","line":38,"in_reply_to":"3a50d1a3_ee1e8b5e","updated":"2015-07-31 08:37:02.000000000","message":"Yeah, it is difficult to cover every situation in this sentence.\n\nThis is just a guideline and provides a hint to consider which is better, project name or service type.","commit_id":"e6718cf9e24fca2091903712b7afee92cb2b3255"}]}