)]}'
{"reference/programs.yaml":[{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"53a0271504dcecbdd8f6d52dac626734cab47310","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Image Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_9b009e35","line":26,"updated":"2014-06-05 08:46:38.000000000","message":"Should the program be renamed also to reflect the broadening of the scope out from pure images?\n\ne.g.\n\n  s/Image Service/Repository Service/\n\nor something generic of that ilk.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":455,"name":"Stuart McLaren","email":"stuart.mclaren@hpe.com","username":"stuart-mclaren"},"change_message_id":"4ad621270a4b5fb67e5a7e28dad439979644e4a9","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Image Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_f59b6e63","line":26,"in_reply_to":"1ae5cdf2_9b009e35","updated":"2014-06-05 10:02:00.000000000","message":"I think that\u0027s a good point.\n\nEg Heat templates aren\u0027t really images.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"79bcb2a9812613580fa7282466499a62cabe0275","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Image Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_7454b7c9","line":26,"in_reply_to":"1ae5cdf2_af950f34","updated":"2014-06-05 15:10:12.000000000","message":"I\u0027m not sure we wanna take on all the other changes necessary with changing a program name, or if it even completely falls under the technical branch of openstack to change program names (it might be more of a Board governance thing?) But just to float the proposition I will propose this change in the next patchset.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"55f6d257c12f371b2315b54c9c98dde7f5466324","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Image Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_af950f34","line":26,"in_reply_to":"1ae5cdf2_c49ec206","updated":"2014-06-05 13:43:46.000000000","message":"How about \"Artifact Repository Service\" ?","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":177,"name":"Alex Meade","email":"mr.alex.meade@gmail.com","username":"alex-meade"},"change_message_id":"fcbe71308142bbb8a9d47517134375dd62b2e278","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Image Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_c49ec206","line":26,"in_reply_to":"1ae5cdf2_f59b6e63","updated":"2014-06-05 13:07:01.000000000","message":"+1 I like \"repository service\"","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"55f6d257c12f371b2315b54c9c98dde7f5466324","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"},{"line_number":30,"context_line":"    different artifact types (entities, objects) in a unified manner."},{"line_number":31,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":32,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":33,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_cfe7bbaa","line":30,"updated":"2014-06-05 13:43:46.000000000","message":"I think the service itself manages actual artifacts, not artifact types.  Also, we seem to be assuming that everyone is familiar with how we\u0027re defining artifacts.  How about:\n\nmission:\nTo provide services to store, browse, share, distribute, and manage artifacts consumable by openstack services in a unified manner.   An artifact is a (data, description) association in which the description has a well-defined discoverable type and the data is immutable once the artifact is made available.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"7ebd03b50ef2175a84d7e4e797da361932cd6757","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"},{"line_number":30,"context_line":"    different artifact types (entities, objects) in a unified manner."},{"line_number":31,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":32,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":33,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_e22e5bfa","line":30,"updated":"2014-06-05 06:54:28.000000000","message":"We should probably just modify the previous patch with this change.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"79bcb2a9812613580fa7282466499a62cabe0275","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"},{"line_number":30,"context_line":"    different artifact types (entities, objects) in a unified manner."},{"line_number":31,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":32,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":33,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_f457e7c7","line":30,"in_reply_to":"1ae5cdf2_cfe7bbaa","updated":"2014-06-05 15:10:12.000000000","message":"Thanks, I\u0027ll use that.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"4a06dffc82a6ec888856560272d6d2a50bb8d878","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"},{"line_number":30,"context_line":"    different artifact types (entities, objects) in a unified manner."},{"line_number":31,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":32,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":33,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_c1086fdc","line":30,"in_reply_to":"1ae5cdf2_e22e5bfa","updated":"2014-06-05 14:48:16.000000000","message":"No, it\u0027s good to have it in two separate changes. We need the current mission defined before we discuss modifying it :) the first change should be a no-brainer, while the second one will trigger more discussion.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"79bcb2a9812613580fa7282466499a62cabe0275","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  mission:"},{"line_number":29,"context_line":"    To to provide services to store, browse, share, distribute and manage"},{"line_number":30,"context_line":"    different artifact types (entities, objects) in a unified manner."},{"line_number":31,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":32,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":33,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1ae5cdf2_14cd33b7","line":30,"in_reply_to":"1ae5cdf2_e22e5bfa","updated":"2014-06-05 15:10:12.000000000","message":"The argument for having two changes is that it we\u0027re doing two different things: 1) add a missing mission statement, 2) change the mission to reflect our new aspirations. That being said, I\u0027m fine with squashing the changes together if that is what most people want, so I guess we need a vote or something on this point.","commit_id":"6973b098b54314aabce3d57e0644afd4fb8ec458"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"21e8aafb1dbc5c52810177af2156b4b77fefd7cb","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_d2183bd5","line":26,"updated":"2014-06-05 16:00:44.000000000","message":"Just floating this out there because it is more accurate if we adopt the mission below. However, what are the other costs associated with changing a program name?","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"fc080281bc4c909433a335e4a29820cc5a313536","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_2d61eba8","line":26,"in_reply_to":"1ae5cdf2_0976ec05","updated":"2014-06-06 08:11:48.000000000","message":"\u0027Artifact Catalog\u0027 perhaps?\n\nIt depends on whether it\u0027s felt a catalog offers more functionality than a simple repository\n\nMost people would think of e.g. https://www.servicenow.com/products/it-service-automation-applications/service-catalog.html when talking about a catalog in this sort of context","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"748cc386b06aebdc6a6b0d581e048b6bf578121b","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_3e9f45b6","line":26,"in_reply_to":"1ae5cdf2_2d61eba8","updated":"2014-06-06 14:28:58.000000000","message":"The problem I see with shortening the name is: \"Artifact Repository\" captures the you-put-stuff-in-it aspect, but doesn\u0027t capture the cataloging aspect.  Likewise, \"Artifact Catalog\" doesn\u0027t necessarily include the you-put-stuff-in-it aspect.  To me, anyway, \"Artifact Repository Service\" implies you-put-stuff-in-it and you\u0027ve got services available to help you catalog, search, etc.\n\nMy opinion is that the goal of this project is that all openstack components should be able to use glance to get the artifacts they need without putting some middleware in front of glance that gives them better searching, etc., facilities.  I think that\u0027s captured by the \"Service\" aspect of \"Artifact Repository Service\".","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"8036827e4f36ca7ebb6df14c64a5180322fd1feb","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_b217dd53","line":26,"in_reply_to":"1ae5cdf2_3e9f45b6","updated":"2014-06-09 11:53:12.000000000","message":"Not sure how non-openstack-familiar folks read this but, at least for me, openstack released projects (the ones that are used to build a cloud) are always services. None of the existing projects mention it because it is implicit.\n\nIf the implicitness of those projects being services is an issue, then we should also rename other programs. I think \u0027Artifact Repository\u0027 would be enough.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"28a1048752a69c03352e79829e19300c158fe29c","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_0976ec05","line":26,"in_reply_to":"1ae5cdf2_867bcb79","updated":"2014-06-05 23:37:46.000000000","message":"Is \"Catalog\" an option? Or would the naming conflict with the keystone catalog?","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"2df8dbee09c803ad57218a4110eb46e4b641c435","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_2877c703","line":26,"in_reply_to":"1ae5cdf2_b217dd53","updated":"2014-06-09 23:09:28.000000000","message":"I thinks \"repository\" includes the concept of \"catalog\" in the ways that matter for us.\n\nAs I read this discussion, there is sufficient consensus for dropping \"Service\", which I see as a somewhat extraneous word which I initially included since we were formerly called the \"Image Service\".","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"a2addb8fcc5abd4491906c725d425514a0af2683","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_867bcb79","line":26,"in_reply_to":"1ae5cdf2_c1dce248","updated":"2014-06-05 22:18:07.000000000","message":"+1 to either \"Artifact Repository\" or \"Artifacts\".\n\nBoth are nicely pithy.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"5cc7fe1df9c49d3fe5e7544fcb2863c285e91a4b","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    - repo: openstack/swift-bench"},{"line_number":24,"context_line":"    - repo: openstack/swift-specs"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Artifact Repository Service:"},{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_c1dce248","line":26,"in_reply_to":"1ae5cdf2_d2183bd5","updated":"2014-06-05 20:02:48.000000000","message":"I\u0027d shorten to \"Artifact Repository\" since we don\u0027t have \"Service\" in most other program names.  It seems the last couple have it, but I personally prefer dropping it.\n\nYou could even shorten to \"Artifacts\".\n\nArtifacts seems extremely broad, but you\u0027ve defined what you mean by artifacts in the mission, so I think it\u0027s OK, as long as we can agree on the definition.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"28a1048752a69c03352e79829e19300c158fe29c","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  mission:"},{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_69669052","line":32,"updated":"2014-06-05 23:37:46.000000000","message":"s/document/documents/","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"2df8dbee09c803ad57218a4110eb46e4b641c435","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  mission:"},{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_5c185475","line":32,"in_reply_to":"1ae5cdf2_69669052","updated":"2014-06-09 23:09:28.000000000","message":"It actually was meant to be document, following parallelism as \"document data\" and \"bulk, unstructured data\". But that parallelism is awkards, so I\u0027m changing it. There is not in my mind a clear distinction between \"document data\" and \"documents\" and the latter is less awkward.\n\nThanks!","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"28a1048752a69c03352e79829e19300c158fe29c","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_c9dde4e1","line":33,"updated":"2014-06-05 23:37:46.000000000","message":"\"immutable\" + \"versioned\" is an odd juxtaposition. Maybe we could just refer to \"persistent versioning\" or something like that?","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"a2addb8fcc5abd4491906c725d425514a0af2683","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_26b83710","line":33,"updated":"2014-06-05 22:18:07.000000000","message":"I\u0027m not loving \"unstructured\" in this context.\n\nSure, glance treats these artifacts as opaque blobs.\n\nBut these blobs may, and do, have their own internal structure, right?\n\nBut I do like the emphasis on type, immutability and versioning.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"8036827e4f36ca7ebb6df14c64a5180322fd1feb","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_b2943de9","line":33,"in_reply_to":"1ae5cdf2_3ef2e56f","updated":"2014-06-09 11:53:12.000000000","message":"In my experience, tagging data as \"unstructured\" brings more problems than it solves. One of them is exactly thinking that since the data is unstructured from Glance\u0027s POV the structure doesn\u0027t really matters. I don\u0027t think mentioning `unstructured` here buys us anything.\n\nThat said, I agree with mentioning immutability which is in fact a non opt-in/opt-out property of the artifacts.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"2df8dbee09c803ad57218a4110eb46e4b641c435","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_fc3920d9","line":33,"in_reply_to":"1ae5cdf2_b2943de9","updated":"2014-06-09 23:09:28.000000000","message":"I agree that immutable and versioned feel oddly put together in this sentence. I\u0027m not entirely sure how to fix it. For the next revision, I\u0027ll focus on the fact that a given version of the artifact is immutable.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"748cc386b06aebdc6a6b0d581e048b6bf578121b","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_8180fe47","line":33,"in_reply_to":"1ae5cdf2_c2e4d10e","updated":"2014-06-06 14:28:58.000000000","message":"Well, the data is \"unstructured\" from the Glance point of view.  I think the reason to call it \"unstructured\" here is to underscore that Glance doesn\u0027t care what the data is, Glance\u0027s primary concern is the document describing the data.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"52c9ec988ec3bb9b0d4ba615e845acdb0801a9dd","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_c2e4d10e","line":33,"in_reply_to":"1ae5cdf2_c9dde4e1","updated":"2014-06-06 10:09:23.000000000","message":"Agreed w.r.t \"unstructured\" not looking good in this context.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"748cc386b06aebdc6a6b0d581e048b6bf578121b","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_3ef2e56f","line":33,"in_reply_to":"1ae5cdf2_c9dde4e1","updated":"2014-06-06 14:28:58.000000000","message":"The idea is that artifacts are immutable with versioning as a convenience.  Glance will guarantee that when you ask for v3.1.23 of an artifact, you always get the same bits (or nothing). If you have to update that artifact for some reason, you have no choice but to get a new version on it.  Right now with images, there\u0027s no versioning unless you do it yourself by adding a custom image property.  The immutability-once-published is a key aspect of Glance, so I\u0027d definitely like to see \"immutable\" in the statement.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"21e8aafb1dbc5c52810177af2156b4b77fefd7cb","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_721f67b7","line":34,"updated":"2014-06-05 16:00:44.000000000","message":"I really felt like we needed to offer some definition of an artifact. Let\u0027s try this one on for size.","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"fc080281bc4c909433a335e4a29820cc5a313536","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_ad225b4f","line":34,"in_reply_to":"1ae5cdf2_017faa15","updated":"2014-06-06 08:11:48.000000000","message":"Perhaps the emphasis here should be on browsability?\n\ni.e. it\u0027s only a repository/catalog for the types of artifacts that users will want to browse and select?","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"5cc7fe1df9c49d3fe5e7544fcb2863c285e91a4b","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_017faa15","line":34,"in_reply_to":"1ae5cdf2_721f67b7","updated":"2014-06-05 20:02:48.000000000","message":"I completely agree that a definition is needed.  It\u0027s still pretty broad, but I\u0027m not sure how to tighten it up.  As defined, it sounds like keys could be artifacts, even though we have a separate program for that.  Perhaps that\u0027s fine, and there will just be some cases that warrant special handling elsewhere (like keys).","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":7665,"name":"Travis Tripp","email":"os.travis.tripp@gmail.com","username":"travis.tripp"},"change_message_id":"40fa0ceb65108b7283a04a7be8cc0ebf86c54222","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_907d98ea","line":34,"in_reply_to":"1ae5cdf2_ad225b4f","updated":"2014-06-07 00:21:15.000000000","message":"As Zane mentioned in his general comments (non-inline), this definition doesn\u0027t seem to include the metadata schema catalog that was discussed at the Juno design summit and for which we\u0027ve now submitted a spec [1].\n\nPerhaps a change to the first sentence: \n\nTo provide services to store, browse, share, distribute, and manage artifacts and metadata schemas consumable by OpenStack services and users in a unified manner.\n\nThis doesn\u0027t affect the definition of artifacts, but if needed, \"metadata schemas\" could be further qualified based on the text in the spec referenced below.\n\n[1] https://review.openstack.org/#/c/98554/","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"2df8dbee09c803ad57218a4110eb46e4b641c435","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An artifact"},{"line_number":32,"context_line":"    is any strongly-typed, versioned collection of document and bulk,"},{"line_number":33,"context_line":"    unstructured data and is immutable once the artifact is published in the"},{"line_number":34,"context_line":"    repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1ae5cdf2_dc5aa429","line":34,"in_reply_to":"1ae5cdf2_ad225b4f","updated":"2014-06-09 23:09:28.000000000","message":"Mark McLoughlin:\nI think that\u0027s a great idea, but I can\u0027t quite figure out how to phrase it. Have a look at the next revision if you have any suggestions.\n\nThanks!\n\nTravis Tripp:\nI think this language does not include but does not preclude the metadata schemas you have discussed. I think they fall under the general heading of making the glance artifacts user-metadata and tags easier to use. The fact that the metadata catalog (for lack of a better word) also benefits other openstack resources is in my view, just gravy.\n\nI\u0027m eager to hear counters to this position.\n\nThanks!","commit_id":"d2d4c3672db494894b7f463eee520d3ce528d6db"},{"author":{"_account_id":2889,"name":"Aeva Black","email":"aeva.online@gmail.com","username":"tenbrae"},"change_message_id":"6d6648da857a342bbcbe3f3ee55571bd465a2132","unresolved":false,"context_lines":[{"line_number":27,"context_line":"  codename: Glance"},{"line_number":28,"context_line":"  ptl: Mark Washenberger (markwash)"},{"line_number":29,"context_line":"  mission:"},{"line_number":30,"context_line":"    To provide services to store, browse, share, distribute, and manage"},{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_fdfe516a","line":30,"updated":"2014-06-17 21:03:43.000000000","message":"Here\u0027s another attempt at a much more general wording:\n\n  To provide a service which brokers access to versioned data objects\n  and associated metadata. In the absence of an appropriately\n  configured storage back-end, the service will store the object(s) itself.","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"0f2c267e3dc6a71c02f55c89c2a3a093df2b458c","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_ef985b1d","line":34,"updated":"2014-06-10 19:54:45.000000000","message":"Are we getting too much into implementation here? I understand the need to describe what we mean by artifact, but in the other mission statements we have tried to avoid locking in details that make it difficult for the program to adjust implementation.\n\nIs a single artifact a collection of documents? Does it matter to the mission how you are organizing what goes into an artifact?\n\nDoes glance see some artifacts as documents and some as BLOBs? Does that distinction matter to the mission, or is it an implementation detail?\n\nI think we can leave out the stuff about versioning entirely. That\u0027s relevant as a feature, but it doesn\u0027t need to be part of the mission. Ditto immutability -- you don\u0027t want to have to come back to the TC for permission to make BLOBs mutable if you decide you need that as a feature later.\n\nStripping all of that out and building on Mark\u0027s suggestion to focus on the browsing, I get:\n\n  To provide user-facing services to store, browse, share, distribute,\n  and manage BLOBs.\n\nIf \"browse\" means that there is a search API, maybe:\n\n  To provide user-facing services to store and manage BLOBs\n  so they are discoverable by their application-specific meta-data.","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"53af0b5c6e48a53d221f62048dec20d4d7ce31c4","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_05ae9f2f","line":34,"in_reply_to":"1ae5cdf2_42bfc2aa","updated":"2014-06-16 14:45:56.000000000","message":"The program mission describes the goal of the *team*. I understand that immutability is an important feature for some (all?) of the artifact types identified so far. That is still an implementation detail of the software, rather than the team building the software. We would not create a separate program, with a separate set of developers, to build a service just like glance for mutable artifacts.","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"64f6d0d2d51ff48dd14b3a11ef71f6fc7a1b0c66","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_32d82df0","line":34,"in_reply_to":"1ae5cdf2_4955a6f8","updated":"2014-06-24 06:24:19.000000000","message":"After having some second thoughts about the nature of the immutabilty requirement in Glance, I really like these suggestions. I think data asset is a great term, because it actually kind of implies the immutability we care the most about. The key feature of a data asset is the data itself, not what it models, in a sense. (One would not view a nova server/instance as a \"data asset\", as I understand it.)\n\nThe first take is technical enough that I might still throw in \"immutable\" to modify \"data asset\", but I think the second approach is sufficiently vernacular to leave immutability implied.","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"3303b0be9ee85d7e192289f7f9bb2cb371000450","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_e9ebd2d9","line":34,"in_reply_to":"1ae5cdf2_4955a6f8","updated":"2014-06-11 16:24:50.000000000","message":"`data assets` I like that. I like the first description more because it keeps the mission generic but still precise.","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"3e2e32eaa60659fce3906b0d425ce4844fcb5606","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_9de2ad2d","line":34,"in_reply_to":"1ae5cdf2_5d63c5dc","updated":"2014-06-10 20:08:48.000000000","message":"From The Jargon File (version 4.4.7, 29 Dec 2003) [jargon]:\n\n  BLOB\n  \n  \n      1. n. [acronym: Binary Large OBject] Used by database people to refer to\n      any random large block of bits that needs to be stored in a database, such\n      as a picture or sound file. The essential point about a BLOB is that it\u0027s\n      an object that cannot be interpreted within the database itself.\n  \n      2. v. To {mailbomb} someone by sending a BLOB to him/her; esp. used as a\n      mild threat. ?If that program crashes again, I\u0027m going to BLOB the core\n      dump to you.?","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"e0f3f1a4dbf8d11a53001ee6190435d928d55a1a","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_4955a6f8","line":34,"in_reply_to":"1ae5cdf2_884b36b0","updated":"2014-06-11 16:18:52.000000000","message":"Here\u0027s another take:\n\n To provide a service to store, browse, share, distribute, and manage\n data assets with internal structure and metadata defined by other \n services.\n\nand more \"folksy\":\n\n To provide a service where users can upload and discover data assets\n that are meant to be used with other services, like images for Nova\n and templates for Heat.","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"5b7865b941d0acea3b89d49669f8b84c66dafb3d","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_884b36b0","line":34,"in_reply_to":"1ae5cdf2_9de2ad2d","updated":"2014-06-11 11:17:44.000000000","message":"We should take the implementation details out of the mission, agreed. However, I don\u0027t like the sound of BLOB in this context. I\u0027d like the mission to specify the type of data glance will hold. That data used to be \"Images\" and it\u0027s now becoming \"artifacts\". Some questions:\n\nDo we really need to explain what an artifact is in the mission? Can we explain what an artifact is in Glance\u0027s documentation?\n\nCan an artifact be described as a \"cloud infrastructure resource/ item/ template\" ?","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"407be1be8d9db133fee96f60c8a23dc98f32a04c","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_42bfc2aa","line":34,"in_reply_to":"1ae5cdf2_e9ebd2d9","updated":"2014-06-16 12:40:34.000000000","message":"About immutability ...\n\nImmutability is a key feature of images, i.e., once the data has been uploaded and the image goes active, Glance will not allow you to modify the data (the \"opaque blobs).  This is extremely important so that people booting VM images know exactly what they\u0027re getting.  (Old image data can be deleted or replaced, but it cannot be updated.  This prevents bad surprises on the part of image consumers.)\n\nThe glance artifacts working group also identified immutability as a key feature: artifacts, once published, cannot be modified.  So actually, I think we *do* want to be forced to go before the TC before immutability can be removed as a requirement for artifacts (including images) that are stored in Glance--it\u0027s that important.\n\nAbout versioning ...\n\nSince the actual artifacts (i.e., the data) are immutable, that raises the question of \"how can I update immutable objects\"?  Since an update to image data requires publication of a completely new Glance object with a different UUID from the prior version, it would be good to have a way to express the relation between the two Glance objects.  Up to now, you had to do this informally by making up your own versioning scheme and using custom image properties.  Versioning is important enough (given immutability) that our current thinking is that a flexible versioning scheme should be provided by Glance itself instead of forcing users to implement it themselves.\n\nThat being said, I can take or leave mentioning versioning in the mission statement, but immutability must be stated explicitly.","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"bf367d5450ebd8892c54f6b3e019ce5854e5b386","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    artifacts consumable by OpenStack services in a unified manner. An"},{"line_number":32,"context_line":"    artifact is a strongly-typed, versioned collection of documents and opaque"},{"line_number":33,"context_line":"    blobs of data and a given version of an artifact is immutable once it is"},{"line_number":34,"context_line":"    published in the repository."},{"line_number":35,"context_line":"  url: https://wiki.openstack.org/wiki/Glance"},{"line_number":36,"context_line":"  projects:"},{"line_number":37,"context_line":"    - repo: openstack/glance"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ae5cdf2_5d63c5dc","line":34,"in_reply_to":"1ae5cdf2_ef985b1d","updated":"2014-06-10 20:07:12.000000000","message":"Liking where you\u0027re going with this\n\n(except \u0027blob\u0027 isn\u0027t an acronym ... is it?)","commit_id":"46570aa603792f20d8ad247edda3727da68e04f1"}]}