)]}'
{"doc/source/glanceapi.rst":[{"author":{"_account_id":5202,"name":"Erno Kuvaja","email":"jokke@usr.fi","username":"jokke"},"change_message_id":"dfd370a89329dd4cb9f1a800631d5674f6086e79","unresolved":false,"context_lines":[{"line_number":61,"context_line":"delete images, and manipulate image metadata.  Nova acts as a proxy to Glance"},{"line_number":62,"context_line":"for these image-related calls.  It\u0027s important to note that the image-related"},{"line_number":63,"context_line":"calls in the Compute v2 API are a proper subset of the calls available in the"},{"line_number":64,"context_line":"Images APIs."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Currently Nova uses the Images v1 API, but work is in progress to convert Nova"},{"line_number":67,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a061dce_28030944","line":64,"updated":"2016-04-05 00:35:07.000000000","message":"Perhaps worth of mentioning that one can also deploy multiple glance nodes which of some might provide v1/v2 for internal consumers like Nova and some external only nodes provide v2 api for public use. There is no reason to rely on Nova\u0027s image API proxy if one does not want to expose v1 to public endpoints.","commit_id":"1c05720174d9cab8465710fd00d0b1b2f62289b0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"83c62073dac98fb80bff237ac6470d6e03932079","unresolved":false,"context_lines":[{"line_number":61,"context_line":"delete images, and manipulate image metadata.  Nova acts as a proxy to Glance"},{"line_number":62,"context_line":"for these image-related calls.  It\u0027s important to note that the image-related"},{"line_number":63,"context_line":"calls in the Compute v2 API are a proper subset of the calls available in the"},{"line_number":64,"context_line":"Images APIs."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Currently Nova uses the Images v1 API, but work is in progress to convert Nova"},{"line_number":67,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a061dce_59ba8d24","line":64,"in_reply_to":"9a061dce_28030944","updated":"2016-04-05 02:44:31.000000000","message":"That\u0027s a good point, Erno.  I think I may make it in the v2 section (which is a bit short) so that it\u0027s clear that v2 is not only open to development, it\u0027s actually in use in some clouds as a public-facing Images endpoint.","commit_id":"1c05720174d9cab8465710fd00d0b1b2f62289b0"},{"author":{"_account_id":455,"name":"Stuart McLaren","email":"stuart.mclaren@hpe.com","username":"stuart-mclaren"},"change_message_id":"5d6455eac2a768e57bb7fedaa02bd6df835ea81d","unresolved":false,"context_lines":[{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"},{"line_number":32,"context_line":"as \"OpenStack\", a cloud exposing an OpenStack Images API must include the"},{"line_number":33,"context_line":"Glance Images API implementation code.  Thus, although conceptually"},{"line_number":34,"context_line":"independent, the OpenStack Images APIs are intimately associated with Glance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"**References**"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_c877db38","line":33,"range":{"start_line":32,"start_character":33,"end_line":33,"end_character":37},"updated":"2016-04-05 10:51:43.000000000","message":"\"a cloud exposing an OpenStack Images API must include the Glance Images API implementation code\"\n\nI don\u0027t fully understand this. (The meaning of \u0027required designated section\u0027 isn\u0027t totally obvious to me -- is it defined/explained anywhere?)\n\nI thought your deployment would be designated eg \"OpenStack Platorm\" if it passed the relevant tempest tests selected by DefCore?\n\nThis is a bit like a Turing test. Anything that implements the API correctly would pass. Surely there\u0027s no test that automatically deduces if it\u0027s the traditional Glance code being run, or a re-implementation in Go (like Hummingbird for Swift). Can a \u0027Go\u0027 based deployment fail to be verified as eg OpenStack Platform? If so, how?","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":455,"name":"Stuart McLaren","email":"stuart.mclaren@hpe.com","username":"stuart-mclaren"},"change_message_id":"cfda625e5d98d4a78bf62d2e9f2fe64603886933","unresolved":false,"context_lines":[{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"},{"line_number":32,"context_line":"as \"OpenStack\", a cloud exposing an OpenStack Images API must include the"},{"line_number":33,"context_line":"Glance Images API implementation code.  Thus, although conceptually"},{"line_number":34,"context_line":"independent, the OpenStack Images APIs are intimately associated with Glance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"**References**"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_2f3d228f","line":33,"range":{"start_line":32,"start_character":33,"end_line":33,"end_character":37},"in_reply_to":"9a061dce_235543c5","updated":"2016-04-07 16:10:09.000000000","message":"\u003e Hope that helps!\n\nYes, very helpful Mark -- thanks.\n\nThe legal \u0027use the code\u0027 side of this is something I definitely hadn\u0027t realised up to now.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"1eb4655b3809127dbb0cb7c84b853d0a8ad0f665","unresolved":false,"context_lines":[{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"},{"line_number":32,"context_line":"as \"OpenStack\", a cloud exposing an OpenStack Images API must include the"},{"line_number":33,"context_line":"Glance Images API implementation code.  Thus, although conceptually"},{"line_number":34,"context_line":"independent, the OpenStack Images APIs are intimately associated with Glance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"**References**"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_00d90857","line":33,"range":{"start_line":32,"start_character":33,"end_line":33,"end_character":37},"in_reply_to":"9a061dce_2f3d228f","updated":"2016-04-07 17:59:32.000000000","message":"Thanks, Mark.  I\u0027ll add some of the references you provided.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0f8b53ba20952cd3923168858fd25a90977e9e9d","unresolved":false,"context_lines":[{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"},{"line_number":32,"context_line":"as \"OpenStack\", a cloud exposing an OpenStack Images API must include the"},{"line_number":33,"context_line":"Glance Images API implementation code.  Thus, although conceptually"},{"line_number":34,"context_line":"independent, the OpenStack Images APIs are intimately associated with Glance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"**References**"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_f1155e49","line":33,"range":{"start_line":32,"start_character":33,"end_line":33,"end_character":37},"in_reply_to":"9a061dce_81c65947","updated":"2016-04-05 14:01:36.000000000","message":"Good questions, Stuart.  All I could find were the 2 refs below, the first one explaining what a \"designated section\" is, and the second to the repo where the docs saying what\u0027s currently \"designated\" are.  I do know that \"passing\" defcore has been defined to be (a) passing the tests (b) using code containing the designated sections.\n\nI will add a few DefCore people to the review so they can verify the paragraph as a statement of fact about DefCore, Glance, and designated sections (and maybe provide a more specific reference).\n\nI don\u0027t want to provide a defense of the position here; all I want is to make a statement of how DefCore and Glance are related.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":8122,"name":"Cyril Roelandt","email":"cyril@redhat.com","username":"cyril.roelandt.enovance"},"change_message_id":"1833d7f26b8c9a4ab8ebd9cf30a240f3dcf5ea56","unresolved":false,"context_lines":[{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"},{"line_number":32,"context_line":"as \"OpenStack\", a cloud exposing an OpenStack Images API must include the"},{"line_number":33,"context_line":"Glance Images API implementation code.  Thus, although conceptually"},{"line_number":34,"context_line":"independent, the OpenStack Images APIs are intimately associated with Glance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"**References**"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_81c65947","line":33,"range":{"start_line":32,"start_character":33,"end_line":33,"end_character":37},"in_reply_to":"9a061dce_c877db38","updated":"2016-04-05 12:51:25.000000000","message":"That is an interesting concern. I would indeed expect tests to be run in \"black box\" setup.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"1b06400bfb2f7212a75df5bc37524fb38452dd13","unresolved":false,"context_lines":[{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"},{"line_number":32,"context_line":"as \"OpenStack\", a cloud exposing an OpenStack Images API must include the"},{"line_number":33,"context_line":"Glance Images API implementation code.  Thus, although conceptually"},{"line_number":34,"context_line":"independent, the OpenStack Images APIs are intimately associated with Glance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"**References**"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_235543c5","line":33,"range":{"start_line":32,"start_character":33,"end_line":33,"end_character":37},"in_reply_to":"9a061dce_f1155e49","updated":"2016-04-07 15:22:33.000000000","message":"Hi Folks, DefCore Committee Co-chair here.  Some references you may find useful:\n\n\nFirst some history.  When we talk about Designated Sections with respect to DefCore, we\u0027re generally talking about what stems from this section of the principles adopted by the Board of Directors back in 2014:\nhttp://git.openstack.org/cgit/openstack/defcore/tree/doc/source/process/CoreDefinition.rst#n71\n\n\nPerhaps a more straightforward definition of Designated Sections can be found in the DefCore Lexicon:\nhttp://git.openstack.org/cgit/openstack/defcore/tree/doc/source/process/Lexicon.rst#n54\n\n\nWhat\u0027s designated from Glance as of the most recent Board of Directors-approved DefCore Guideline:\nhttp://git.openstack.org/cgit/openstack/defcore/tree/2016.01.json#n2710\n\n\nIn a nutshell, to qualify for the OpenStack Powered(TM) logo and trademark license agreement from the OpenStack Foundation, you not only have to pass the required tests, but must also be using upstream code that is covered under designated sections.  So if you (for example) rewrite the Glance API in Go, you might conceivably pass all the tests--but since you\u0027re not using the upstream code the OpenStack Foundation will refuse to grant you a license to call yourself OpenStack.\n\n\nThere is currently no test that inspects your implementation code to see if you\u0027re actually using the upstream code covered by designated sections.  Instead, that\u0027s basically enforced by legal language in the license agreement.\n\n\nHope that helps!","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":455,"name":"Stuart McLaren","email":"stuart.mclaren@hpe.com","username":"stuart-mclaren"},"change_message_id":"5d6455eac2a768e57bb7fedaa02bd6df835ea81d","unresolved":false,"context_lines":[{"line_number":84,"context_line":"API if one does not want to expose the Images v1 API to public endpoints."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"The Future"},{"line_number":87,"context_line":"**********"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"During the long and tumultuous design phase of what has since become an"},{"line_number":90,"context_line":"independent service named \"Glare\" (the Glance Artifacts Repository), the Glance"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_936eb42d","line":87,"range":{"start_line":87,"start_character":0,"end_line":87,"end_character":10},"updated":"2016-04-05 10:51:43.000000000","message":"This doc seems to focus on the images api.\n\nThe future of that will be\n\n* allowing deployment of nova/cinder/etc without requiring v1\n* v2 for a quite a long time (defcore)\n\n\n\nI\u0027d be inclined to put the glare stuff in a new glare/artifacts focused doc (perhaps minus some of the sausage factory details :-) ). I think we\u0027ll need a glare doc at some point, and that\u0027s a more natural fit for this info.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0f8b53ba20952cd3923168858fd25a90977e9e9d","unresolved":false,"context_lines":[{"line_number":84,"context_line":"API if one does not want to expose the Images v1 API to public endpoints."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"The Future"},{"line_number":87,"context_line":"**********"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"During the long and tumultuous design phase of what has since become an"},{"line_number":90,"context_line":"independent service named \"Glare\" (the Glance Artifacts Repository), the Glance"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_14e8c0b3","line":87,"range":{"start_line":87,"start_character":0,"end_line":87,"end_character":10},"in_reply_to":"9a061dce_1c162ca7","updated":"2016-04-05 14:01:36.000000000","message":"Stuart and Cyril, I disagree.\n\nThe whole point of this update is to address the \"What about Images v3?\" question, so I think this info needs to be here.  It could perhaps be moved to a better location later, but my concern is to make sure this is an accurate statement that is google-able.  So let\u0027s please concentrate on the text, make sure all cores are on board with this, and get it published.  Then I\u0027ll be happy to restructure/move/etc.\n\nMy primary concern is to make sure we\u0027re all on the same page before the summit.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":8122,"name":"Cyril Roelandt","email":"cyril@redhat.com","username":"cyril.roelandt.enovance"},"change_message_id":"1833d7f26b8c9a4ab8ebd9cf30a240f3dcf5ea56","unresolved":false,"context_lines":[{"line_number":84,"context_line":"API if one does not want to expose the Images v1 API to public endpoints."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"The Future"},{"line_number":87,"context_line":"**********"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"During the long and tumultuous design phase of what has since become an"},{"line_number":90,"context_line":"independent service named \"Glare\" (the Glance Artifacts Repository), the Glance"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_1c162ca7","line":87,"range":{"start_line":87,"start_character":0,"end_line":87,"end_character":10},"in_reply_to":"9a061dce_936eb42d","updated":"2016-04-05 12:51:25.000000000","message":"+1 Stuart. It may be easier to start such a file now than moving stuff between files later. It might still be nice to keep the \"Glare is not v3\" part here.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":455,"name":"Stuart McLaren","email":"stuart.mclaren@hpe.com","username":"stuart-mclaren"},"change_message_id":"5d6455eac2a768e57bb7fedaa02bd6df835ea81d","unresolved":false,"context_lines":[{"line_number":86,"context_line":"The Future"},{"line_number":87,"context_line":"**********"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"During the long and tumultuous design phase of what has since become an"},{"line_number":90,"context_line":"independent service named \"Glare\" (the Glance Artifacts Repository), the Glance"},{"line_number":91,"context_line":"community loosely spoke about the Artifacts API being \"Glance v3\".  This,"},{"line_number":92,"context_line":"however, was only a shorthand way of speaking of the Artifacts effort.  The"},{"line_number":93,"context_line":"Artifacts API can\u0027t be the Images v3 API since Artifacts are not the same as"},{"line_number":94,"context_line":"Images.  Conceptually, a virtual machine image could be an Artifact, and the"},{"line_number":95,"context_line":"Glare code has been designed to be compatible with the Images v2 API.  But at"},{"line_number":96,"context_line":"this time, there are no plans to implement an Images v3 API."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"As far as the Glance/Glare relationship goes, it\u0027s too early to say what the"},{"line_number":99,"context_line":"future holds.  While it\u0027s evident that there\u0027s a need for an Artifact"},{"line_number":100,"context_line":"Repository in OpenStack, whether it will be as ubiquitous as the need for an"},{"line_number":101,"context_line":"Images Repository isn\u0027t clear.  On the other hand, industry trends could go in"},{"line_number":102,"context_line":"the opposite direction where everyone needs Artifacts and deployers view images"},{"line_number":103,"context_line":"as simply another type of digital artifact.  As Yogi Berra, an experienced"},{"line_number":104,"context_line":"manager, once said, \"It\u0027s tough to make predictions, especially about the"},{"line_number":105,"context_line":"future.\""},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"Authentication"},{"line_number":108,"context_line":"--------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_53b53cec","line":105,"range":{"start_line":89,"start_character":0,"end_line":105,"end_character":8},"updated":"2016-04-05 10:51:43.000000000","message":"This doc is called \u0027glanceapi.rst\u0027 but focuses on the images api (eg ignoring the metadef stuff).\n\nShould we think about restructuring things a bit?\n\neg have a top level\nglanceapi.rst that basically points to other docs, eg imagesapi.rst, artifactsapi.rst, glancemetadefcatalogapi.rst\n\nEven different directories, eg\n\nimages/\nmetadefs/\nartifacts/","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0f8b53ba20952cd3923168858fd25a90977e9e9d","unresolved":false,"context_lines":[{"line_number":86,"context_line":"The Future"},{"line_number":87,"context_line":"**********"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"During the long and tumultuous design phase of what has since become an"},{"line_number":90,"context_line":"independent service named \"Glare\" (the Glance Artifacts Repository), the Glance"},{"line_number":91,"context_line":"community loosely spoke about the Artifacts API being \"Glance v3\".  This,"},{"line_number":92,"context_line":"however, was only a shorthand way of speaking of the Artifacts effort.  The"},{"line_number":93,"context_line":"Artifacts API can\u0027t be the Images v3 API since Artifacts are not the same as"},{"line_number":94,"context_line":"Images.  Conceptually, a virtual machine image could be an Artifact, and the"},{"line_number":95,"context_line":"Glare code has been designed to be compatible with the Images v2 API.  But at"},{"line_number":96,"context_line":"this time, there are no plans to implement an Images v3 API."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"As far as the Glance/Glare relationship goes, it\u0027s too early to say what the"},{"line_number":99,"context_line":"future holds.  While it\u0027s evident that there\u0027s a need for an Artifact"},{"line_number":100,"context_line":"Repository in OpenStack, whether it will be as ubiquitous as the need for an"},{"line_number":101,"context_line":"Images Repository isn\u0027t clear.  On the other hand, industry trends could go in"},{"line_number":102,"context_line":"the opposite direction where everyone needs Artifacts and deployers view images"},{"line_number":103,"context_line":"as simply another type of digital artifact.  As Yogi Berra, an experienced"},{"line_number":104,"context_line":"manager, once said, \"It\u0027s tough to make predictions, especially about the"},{"line_number":105,"context_line":"future.\""},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"Authentication"},{"line_number":108,"context_line":"--------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a061dce_3464e4e3","line":105,"range":{"start_line":89,"start_character":0,"end_line":105,"end_character":8},"in_reply_to":"9a061dce_53b53cec","updated":"2016-04-05 14:01:36.000000000","message":"Good idea, but let\u0027s make that a different effort.","commit_id":"85ade7ee92a82737073330960e7c8066ff587939"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"6405cd959146d6cdfde24815cf7333e19a0c86ed","unresolved":false,"context_lines":[{"line_number":71,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."},{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_867126ab","line":74,"updated":"2016-04-25 14:54:34.000000000","message":"I think Mike is right here. We haven\u0027t agreed on removing v1 but deprecate it. There are good arguments against removing APIs in general and I think we should go through those before making and statement on it.\nCan we amend this part in a follow-up patch? Removing the part where we say it will be removed should be enough.\n\nTo Kairat\u0027s comment. I don\u0027t think having the code in the codebase means it\u0027s supported. It\u0027s supported now but we can completely deprecate it and not accept patches anymore. Then there comes the discussion on \"Why on earth wouldn\u0027t you accept a fix for something broken?\"\n\nThis is a good discussion to have, perhaps out of the scope of this patch.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":11391,"name":"Mikhail Fedosin","email":"mfedosin@redhat.com","username":"fedosinme"},"change_message_id":"a57560ffb8cc87a6a578249c266ec52e62af5bbc","unresolved":false,"context_lines":[{"line_number":71,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."},{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a18252c_79b1c846","line":74,"range":{"start_line":74,"start_character":0,"end_line":74,"end_character":18},"updated":"2016-04-14 20:54:53.000000000","message":"Maybe I missed something, but I thought there was a decision not to remove v1 from Glance repo, but disable it by default.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":14676,"name":"Kairat Kushaev","email":"kkushaev@mirantis.com","username":"kairat_kushaev"},"change_message_id":"9d74d8e064f27f1d0d9babdb3a974818a0628bbb","unresolved":false,"context_lines":[{"line_number":71,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."},{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_8cd93bf6","line":74,"in_reply_to":"1a122d0e_867126ab","updated":"2016-04-26 04:32:35.000000000","message":"If we are not accepting patches for v1 then bug fixes also will be rejected (it means not supported IIUC). In that case we potentially can store broken code in glance codebase. So it is not clear for me why do we need to have that code at all and do not follow standard deprecation procedure for v1 and store that code forever. I think we can extend deprecation cycle but we also need to remove that code one day. Keeping that code in glance codebase looks like tech debt.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"8fa0ab4c3cd21a275dc9a7982d69ea06a2e76a21","unresolved":false,"context_lines":[{"line_number":71,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."},{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"}],"source_content_type":"text/x-rst","patch_set":3,"id":"dab17558_76ebfcb0","line":74,"in_reply_to":"1a122d0e_8cd93bf6","updated":"2016-05-09 20:17:41.000000000","message":"OK, I will remove the expression \u0027ultimately removed\u0027 and add a reference to the actual OpenStack policy.  As we go through the deprecation steps in the policy, we\u0027ll find out whether v1 could be removed, and if so, when.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"92397f34cc31d262982dfe5fedf0ca88ae9bf759","unresolved":false,"context_lines":[{"line_number":71,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."},{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_9003850f","line":74,"range":{"start_line":74,"start_character":0,"end_line":74,"end_character":18},"in_reply_to":"5a18252c_4ab4da33","updated":"2016-04-15 14:19:01.000000000","message":"I\u0027m not sure we\u0027ve made a binding decision on the deprecation strategy for v1 yet.  I think what will happen (but this is just me talking) is that we\u0027ll announce v1 as \u0027deprecated\u0027 and say that we will remove it effective release X (meaning \u0027X\u0027 as a variable here, not the X-release!) and listen to what the broader openstack community has to say (i.e., we\u0027ll see if anyone screams).\n\nI agree with Kairat that we really actually want to remove it, but I see your point, Mike, that some people might want it for their own nefarious purposes.  I look at the situation like what happened when XML support was removed from the Compute API.  I couldn\u0027t believe they removed it because it seemed like a super-enormous non-backward compatible change, but they did ... and it turned out that not a lot of people were actually using XML, and the people who had custom scripts/tooling that used it rewrote their scripts.  So maybe not a lot of people expose Glance v1 to end users, and maybe it won\u0027t be missed!  We\u0027ll have to wait and see.\n\nAnyway, I think this statement is OK, but I\u0027ll bring it to the PTL\u0027s attention to verify.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":14676,"name":"Kairat Kushaev","email":"kkushaev@mirantis.com","username":"kairat_kushaev"},"change_message_id":"2629cb4acaeef2c03fb77b1485cc1137aafb3d0f","unresolved":false,"context_lines":[{"line_number":71,"context_line":"(and other OpenStack services that consume images) to using the Images v2 API."},{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a18252c_4ab4da33","line":74,"range":{"start_line":74,"start_character":0,"end_line":74,"end_character":18},"in_reply_to":"5a18252c_79b1c846","updated":"2016-04-15 06:55:43.000000000","message":"I would prefer to delete that one day because disabling means it is supported. Otherwise, why do we need to support deprecated api forever? Maybe not now, but in far far future we need to get rid of it IMO.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":8158,"name":"Hemanth Makkapati","email":"makstacker+osgerrit@gmail.com","username":"hemanth.makkapati"},"change_message_id":"7b4a523fd4d88014373913a2fe7f084ba609d8c6","unresolved":false,"context_lines":[{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"},{"line_number":78,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"9a061dce_d9d06ffa","line":75,"updated":"2016-04-08 16:29:47.000000000","message":"Should we explicitly say that as of today Openstack can\u0027t be installed without Glance v1?\nThe above paragraph implicitly hints that, just doesn\u0027t state it explicitly.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"92397f34cc31d262982dfe5fedf0ca88ae9bf759","unresolved":false,"context_lines":[{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"},{"line_number":78,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_ab6294d6","line":75,"in_reply_to":"5a18252c_94553dc8","updated":"2016-04-15 14:19:01.000000000","message":"I agree with Nikhil, I\u0027m inclined to leave the text as-is.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"f9e356da669f38164f911affc1072913c6723af6","unresolved":false,"context_lines":[{"line_number":72,"context_line":"Once that occurs, it will be possible to deploy OpenStack without deploying the"},{"line_number":73,"context_line":"Images v1 API.  At that point, the Images v1 API will be deprecated and"},{"line_number":74,"context_line":"ultimately removed, following the standard OpenStack deprecation policy."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Images v2 API"},{"line_number":77,"context_line":"*************"},{"line_number":78,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a18252c_94553dc8","line":75,"in_reply_to":"9a061dce_d9d06ffa","updated":"2016-04-12 05:09:25.000000000","message":"I guess the point we want to make is that v1 is about to be deprecated and once we do that, it may be unlikely that we will come back and update this document :-)\n\nIt\u0027s (v1) required by Nova, comes in default with devstack so sorta implied. I am okay with that information not being here.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":11391,"name":"Mikhail Fedosin","email":"mfedosin@redhat.com","username":"fedosinme"},"change_message_id":"a57560ffb8cc87a6a578249c266ec52e62af5bbc","unresolved":false,"context_lines":[{"line_number":97,"context_line":"Artifacts API can\u0027t be the Images v3 API since Artifacts are not the same as"},{"line_number":98,"context_line":"Images.  Conceptually, a virtual machine image could be an Artifact, and the"},{"line_number":99,"context_line":"Glare code has been designed to be compatible with the Images v2 API.  But at"},{"line_number":100,"context_line":"this time, there are no plans to implement an Images v3 API."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"As far as the Glance/Glare relationship goes, it\u0027s too early to say what the"},{"line_number":103,"context_line":"future holds.  While it\u0027s evident that there\u0027s a need for an Artifact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a18252c_d48ee32c","line":100,"updated":"2016-04-14 20:54:53.000000000","message":"It depends on how you look.... For sure there are no plans to develop *standalone* Images v3 API, but Glare has its own implementation of Images API as a part of Artifacts API.\nIt\u0027s extremely compatible with v2 - only url prefix is different(\u0027/v1/artifacts/images\u0027 vs. \u0027/v2/images\u0027), but we must remember, that also Glare doesn\u0027t support v2 rudiments like old sorting and tag syntaxes, filters resembling \u0027size_min\u0027 or \u0027min_ram_max\u0027, 2 different tag API and so on. \n\nUltimately we tried to follow the principle \"There is the only one API call to perform the action\". So, basically, we may consider that Glare has cleaner (or reductive) implementation of Image v2 API.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":14676,"name":"Kairat Kushaev","email":"kkushaev@mirantis.com","username":"kairat_kushaev"},"change_message_id":"2629cb4acaeef2c03fb77b1485cc1137aafb3d0f","unresolved":false,"context_lines":[{"line_number":97,"context_line":"Artifacts API can\u0027t be the Images v3 API since Artifacts are not the same as"},{"line_number":98,"context_line":"Images.  Conceptually, a virtual machine image could be an Artifact, and the"},{"line_number":99,"context_line":"Glare code has been designed to be compatible with the Images v2 API.  But at"},{"line_number":100,"context_line":"this time, there are no plans to implement an Images v3 API."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"As far as the Glance/Glare relationship goes, it\u0027s too early to say what the"},{"line_number":103,"context_line":"future holds.  While it\u0027s evident that there\u0027s a need for an Artifact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a18252c_eab32608","line":100,"in_reply_to":"5a18252c_d48ee32c","updated":"2016-04-15 06:55:43.000000000","message":"and there are plans to make Glare API stable because now it is expiremental. I think it is worth to mention in spec.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"92397f34cc31d262982dfe5fedf0ca88ae9bf759","unresolved":false,"context_lines":[{"line_number":97,"context_line":"Artifacts API can\u0027t be the Images v3 API since Artifacts are not the same as"},{"line_number":98,"context_line":"Images.  Conceptually, a virtual machine image could be an Artifact, and the"},{"line_number":99,"context_line":"Glare code has been designed to be compatible with the Images v2 API.  But at"},{"line_number":100,"context_line":"this time, there are no plans to implement an Images v3 API."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"As far as the Glance/Glare relationship goes, it\u0027s too early to say what the"},{"line_number":103,"context_line":"future holds.  While it\u0027s evident that there\u0027s a need for an Artifact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_e6e84319","line":100,"in_reply_to":"5a18252c_eab32608","updated":"2016-04-15 14:19:01.000000000","message":"Thanks for the clarifications, Mike and Kairat.  I\u0027d like to leave this text the way it is for now, as the key point is to address community concerns that the Glance team is working on Images v3 before v1 is even deprecated and before v2 is being consumed by all openstack services.  I think the points you make would be better addressed in the Glare documentation.\n\nStuart made a really good suggestion on an earlier patch that the Glance docs could use a reorganization, as we\u0027ve got docs aimed at developers, Images API consumers, metadefs API consumers, and operators all mixed together.  There\u0027s at least one artifacts-related page in there, too.  Maybe if there\u0027s some free time on Friday at the summit, we could have a quick discussion about reorganizing the docs.  I\u0027m not sure what your plans are for how the Glare docs will fit in.","commit_id":"9e8e490e2220d74c734fd403bb08e81c22fb6eb6"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"ccaf4d60f5f1bd98390661b8bc984a3bc5cc1440","unresolved":false,"context_lines":[{"line_number":22,"context_line":""},{"line_number":23,"context_line":"There used to be a sentence here saying, \"The Images API specification is"},{"line_number":24,"context_line":"developed alongside Glance, but is not considered part of the Glance project.\""},{"line_number":25,"context_line":"That\u0027s only partially true (or completely false, depending upon how strict you"},{"line_number":26,"context_line":"are about these things).  Conceptually, the OpenStack Images API is an"},{"line_number":27,"context_line":"independent definition of a REST API.  In practice, however, the only way"},{"line_number":28,"context_line":"further to develop the Images API is to work with the Glance community to"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_7d328c60","line":25,"range":{"start_line":25,"start_character":7,"end_line":25,"end_character":26},"updated":"2016-05-10 14:30:44.000000000","message":"I think this is assertive completely false because the cloud is legally bound to run the upstream implementation of the Images API implementation and that is Glance.","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"443efe5aeffce254fa5ea25d1122cc4165a4011b","unresolved":false,"context_lines":[{"line_number":22,"context_line":""},{"line_number":23,"context_line":"There used to be a sentence here saying, \"The Images API specification is"},{"line_number":24,"context_line":"developed alongside Glance, but is not considered part of the Glance project.\""},{"line_number":25,"context_line":"That\u0027s only partially true (or completely false, depending upon how strict you"},{"line_number":26,"context_line":"are about these things).  Conceptually, the OpenStack Images API is an"},{"line_number":27,"context_line":"independent definition of a REST API.  In practice, however, the only way"},{"line_number":28,"context_line":"further to develop the Images API is to work with the Glance community to"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_31978c3b","line":25,"range":{"start_line":25,"start_character":7,"end_line":25,"end_character":26},"in_reply_to":"dab17558_46a2549a","updated":"2016-05-10 15:33:53.000000000","message":"Sounds fair.\n\nThis is a definitely subjective discussion; though the legally bound case is true when some operator is trying to figure out if they have the compliance with the OpenStack standards.\n\nFrom your response, I conclude that -- an operator can have a different Images API (from OpenStack prescriptions without being legally liable) and its implementation, so not worry about licensing. The API evaluation seems to be relevant when you are worried about Interop (\u0026 thus branding).\n\nSo, the relaxation on \"how strict you are about things\" works for me.","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"8723b4a54ebcfb9fefa1d35e4d6c0cfa33975eed","unresolved":false,"context_lines":[{"line_number":22,"context_line":""},{"line_number":23,"context_line":"There used to be a sentence here saying, \"The Images API specification is"},{"line_number":24,"context_line":"developed alongside Glance, but is not considered part of the Glance project.\""},{"line_number":25,"context_line":"That\u0027s only partially true (or completely false, depending upon how strict you"},{"line_number":26,"context_line":"are about these things).  Conceptually, the OpenStack Images API is an"},{"line_number":27,"context_line":"independent definition of a REST API.  In practice, however, the only way"},{"line_number":28,"context_line":"further to develop the Images API is to work with the Glance community to"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_46a2549a","line":25,"range":{"start_line":25,"start_character":7,"end_line":25,"end_character":26},"in_reply_to":"dab17558_7d328c60","updated":"2016-05-10 15:19:54.000000000","message":"My point here is just that although the Images API is conceptually distinct from the Glance project, in practice, the Glance project is what determines what\u0027s in the Images API.  The conceptual independence give you the \"partially true\" aspect of the assertion.\n\nAs far as legally bound to run Glance ... only if you want to use the trademark.  The licensing allows you to run whatever you want at your installation.  The \"designated sections\" stuff is mentioned a few sentences down.\n\nSo I\u0027m inclined to leave this one as-is.","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"ccaf4d60f5f1bd98390661b8bc984a3bc5cc1440","unresolved":false,"context_lines":[{"line_number":25,"context_line":"That\u0027s only partially true (or completely false, depending upon how strict you"},{"line_number":26,"context_line":"are about these things).  Conceptually, the OpenStack Images API is an"},{"line_number":27,"context_line":"independent definition of a REST API.  In practice, however, the only way"},{"line_number":28,"context_line":"further to develop the Images API is to work with the Glance community to"},{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_5dfb4847","line":28,"range":{"start_line":28,"start_character":11,"end_line":28,"end_character":18},"updated":"2016-05-10 14:30:44.000000000","message":"develop or devolve say like the Artifacts implementation -- but I can be relaxed on this note.","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"443efe5aeffce254fa5ea25d1122cc4165a4011b","unresolved":false,"context_lines":[{"line_number":25,"context_line":"That\u0027s only partially true (or completely false, depending upon how strict you"},{"line_number":26,"context_line":"are about these things).  Conceptually, the OpenStack Images API is an"},{"line_number":27,"context_line":"independent definition of a REST API.  In practice, however, the only way"},{"line_number":28,"context_line":"further to develop the Images API is to work with the Glance community to"},{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_9172b80f","line":28,"range":{"start_line":28,"start_character":11,"end_line":28,"end_character":18},"in_reply_to":"dab17558_4653746b","updated":"2016-05-10 15:33:53.000000000","message":"+1","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"8723b4a54ebcfb9fefa1d35e4d6c0cfa33975eed","unresolved":false,"context_lines":[{"line_number":25,"context_line":"That\u0027s only partially true (or completely false, depending upon how strict you"},{"line_number":26,"context_line":"are about these things).  Conceptually, the OpenStack Images API is an"},{"line_number":27,"context_line":"independent definition of a REST API.  In practice, however, the only way"},{"line_number":28,"context_line":"further to develop the Images API is to work with the Glance community to"},{"line_number":29,"context_line":"define the new functionality and provide its reference implementation."},{"line_number":30,"context_line":"Further, Glance falls under the \"designated sections\" provision of the"},{"line_number":31,"context_line":"OpenStack DefCore Guidelines, which basically means that in order to qualify"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_4653746b","line":28,"range":{"start_line":28,"start_character":11,"end_line":28,"end_character":18},"in_reply_to":"dab17558_5dfb4847","updated":"2016-05-10 15:19:54.000000000","message":"Good point ... how about: \"the only way to participate in the evolution of the Images API ...\".  That makes it more clear that we\u0027re talking about change over time, without any prescription about whether this change consists of elaboration or simplification of the API.","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"ccaf4d60f5f1bd98390661b8bc984a3bc5cc1440","unresolved":false,"context_lines":[{"line_number":55,"context_line":"*************"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"The v1 API was originally designed as a service API for use by Nova and other"},{"line_number":58,"context_line":"OpenStack services.  Its current status is SUPPORTED.  The Images v1 API is"},{"line_number":59,"context_line":"closed to further development, and the Glance code implementing the v1 API"},{"line_number":60,"context_line":"accepts only serious bugfixes."},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_3d400334","line":58,"range":{"start_line":58,"start_character":21,"end_line":58,"end_character":39},"updated":"2016-05-10 14:30:44.000000000","message":"may be we should use dates here.","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"443efe5aeffce254fa5ea25d1122cc4165a4011b","unresolved":false,"context_lines":[{"line_number":55,"context_line":"*************"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"The v1 API was originally designed as a service API for use by Nova and other"},{"line_number":58,"context_line":"OpenStack services.  Its current status is SUPPORTED.  The Images v1 API is"},{"line_number":59,"context_line":"closed to further development, and the Glance code implementing the v1 API"},{"line_number":60,"context_line":"accepts only serious bugfixes."},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_5125f006","line":58,"range":{"start_line":58,"start_character":21,"end_line":58,"end_character":39},"in_reply_to":"dab17558_06b96c79","updated":"2016-05-10 15:33:53.000000000","message":"+1","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"8723b4a54ebcfb9fefa1d35e4d6c0cfa33975eed","unresolved":false,"context_lines":[{"line_number":55,"context_line":"*************"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"The v1 API was originally designed as a service API for use by Nova and other"},{"line_number":58,"context_line":"OpenStack services.  Its current status is SUPPORTED.  The Images v1 API is"},{"line_number":59,"context_line":"closed to further development, and the Glance code implementing the v1 API"},{"line_number":60,"context_line":"accepts only serious bugfixes."},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_06b96c79","line":58,"range":{"start_line":58,"start_character":21,"end_line":58,"end_character":39},"in_reply_to":"dab17558_3d400334","updated":"2016-05-10 15:19:54.000000000","message":"Good point.  How about \"Its current status as of the Liberty release is SUPPORTED.\"","commit_id":"96cece900bf8931ba4e83c00d503a95f912082fa"}]}