)]}'
{"specs/kilo/approved/nova-api-json-home.rst":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"25980b1e9bdc92ca85c5a24ae322c5553ed6ce8b","unresolved":false,"context_lines":[{"line_number":90,"context_line":"attribute like:"},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"::"},{"line_number":93,"context_line":""},{"line_number":94,"context_line":" {"},{"line_number":95,"context_line":"   \"resources\": {"},{"line_number":96,"context_line":"     \"http://docs.openstack.org/api/openstack-compute/2.1/rel/servers\": {"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9aa7fdbe_4671f4a6","line":93,"updated":"2014-10-27 08:20:19.000000000","message":"Can each resource and its level can be published via  href-template in hierarchical level?\nMeans \"href-template\": \"/v2.1/{project_id}/servers\", can have its allow methods (GET, POSt etc) and another child \"href-template\" for \"servers/action\" etc\n\nJust curious to know how JSON HOME will publish below APIs\n1.  \"/servers/action\" , \"servers/metadata\", \"servers/metadata/key\" etc.\n2. GET /servers - \"servers/detail\"","commit_id":"df50369052a1600a17281e2afb7fe74c04fa3270"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"aca4a63882ba50b18723bcb4ca27c5fc8e9469a1","unresolved":false,"context_lines":[{"line_number":90,"context_line":"attribute like:"},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"::"},{"line_number":93,"context_line":""},{"line_number":94,"context_line":" {"},{"line_number":95,"context_line":"   \"resources\": {"},{"line_number":96,"context_line":"     \"http://docs.openstack.org/api/openstack-compute/2.1/rel/servers\": {"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9aa7fdbe_111f246d","line":93,"in_reply_to":"9aa7fdbe_4671f4a6","updated":"2014-10-27 09:56:11.000000000","message":"Nice point, and we can do it because Keystone has already done the same thing for its own resources.","commit_id":"df50369052a1600a17281e2afb7fe74c04fa3270"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"25980b1e9bdc92ca85c5a24ae322c5553ed6ce8b","unresolved":false,"context_lines":[{"line_number":122,"context_line":"     \"http://docs.openstack.org/api/openstack-compute/2.1/rel/old-resource\": {"},{"line_number":123,"context_line":"       \"href-template\": \"/v2.1/{project_id}/old-resource\","},{"line_number":124,"context_line":"       \"hints\": {"},{"line_number":125,"context_line":"         \"status\": \"deprecated\","},{"line_number":126,"context_line":"         \"allow\": [\"GET\", \"POST\", \"PUT\", \"DELETE\"],"},{"line_number":127,"context_line":"       },"},{"line_number":128,"context_line":"       [..]"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9aa7fdbe_a661c0d4","line":125,"updated":"2014-10-27 08:20:19.000000000","message":"status field can be used to show \"experimental\" for experimental APIs right?","commit_id":"df50369052a1600a17281e2afb7fe74c04fa3270"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"aca4a63882ba50b18723bcb4ca27c5fc8e9469a1","unresolved":false,"context_lines":[{"line_number":122,"context_line":"     \"http://docs.openstack.org/api/openstack-compute/2.1/rel/old-resource\": {"},{"line_number":123,"context_line":"       \"href-template\": \"/v2.1/{project_id}/old-resource\","},{"line_number":124,"context_line":"       \"hints\": {"},{"line_number":125,"context_line":"         \"status\": \"deprecated\","},{"line_number":126,"context_line":"         \"allow\": [\"GET\", \"POST\", \"PUT\", \"DELETE\"],"},{"line_number":127,"context_line":"       },"},{"line_number":128,"context_line":"       [..]"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9aa7fdbe_b12e58a3","line":125,"in_reply_to":"9aa7fdbe_a661c0d4","updated":"2014-10-27 09:56:11.000000000","message":"No, current JSON-Home doesn\u0027t contain \"experimental\".\nMaybe we can use \"deprecated\" for this case because of the similar meaning.","commit_id":"df50369052a1600a17281e2afb7fe74c04fa3270"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"f8ad6c890692de81bb8075a5d5997ac34549b4c4","unresolved":false,"context_lines":[{"line_number":48,"context_line":"On JSON-Home spec, JSON-Home works only if passing \u0027application/json-home\u0027 in"},{"line_number":49,"context_line":"an accept header. If nova-api receives it, nova-api provides available REST"},{"line_number":50,"context_line":"URLs to a client with JSON-Home format. For example, nova-api will provide"},{"line_number":51,"context_line":"the following data if \"GET /v2.1\" by passing \u0027application/json-home\u0027:"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"::"},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9aa7fdbe_48cd6c65","line":51,"updated":"2014-10-28 00:17:50.000000000","message":"if a client \"GET /v2.1\" with an accept header \u0027application/json-home\u0027:","commit_id":"29973946a35e52e78b3fdb720a6be5f6d97d4079"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"f8ad6c890692de81bb8075a5d5997ac34549b4c4","unresolved":false,"context_lines":[{"line_number":298,"context_line":""},{"line_number":299,"context_line":"None yet."},{"line_number":300,"context_line":"We can get API URLs, HTTP methods(GET, POST, ..) with this feature, but API"},{"line_number":301,"context_line":"documents needs request/response body formats also and this spec cannot cover"},{"line_number":302,"context_line":"it as the first step. The feature which provides request/response body formats"},{"line_number":303,"context_line":"will be discussed on the other spec across projects. After that we will be"},{"line_number":304,"context_line":"able to get API documents with the same way on different projects, that will"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9aa7fdbe_28858806","line":301,"updated":"2014-10-28 00:17:50.000000000","message":"s/cannot/does not/","commit_id":"29973946a35e52e78b3fdb720a6be5f6d97d4079"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/nova-api-json-home"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Nova needs to provide a standard API extension discovery way to clients."},{"line_number":14,"context_line":"This spec proposes JSON-Home as the way."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Problem description"},{"line_number":17,"context_line":"\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":5,"id":"5a890539_7a29a588","line":14,"updated":"2014-11-20 10:57:29.000000000","message":"+1\n\nI totally support this.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"1e30c62393ad3a823428a3b5c428e2a8ef68b7ca","unresolved":false,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/nova-api-json-home"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Nova needs to provide a standard API extension discovery way to clients."},{"line_number":14,"context_line":"This spec proposes JSON-Home as the way."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Problem description"},{"line_number":17,"context_line":"\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":5,"id":"5a890539_8485135b","line":14,"in_reply_to":"5a890539_7a29a588","updated":"2014-11-20 12:25:08.000000000","message":"Thanks!","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":21,"context_line":"From the point of view of whole OpenStack projects, the ways are not"},{"line_number":22,"context_line":"consistent and application programers should write an application for"},{"line_number":23,"context_line":"handling these extensions by different ways."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"----------"},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_3ab47d34","line":24,"updated":"2014-11-20 10:57:29.000000000","message":"Given the direction of the versioning of the API, I wonder if we actually want to look at this in a totally different way.\n\nTo make this work, maybe this spec should remove the ability to disable API extensions.\n\nNote, deployers are still free to use policy to \"disallow\" an extension. We probably want a way for policy to influence what is listed as available, but we should certainly keep that a separate debate.\n\nThis then means JSON-Home is purely to discover what *version* is available on a particular openstack deployment. Indeed, given the microversions, there maybe some APIs that are marked \"experimental\" due to out of tree changes that have been made too them.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":21,"context_line":"From the point of view of whole OpenStack projects, the ways are not"},{"line_number":22,"context_line":"consistent and application programers should write an application for"},{"line_number":23,"context_line":"handling these extensions by different ways."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"----------"},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_ee76b6d7","line":24,"in_reply_to":"5a890539_3ab47d34","updated":"2014-11-20 11:35:44.000000000","message":"I think the scope of current approved microversion spec can cover how to change a request/response body only. it does not cover how to change API path.\nand current this spec covers API paths, which are not changed with microversion, only.\n\nSo both specs avoid conflicts now.\n\nWhen adding \"JSON-Schema on JSON-Home\", we need to consider microversions.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"1e30c62393ad3a823428a3b5c428e2a8ef68b7ca","unresolved":false,"context_lines":[{"line_number":21,"context_line":"From the point of view of whole OpenStack projects, the ways are not"},{"line_number":22,"context_line":"consistent and application programers should write an application for"},{"line_number":23,"context_line":"handling these extensions by different ways."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"----------"},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_04aa03d2","line":24,"in_reply_to":"5a890539_ee76b6d7","updated":"2014-11-20 12:25:08.000000000","message":"Added this just before \"Alternatives\".","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"No priority defined for this feature yet."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Proposed change"},{"line_number":42,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_3a8b9d69","line":39,"updated":"2014-11-20 10:57:29.000000000","message":"I think this is a part of the api-microversion priority, but only just.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"1e30c62393ad3a823428a3b5c428e2a8ef68b7ca","unresolved":false,"context_lines":[{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"No priority defined for this feature yet."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Proposed change"},{"line_number":42,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_f10bfb28","line":39,"in_reply_to":"5a890539_0e2062af","updated":"2014-11-20 12:25:08.000000000","message":"Done","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"No priority defined for this feature yet."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Proposed change"},{"line_number":42,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_0e2062af","line":39,"in_reply_to":"5a890539_3a8b9d69","updated":"2014-11-20 11:35:44.000000000","message":"Here should be None now?","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":69,"context_line":"     },"},{"line_number":70,"context_line":"     [..]"},{"line_number":71,"context_line":"   }"},{"line_number":72,"context_line":" }"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"The keys of the resources property are link relationship types. A relationship"},{"line_number":75,"context_line":"type needs to be chosen for the key. There are several relationship types"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_5ac78912","line":72,"updated":"2014-11-20 10:57:29.000000000","message":"Is this not technically micro-version specific?","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":69,"context_line":"     },"},{"line_number":70,"context_line":"     [..]"},{"line_number":71,"context_line":"   }"},{"line_number":72,"context_line":" }"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"The keys of the resources property are link relationship types. A relationship"},{"line_number":75,"context_line":"type needs to be chosen for the key. There are several relationship types"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_6e3726b1","line":72,"in_reply_to":"5a890539_5ac78912","updated":"2014-11-20 11:35:44.000000000","message":"This is general from JSON-Home spec, not micro-version specific.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":84,"context_line":"http://docs.openstack.org/api/openstack-compute/2/xsd. So Nova should publish"},{"line_number":85,"context_line":"a similar location for consistency. For v2.1 resources, the relationship type"},{"line_number":86,"context_line":"link will be http://docs.openstack.org/api/openstack-compute/2.1/rel as the"},{"line_number":87,"context_line":"above sample."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"If querying against a specific URL(eg. GET /v2.1/{project_id}/servers), client"},{"line_number":90,"context_line":"can get more detail information(available HTTP methods, format) on \"hints\""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_da3e1929","line":87,"updated":"2014-11-20 10:57:29.000000000","message":"Don\u0027t we need one for each microversion?","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"1e30c62393ad3a823428a3b5c428e2a8ef68b7ca","unresolved":false,"context_lines":[{"line_number":84,"context_line":"http://docs.openstack.org/api/openstack-compute/2/xsd. So Nova should publish"},{"line_number":85,"context_line":"a similar location for consistency. For v2.1 resources, the relationship type"},{"line_number":86,"context_line":"link will be http://docs.openstack.org/api/openstack-compute/2.1/rel as the"},{"line_number":87,"context_line":"above sample."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"If querying against a specific URL(eg. GET /v2.1/{project_id}/servers), client"},{"line_number":90,"context_line":"can get more detail information(available HTTP methods, format) on \"hints\""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_d1151f4a","line":87,"in_reply_to":"5a890539_9129d78b","updated":"2014-11-20 12:25:08.000000000","message":"Done","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":84,"context_line":"http://docs.openstack.org/api/openstack-compute/2/xsd. So Nova should publish"},{"line_number":85,"context_line":"a similar location for consistency. For v2.1 resources, the relationship type"},{"line_number":86,"context_line":"link will be http://docs.openstack.org/api/openstack-compute/2.1/rel as the"},{"line_number":87,"context_line":"above sample."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"If querying against a specific URL(eg. GET /v2.1/{project_id}/servers), client"},{"line_number":90,"context_line":"can get more detail information(available HTTP methods, format) on \"hints\""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_9129d78b","line":87,"in_reply_to":"5a890539_da3e1929","updated":"2014-11-20 11:35:44.000000000","message":"Maybe multiple links for each microversion would be unnecessary because the endpoint would be the same on all microversions.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":145,"context_line":"API definitions with \"hints\" of JSON-Home (JSON-Schema on JSON-Home) as an"},{"line_number":146,"context_line":"OpenStack specific feature. However, the feature is out of scope from this"},{"line_number":147,"context_line":"spec and this spec covers the standard scope of JSON-Home without JSON-Schema."},{"line_number":148,"context_line":"The feature needs the other spec and we need to discuss it across projects."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"API router has already contained necessary information for JSON-Home, and"},{"line_number":151,"context_line":"we can implement JSON-Home feature just by arranging the information to"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_baa22d49","line":148,"updated":"2014-11-20 10:57:29.000000000","message":"Honestly, can\u0027t we add that here? It feels like thats the most useful part.\n\nMaybe we have something like:\napplication/json-home-with-payload-schema\n\nBut you are right, that should be another blueprint.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":145,"context_line":"API definitions with \"hints\" of JSON-Home (JSON-Schema on JSON-Home) as an"},{"line_number":146,"context_line":"OpenStack specific feature. However, the feature is out of scope from this"},{"line_number":147,"context_line":"spec and this spec covers the standard scope of JSON-Home without JSON-Schema."},{"line_number":148,"context_line":"The feature needs the other spec and we need to discuss it across projects."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"API router has already contained necessary information for JSON-Home, and"},{"line_number":151,"context_line":"we can implement JSON-Home feature just by arranging the information to"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_8e15329d","line":148,"in_reply_to":"5a890539_baa22d49","updated":"2014-11-20 11:35:44.000000000","message":"Yeah, that would be interesting feature, and application/json-home-with-payload-schema seems a nice interface.\nHowever, I cannot describe anything now due to the spec scope and need to discuss more cross projects :-(","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":163,"context_line":""},{"line_number":164,"context_line":"None."},{"line_number":165,"context_line":"Current API router has already contained necessary data for JSON-Home support."},{"line_number":166,"context_line":"So we don\u0027t need to change data model."},{"line_number":167,"context_line":""},{"line_number":168,"context_line":"REST API impact"},{"line_number":169,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_da6c5939","line":166,"updated":"2014-11-20 10:57:29.000000000","message":"This means DB model really, so this can just be \"none\"","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"1e30c62393ad3a823428a3b5c428e2a8ef68b7ca","unresolved":false,"context_lines":[{"line_number":163,"context_line":""},{"line_number":164,"context_line":"None."},{"line_number":165,"context_line":"Current API router has already contained necessary data for JSON-Home support."},{"line_number":166,"context_line":"So we don\u0027t need to change data model."},{"line_number":167,"context_line":""},{"line_number":168,"context_line":"REST API impact"},{"line_number":169,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_64e9071a","line":166,"in_reply_to":"5a890539_6e79e6fb","updated":"2014-11-20 12:25:08.000000000","message":"Done","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":163,"context_line":""},{"line_number":164,"context_line":"None."},{"line_number":165,"context_line":"Current API router has already contained necessary data for JSON-Home support."},{"line_number":166,"context_line":"So we don\u0027t need to change data model."},{"line_number":167,"context_line":""},{"line_number":168,"context_line":"REST API impact"},{"line_number":169,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_6e79e6fb","line":166,"in_reply_to":"5a890539_da6c5939","updated":"2014-11-20 11:35:44.000000000","message":"Thanks, will remove.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":184,"context_line":""},{"line_number":185,"context_line":"  * URL for the resource"},{"line_number":186,"context_line":"    /v2.1 and under"},{"line_number":187,"context_line":"    /v2 and under. If configuring v2.1 implementation as /v2 on api-paste.ini."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"  * JSON schema definition for the body data if allowed"},{"line_number":190,"context_line":"    A request body is not allowed."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_ba5dcd7b","line":187,"updated":"2014-11-20 10:57:29.000000000","message":"I don\u0027t think we need this for v2, lets just do it for the new thing.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"1e30c62393ad3a823428a3b5c428e2a8ef68b7ca","unresolved":false,"context_lines":[{"line_number":184,"context_line":""},{"line_number":185,"context_line":"  * URL for the resource"},{"line_number":186,"context_line":"    /v2.1 and under"},{"line_number":187,"context_line":"    /v2 and under. If configuring v2.1 implementation as /v2 on api-paste.ini."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"  * JSON schema definition for the body data if allowed"},{"line_number":190,"context_line":"    A request body is not allowed."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_448b2b68","line":187,"in_reply_to":"5a890539_ae5aee80","updated":"2014-11-20 12:25:08.000000000","message":"Done","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":184,"context_line":""},{"line_number":185,"context_line":"  * URL for the resource"},{"line_number":186,"context_line":"    /v2.1 and under"},{"line_number":187,"context_line":"    /v2 and under. If configuring v2.1 implementation as /v2 on api-paste.ini."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"  * JSON schema definition for the body data if allowed"},{"line_number":190,"context_line":"    A request body is not allowed."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_ae5aee80","line":187,"in_reply_to":"5a890539_ba5dcd7b","updated":"2014-11-20 11:35:44.000000000","message":"Thanks, will remove this line.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"161535485b6b46f5d91f7123e6a06f4a26e7bfcc","unresolved":false,"context_lines":[{"line_number":253,"context_line":"* Please state anything that those doing continuous deployment, or those"},{"line_number":254,"context_line":"  upgrading from the previous release, need to be aware of."},{"line_number":255,"context_line":"  This feature works only if client passes a new option \u0027application/json-home\u0027"},{"line_number":256,"context_line":"  in an accept header, and it doesn\u0027t affect to the existing OpenStack clouds."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"Developer impact"},{"line_number":259,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_7abfe560","line":256,"updated":"2014-11-20 10:57:29.000000000","message":"This needs removing?","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"d3e51b8b27ac93e18134276cd868b11906af36b1","unresolved":false,"context_lines":[{"line_number":253,"context_line":"* Please state anything that those doing continuous deployment, or those"},{"line_number":254,"context_line":"  upgrading from the previous release, need to be aware of."},{"line_number":255,"context_line":"  This feature works only if client passes a new option \u0027application/json-home\u0027"},{"line_number":256,"context_line":"  in an accept header, and it doesn\u0027t affect to the existing OpenStack clouds."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"Developer impact"},{"line_number":259,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_71746b9c","line":256,"in_reply_to":"5a890539_7abfe560","updated":"2014-11-20 11:35:44.000000000","message":"OK, will remove here.","commit_id":"d327a62e3b01abda03ed0f5442234ee541cd536b"},{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"9971164aed937d8c3bb6c924d9959d9431c94e54","unresolved":false,"context_lines":[{"line_number":20,"context_line":"API, but the way is Nova-specific and that is not a standard way."},{"line_number":21,"context_line":"From the point of view of whole OpenStack projects, the ways are not"},{"line_number":22,"context_line":"consistent and application programers should write an application for"},{"line_number":23,"context_line":"handling these extensions by different ways."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_86c88523","line":23,"updated":"2014-12-10 20:28:52.000000000","message":"I really like the idea of using JSON-Home, but I think it should be justified without talking about extensions.  There has been some talk about removing extensions, and what would be the reason to use this if that happened?\n\nNot that we shouldn\u0027t do this for the reasons you\u0027ve described, but I think this is useful even if we didn\u0027t have extensions and should be described like that.","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"b1941714f0e92cb2091c4deea4501973f405814b","unresolved":false,"context_lines":[{"line_number":20,"context_line":"API, but the way is Nova-specific and that is not a standard way."},{"line_number":21,"context_line":"From the point of view of whole OpenStack projects, the ways are not"},{"line_number":22,"context_line":"consistent and application programers should write an application for"},{"line_number":23,"context_line":"handling these extensions by different ways."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_5b7f0c66","line":23,"in_reply_to":"3a961159_59259407","updated":"2014-12-12 16:24:19.000000000","message":"I mean the first one.  But what I really mean is that the problem description makes this spec seem like it\u0027s primarily intended to replace \"list extensions\".  I think it\u0027s much more useful than that and the problem could be restated to be about API discoverability in general.","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"caa261ab48c0cb256fdaa395d75ceda351e11b48","unresolved":false,"context_lines":[{"line_number":20,"context_line":"API, but the way is Nova-specific and that is not a standard way."},{"line_number":21,"context_line":"From the point of view of whole OpenStack projects, the ways are not"},{"line_number":22,"context_line":"consistent and application programers should write an application for"},{"line_number":23,"context_line":"handling these extensions by different ways."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_1ff1d094","line":23,"in_reply_to":"3a961159_5b7f0c66","updated":"2014-12-15 02:55:10.000000000","message":"@Andrew\n\nThanks for clarifying it. I agree with your comment, current description scope seems extension-specific, and \"API discoverability\" is a nice word.\nI will apply it to the next spec with changing the title also.","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"7cb8deca62e5ac0872149cf8ab610fda6add001b","unresolved":false,"context_lines":[{"line_number":20,"context_line":"API, but the way is Nova-specific and that is not a standard way."},{"line_number":21,"context_line":"From the point of view of whole OpenStack projects, the ways are not"},{"line_number":22,"context_line":"consistent and application programers should write an application for"},{"line_number":23,"context_line":"handling these extensions by different ways."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Use Cases"},{"line_number":26,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_59259407","line":23,"in_reply_to":"3a961159_86c88523","updated":"2014-12-11 04:01:05.000000000","message":"I think extensions contains two meanings/features now.\n\nThe one is for adding the resource like os-agents.\n\n os-agents adds /v2/{project-id}/os-agents as the resource.\n\nThe other is for adding special attributes to the existing API like OS-SCH-HNT(scheduler_hints).\n\n OS-SCH-HNT adds \u0027os:scheduler_hints\u0027 attribute to \"create a server\" API.\n\nJSON-Home of current this spec can cover info of the first one, because it can provide resource info(API URLs).\nHowever, it cannot cover the second one because it cannot provide request/response body info. Maybe \"JSON-Schema on JSON-Home\" can cover it, but it is out of scope from this spec as line 147.\n\nIf  \"extensions\" you mentioned is the first one, we don\u0027t need to consider extensions and the removal of extensions would not affect this spec because it is just a resource.\nIf the second one, that is out of scope. and \"JSON-Schema on JSON-Home\" will be able to avoid the effect of extension removals in the future.","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":5292,"name":"Christopher Yeoh","email":"cbkyeoh@gmail.com","username":"cyeoh-0"},"change_message_id":"99529ce4cdccae129419398a6bd4227844d1cee6","unresolved":false,"context_lines":[{"line_number":156,"context_line":"The scope of approved microversion spec can cover how to change a request/"},{"line_number":157,"context_line":"response body only. It doesn\u0027t cover how to change API paths. On the other"},{"line_number":158,"context_line":"hand, this spec covers API paths, which are not changed with microversion."},{"line_number":159,"context_line":"So each scope of these specs are different now. When adding \"JSON-Schema on"},{"line_number":160,"context_line":"JSON-Home\", we will need to consider microversions."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_a1c376eb","line":159,"updated":"2014-12-12 05:45:07.000000000","message":"I don\u0027t think this is true anymore. A micro version bump can remove or add a resource url. So the Jason home info needs to take into account micro version header","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"caa261ab48c0cb256fdaa395d75ceda351e11b48","unresolved":false,"context_lines":[{"line_number":156,"context_line":"The scope of approved microversion spec can cover how to change a request/"},{"line_number":157,"context_line":"response body only. It doesn\u0027t cover how to change API paths. On the other"},{"line_number":158,"context_line":"hand, this spec covers API paths, which are not changed with microversion."},{"line_number":159,"context_line":"So each scope of these specs are different now. When adding \"JSON-Schema on"},{"line_number":160,"context_line":"JSON-Home\", we will need to consider microversions."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_a240a307","line":159,"in_reply_to":"3a961159_5498c477","updated":"2014-12-15 02:55:10.000000000","message":"Yeah, the combination of microversions and JSON-Home can cover many cases.\nAnd I guess now clients should not be able to access to the API path which is removed with the specified microversion even if minimum microversion supports it because of the interoperability.\n\nSo I now agree with that this spec supports microversions also.","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"a1f87e0e8bb4df77e59745db8eee2e93ad38b0fa","unresolved":false,"context_lines":[{"line_number":156,"context_line":"The scope of approved microversion spec can cover how to change a request/"},{"line_number":157,"context_line":"response body only. It doesn\u0027t cover how to change API paths. On the other"},{"line_number":158,"context_line":"hand, this spec covers API paths, which are not changed with microversion."},{"line_number":159,"context_line":"So each scope of these specs are different now. When adding \"JSON-Schema on"},{"line_number":160,"context_line":"JSON-Home\", we will need to consider microversions."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_a7c386eb","line":159,"in_reply_to":"3a961159_a1c376eb","updated":"2014-12-12 08:29:06.000000000","message":"Yeah, I forgot to update here. Microversion bump can remove/add a resource URL.\n\nHowever, I am not sure we need microversion header for JSON-Home now. As line 115, JSON-Home can provide \"deprecated\" info for each resource URL. I\u0027d like to separate this topic to two cases(add/remove a resource).\n\n* Add a new resource\n If we can use a new resource URL without specifying a new microversion\n because it is backwards compatible, it is enough that JSON-Home provides\n a new resource info without a microversion. Otherwise, microversion header\n is necessary for JSON-Home.\n\n* Remove a old resource\n If we can use an old resource URL with specifying a new microversion until\n the default(lowest) microversion bump, it is enough that JSON-Home provides\n an old resource info as \"deprecated\" without a microversion. Otherwise,\n microversion header is necessary for JSON-Home in this case also.\n\nSo I\u0027m not sure which is reasonable for each case on a microversion.","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"32f58c46565e402a310b483305e02c438f858cbc","unresolved":false,"context_lines":[{"line_number":156,"context_line":"The scope of approved microversion spec can cover how to change a request/"},{"line_number":157,"context_line":"response body only. It doesn\u0027t cover how to change API paths. On the other"},{"line_number":158,"context_line":"hand, this spec covers API paths, which are not changed with microversion."},{"line_number":159,"context_line":"So each scope of these specs are different now. When adding \"JSON-Schema on"},{"line_number":160,"context_line":"JSON-Home\", we will need to consider microversions."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a961159_5498c477","line":159,"in_reply_to":"3a961159_a7c386eb","updated":"2014-12-12 12:56:36.000000000","message":"Assume microversions apply to everything. I think the microversion header should work fine with JSON home in the same way that we expect.\n\nIf you don\u0027t send it, you get the oldest version described. If you do send it you get that version.","commit_id":"2581b539900bc2e12666249a46eca7c909e07d77"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"94024e2a7fdcf973758cce67b0d56f126c4a6776","unresolved":false,"context_lines":[{"line_number":32,"context_line":"these features by a common way. For example, end users can get available REST"},{"line_number":33,"context_line":"URLs(v2/{project-id}/servers, etc) by passing \u0027application/json-home\u0027 in an"},{"line_number":34,"context_line":"accept header with GET method."},{"line_number":35,"context_line":"Developers can get full set of REST URLs including details(available method("},{"line_number":36,"context_line":"GET/POST/PUT etc)) and create API document based on the information. Ideally"},{"line_number":37,"context_line":"it is the best to generate API document automatically from this feature."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_19cee5b7","line":35,"updated":"2015-01-13 11:51:10.000000000","message":"nit: ...including details such as available methods (GET/PUT/POST etc)...\n\nAside from the missing whitespace, I don\u0027t think nested parens in English prose are very easy to read.","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"23746de2f12fbdf794cbdd1dff13297f33d4fb3c","unresolved":false,"context_lines":[{"line_number":32,"context_line":"these features by a common way. For example, end users can get available REST"},{"line_number":33,"context_line":"URLs(v2/{project-id}/servers, etc) by passing \u0027application/json-home\u0027 in an"},{"line_number":34,"context_line":"accept header with GET method."},{"line_number":35,"context_line":"Developers can get full set of REST URLs including details(available method("},{"line_number":36,"context_line":"GET/POST/PUT etc)) and create API document based on the information. Ideally"},{"line_number":37,"context_line":"it is the best to generate API document automatically from this feature."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_6338fdd4","line":35,"in_reply_to":"3a961159_19cee5b7","updated":"2015-01-14 00:39:43.000000000","message":"Done","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"94024e2a7fdcf973758cce67b0d56f126c4a6776","unresolved":false,"context_lines":[{"line_number":34,"context_line":"accept header with GET method."},{"line_number":35,"context_line":"Developers can get full set of REST URLs including details(available method("},{"line_number":36,"context_line":"GET/POST/PUT etc)) and create API document based on the information. Ideally"},{"line_number":37,"context_line":"it is the best to generate API document automatically from this feature."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Project Priority"},{"line_number":40,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_d9bb7d0d","line":37,"updated":"2015-01-13 11:51:10.000000000","message":"nit lines 35,37: \"document\" should be \"documents\" or maybe \"documentation\"?","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"23746de2f12fbdf794cbdd1dff13297f33d4fb3c","unresolved":false,"context_lines":[{"line_number":34,"context_line":"accept header with GET method."},{"line_number":35,"context_line":"Developers can get full set of REST URLs including details(available method("},{"line_number":36,"context_line":"GET/POST/PUT etc)) and create API document based on the information. Ideally"},{"line_number":37,"context_line":"it is the best to generate API document automatically from this feature."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Project Priority"},{"line_number":40,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_c3445149","line":37,"in_reply_to":"3a961159_d9bb7d0d","updated":"2015-01-14 00:39:43.000000000","message":"Done","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"94024e2a7fdcf973758cce67b0d56f126c4a6776","unresolved":false,"context_lines":[{"line_number":44,"context_line":"Proposed change"},{"line_number":45,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"There is JSON-Home as one of standard ways and Keystone has already implemented"},{"line_number":48,"context_line":"JSON-Home on Keystone REST API. This spec/blueprint proposes JSON-Home support"},{"line_number":49,"context_line":"for Nova v2.1 API."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_d969bd8d","line":47,"updated":"2015-01-13 11:51:10.000000000","message":"nit: JSON-Home is a standard, and Keystone....\n\nIt would also be good to have a link to the footnote here.","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"23746de2f12fbdf794cbdd1dff13297f33d4fb3c","unresolved":false,"context_lines":[{"line_number":44,"context_line":"Proposed change"},{"line_number":45,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"There is JSON-Home as one of standard ways and Keystone has already implemented"},{"line_number":48,"context_line":"JSON-Home on Keystone REST API. This spec/blueprint proposes JSON-Home support"},{"line_number":49,"context_line":"for Nova v2.1 API."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_a3bca507","line":47,"in_reply_to":"3a961159_d969bd8d","updated":"2015-01-14 00:39:43.000000000","message":"Done","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"94024e2a7fdcf973758cce67b0d56f126c4a6776","unresolved":false,"context_lines":[{"line_number":78,"context_line":"type needs to be chosen for the key. There are several relationship types"},{"line_number":79,"context_line":"registered with IANA, but there\u0027s none designated for compute API resources."},{"line_number":80,"context_line":"If a group doesn\u0027t want to register a relation with IANA (see section 4.2"},{"line_number":81,"context_line":"\"Extension Relation Types\" in RFC 5988), they can use some unique URL instead."},{"line_number":82,"context_line":"An application could potentially fetch this URL to get information about the"},{"line_number":83,"context_line":"relationship, so we should pick one that could potentially be used to serve up"},{"line_number":84,"context_line":"some info about what the relationship is and describe the resource."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_b9f151e0","line":81,"updated":"2015-01-13 11:51:10.000000000","message":"A link to the RFC or footnote here would be helpful","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"23746de2f12fbdf794cbdd1dff13297f33d4fb3c","unresolved":false,"context_lines":[{"line_number":78,"context_line":"type needs to be chosen for the key. There are several relationship types"},{"line_number":79,"context_line":"registered with IANA, but there\u0027s none designated for compute API resources."},{"line_number":80,"context_line":"If a group doesn\u0027t want to register a relation with IANA (see section 4.2"},{"line_number":81,"context_line":"\"Extension Relation Types\" in RFC 5988), they can use some unique URL instead."},{"line_number":82,"context_line":"An application could potentially fetch this URL to get information about the"},{"line_number":83,"context_line":"relationship, so we should pick one that could potentially be used to serve up"},{"line_number":84,"context_line":"some info about what the relationship is and describe the resource."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_2325155c","line":81,"in_reply_to":"3a961159_b9f151e0","updated":"2015-01-14 00:39:43.000000000","message":"Done","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"94024e2a7fdcf973758cce67b0d56f126c4a6776","unresolved":false,"context_lines":[{"line_number":151,"context_line":"spec and this spec covers the standard scope of JSON-Home without JSON-Schema."},{"line_number":152,"context_line":"The feature needs the other spec and we need to discuss it across projects."},{"line_number":153,"context_line":""},{"line_number":154,"context_line":"API router has already contained necessary information for JSON-Home, and"},{"line_number":155,"context_line":"we can implement JSON-Home feature just by arranging the information to"},{"line_number":156,"context_line":"JSON-Home format and publishing it to a client."},{"line_number":157,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_b9187120","line":154,"updated":"2015-01-13 11:51:10.000000000","message":"I don\u0027t quite understand the start of this paragraph. I guess you mean something like \"The API router classes already contain the necessary information for JSON-Home\", and...?","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"23746de2f12fbdf794cbdd1dff13297f33d4fb3c","unresolved":false,"context_lines":[{"line_number":151,"context_line":"spec and this spec covers the standard scope of JSON-Home without JSON-Schema."},{"line_number":152,"context_line":"The feature needs the other spec and we need to discuss it across projects."},{"line_number":153,"context_line":""},{"line_number":154,"context_line":"API router has already contained necessary information for JSON-Home, and"},{"line_number":155,"context_line":"we can implement JSON-Home feature just by arranging the information to"},{"line_number":156,"context_line":"JSON-Home format and publishing it to a client."},{"line_number":157,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_83e089f9","line":154,"in_reply_to":"3a961159_b9187120","updated":"2015-01-14 00:39:43.000000000","message":"Yeah, right. done","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"94024e2a7fdcf973758cce67b0d56f126c4a6776","unresolved":false,"context_lines":[{"line_number":181,"context_line":"* Specification for the method"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"  * Description"},{"line_number":184,"context_line":"    API extension discovery"},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"  * Method type"},{"line_number":187,"context_line":"    GET"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_9909f534","line":184,"updated":"2015-01-13 11:51:10.000000000","message":"This line (and others in the list) don\u0027t get formatted properly. They end up as continutations of the previous line, so it looks like a single bullet:\n\n    * Description API extension discovery\n\n I think we need another deeper level of bullet points, or something else.","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"23746de2f12fbdf794cbdd1dff13297f33d4fb3c","unresolved":false,"context_lines":[{"line_number":181,"context_line":"* Specification for the method"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"  * Description"},{"line_number":184,"context_line":"    API extension discovery"},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"  * Method type"},{"line_number":187,"context_line":"    GET"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_83f16998","line":184,"in_reply_to":"3a961159_9909f534","updated":"2015-01-14 00:39:43.000000000","message":"Done","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"94024e2a7fdcf973758cce67b0d56f126c4a6776","unresolved":false,"context_lines":[{"line_number":300,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":301,"context_line":""},{"line_number":302,"context_line":"None yet."},{"line_number":303,"context_line":"We can get API URLs, HTTP methods(GET, POST, ..) with this feature, but API"},{"line_number":304,"context_line":"documents needs request/response body formats also and this spec doesn\u0027t cover"},{"line_number":305,"context_line":"it as the first step. The feature which provides request/response body formats"},{"line_number":306,"context_line":"will be discussed on the other spec across projects. After that we will be"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3a961159_f9e919e4","line":303,"updated":"2015-01-13 11:51:10.000000000","message":"nit: missing space before (","commit_id":"4e25656692a04e63fa520171fbba7c983d2f26c0"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"cb95d45d810109ff2d71b0e8efc4ab0ffe3593b5","unresolved":false,"context_lines":[{"line_number":46,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"JSON-Home is a standard, and Keystone has already implemented JSON-Home on"},{"line_number":49,"context_line":"Keystone REST API[1]. This spec/blueprint proposes JSON-Home support for Nova"},{"line_number":50,"context_line":"v2.1 API."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"On JSON-Home spec[2], JSON-Home works only if passing \u0027application/json-home\u0027"}],"source_content_type":"text/x-rst","patch_set":10,"id":"3a961159_76718044","line":49,"updated":"2015-01-14 16:10:20.000000000","message":"There\u0027s an rst syntx for footnotes: http://docutils.sourceforge.net/docs/user/rst/quickref.html#footnotes","commit_id":"d3e1575e0310552edf49cfdc81a84292efa2cf1c"}],"specs/liberty/approved/nova-api-json-home.rst":[{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"0e9767ab6828853107659fc3d1620e07c5e0967b","unresolved":false,"context_lines":[{"line_number":86,"context_line":"some info about what the relationship is and describe the resource."},{"line_number":87,"context_line":"Keystone publishes http://docs.openstack.org/api/openstack-identity/3/rel as"},{"line_number":88,"context_line":"it. In addition, Nova has already published its XSD files at"},{"line_number":89,"context_line":"http://docs.openstack.org/api/openstack-compute/2/xsd. So Nova should publish"},{"line_number":90,"context_line":"a similar location for consistency. For v2.1 resources, the relationship type"},{"line_number":91,"context_line":"link will be http://docs.openstack.org/api/openstack-compute/2.1/rel as the"},{"line_number":92,"context_line":"above sample. On v2.1 API + microversions, we will continue using the same"}],"source_content_type":"text/x-rst","patch_set":17,"id":"9a80dd14_dbe54add","line":89,"updated":"2015-03-17 13:44:05.000000000","message":"I didn\u0027t find it , is it wrong link or updated?\n\nhttp://docs.openstack.org/api/openstack-compute/2/xsd","commit_id":"bdd73f949a9295f11c9ba7560cb5a8385de57503"},{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"3243db186804c10e72b28d84354468f94422d791","unresolved":false,"context_lines":[{"line_number":86,"context_line":"some info about what the relationship is and describe the resource."},{"line_number":87,"context_line":"Keystone publishes http://docs.openstack.org/api/openstack-identity/3/rel as"},{"line_number":88,"context_line":"it. In addition, Nova has already published its XSD files at"},{"line_number":89,"context_line":"http://docs.openstack.org/api/openstack-compute/2/xsd. So Nova should publish"},{"line_number":90,"context_line":"a similar location for consistency. For v2.1 resources, the relationship type"},{"line_number":91,"context_line":"link will be http://docs.openstack.org/api/openstack-compute/2.1/rel as the"},{"line_number":92,"context_line":"above sample. On v2.1 API + microversions, we will continue using the same"}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a6ced46_8ab479f3","line":89,"in_reply_to":"9a80dd14_6240a0a5","updated":"2015-03-23 10:22:07.000000000","message":"ok, got it , thanks","commit_id":"bdd73f949a9295f11c9ba7560cb5a8385de57503"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"5dc20c60a7d4797dd09a39b1c38e2ffbc98c791f","unresolved":false,"context_lines":[{"line_number":86,"context_line":"some info about what the relationship is and describe the resource."},{"line_number":87,"context_line":"Keystone publishes http://docs.openstack.org/api/openstack-identity/3/rel as"},{"line_number":88,"context_line":"it. In addition, Nova has already published its XSD files at"},{"line_number":89,"context_line":"http://docs.openstack.org/api/openstack-compute/2/xsd. So Nova should publish"},{"line_number":90,"context_line":"a similar location for consistency. For v2.1 resources, the relationship type"},{"line_number":91,"context_line":"link will be http://docs.openstack.org/api/openstack-compute/2.1/rel as the"},{"line_number":92,"context_line":"above sample. On v2.1 API + microversions, we will continue using the same"}],"source_content_type":"text/x-rst","patch_set":17,"id":"9a80dd14_6240a0a5","line":89,"in_reply_to":"9a80dd14_dbe54add","updated":"2015-03-20 01:08:02.000000000","message":"@jichenjc\n\nI also had the same thinking when I saw this on Keystone side. but the above URL is not for finding, just namespace for the identification.\nSo the URL is not wrong.","commit_id":"bdd73f949a9295f11c9ba7560cb5a8385de57503"},{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"0e9767ab6828853107659fc3d1620e07c5e0967b","unresolved":false,"context_lines":[{"line_number":161,"context_line":"response bodies. This JSON-Home feature provides available API URLs of each"},{"line_number":162,"context_line":"microversion which is specified with \"X-OpenStack-Nova-API-Version\" in a"},{"line_number":163,"context_line":"header. If not specifying a microversion, this feature provides available API"},{"line_number":164,"context_line":"URLs of minimum microversion. \"JSON-Schema on JSON-Home\" will provide available"},{"line_number":165,"context_line":"request/response bodies of the specified microversion also based on the same"},{"line_number":166,"context_line":"semantic."},{"line_number":167,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"9a80dd14_9bbaf26f","line":164,"updated":"2015-03-17 13:44:05.000000000","message":"minimum -\u003e maximum?","commit_id":"bdd73f949a9295f11c9ba7560cb5a8385de57503"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"5dc20c60a7d4797dd09a39b1c38e2ffbc98c791f","unresolved":false,"context_lines":[{"line_number":161,"context_line":"response bodies. This JSON-Home feature provides available API URLs of each"},{"line_number":162,"context_line":"microversion which is specified with \"X-OpenStack-Nova-API-Version\" in a"},{"line_number":163,"context_line":"header. If not specifying a microversion, this feature provides available API"},{"line_number":164,"context_line":"URLs of minimum microversion. \"JSON-Schema on JSON-Home\" will provide available"},{"line_number":165,"context_line":"request/response bodies of the specified microversion also based on the same"},{"line_number":166,"context_line":"semantic."},{"line_number":167,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"9a80dd14_a21d38c0","line":164,"in_reply_to":"9a80dd14_9bbaf26f","updated":"2015-03-20 01:08:02.000000000","message":"No, minimum is right.\nOn microversions mechanism, when not specifying a microversion on client side, Nova works on minimum microversion as the default. On JSON-Home, Nova should work on minimum for consistent behavior.","commit_id":"bdd73f949a9295f11c9ba7560cb5a8385de57503"},{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"3243db186804c10e72b28d84354468f94422d791","unresolved":false,"context_lines":[{"line_number":161,"context_line":"response bodies. This JSON-Home feature provides available API URLs of each"},{"line_number":162,"context_line":"microversion which is specified with \"X-OpenStack-Nova-API-Version\" in a"},{"line_number":163,"context_line":"header. If not specifying a microversion, this feature provides available API"},{"line_number":164,"context_line":"URLs of minimum microversion. \"JSON-Schema on JSON-Home\" will provide available"},{"line_number":165,"context_line":"request/response bodies of the specified microversion also based on the same"},{"line_number":166,"context_line":"semantic."},{"line_number":167,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a6ced46_4a8fe123","line":164,"in_reply_to":"9a80dd14_a21d38c0","updated":"2015-03-23 10:22:07.000000000","message":"ok, my fault, double check the spec again and it\u0027s right","commit_id":"bdd73f949a9295f11c9ba7560cb5a8385de57503"},{"author":{"_account_id":12175,"name":"Eli Qiao","email":"qiaoliyong@gmail.com","username":"Eli"},"change_message_id":"84fc5d8c3ff795de993de2dd13ff4b9a5db391cb","unresolved":false,"context_lines":[{"line_number":92,"context_line":"above sample. On v2.1 API + microversions, we will continue using the same"},{"line_number":93,"context_line":"endpoint(/v2.1) and we can use the same link for all microversions."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"If querying against a specific URL(eg. GET /v2.1/{project_id}/servers), client"},{"line_number":96,"context_line":"can get more detail information(available HTTP methods, format) on \"hints\""},{"line_number":97,"context_line":"attribute like:"},{"line_number":98,"context_line":""}],"source_content_type":"text/x-rst","patch_set":18,"id":"9abe1de1_b7d008cb","line":95,"updated":"2015-04-27 08:40:36.000000000","message":"1 question: what does the specific URL mean?\nsomething like http://liyong:8774/v2.1/52a0ee83fb524376bd603547aea415a3/servers\n\ndo you mean, add more information to this api resp body?\n\nEli.","commit_id":"f23c98f60fcee7fc2373ed94583787c97515cb2b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"143fb4ff80cd4cd9f9e6efe3200f3af3b8674280","unresolved":false,"context_lines":[{"line_number":151,"context_line":"API definitions with \"hints\" of JSON-Home (JSON-Schema on JSON-Home) as an"},{"line_number":152,"context_line":"OpenStack specific feature. However, the feature is out of scope from this"},{"line_number":153,"context_line":"spec and this spec covers the standard scope of JSON-Home without JSON-Schema."},{"line_number":154,"context_line":"The feature needs the other spec and we need to discuss it across projects."},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"The API router class already contains necessary information for JSON-Home,"},{"line_number":157,"context_line":"and we can implement JSON-Home feature just by arranging the information to"}],"source_content_type":"text/x-rst","patch_set":18,"id":"7ad32947_00f3e774","line":154,"updated":"2015-04-27 16:39:14.000000000","message":"I guess we can let users request a different mime type in the future.","commit_id":"f23c98f60fcee7fc2373ed94583787c97515cb2b"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"15bf5bcd48c09186b0dd0bb2a037f97b02957d71","unresolved":false,"context_lines":[{"line_number":302,"context_line":"to implement Tempest test for JSON-Home."},{"line_number":303,"context_line":"Ideally, this feature of Nova will use the same Tempest test mechanism as"},{"line_number":304,"context_line":"Keystone and test JSON-Home on the gate. If we do that, we can reduce the"},{"line_number":305,"context_line":"test code on Tempest and verify consistent JSON-Home across projects."},{"line_number":306,"context_line":""},{"line_number":307,"context_line":"Documentation Impact"},{"line_number":308,"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":18,"id":"1aca2d91_96a7214f","line":305,"updated":"2015-05-06 20:14:03.000000000","message":"I wonder if this is a good candidate for in tree functional testing.","commit_id":"f23c98f60fcee7fc2373ed94583787c97515cb2b"}]}
