Open Stack

I think this is a great feature to have it in Glance. Tagging mechanism for
objects which are not owned by Glance is complimentary to artifact
catalog\repository in Glance. As soon as we keep tags and artifacts
metadata close to each other the end-user will be able to use them
seamlessly.
Artifacts also can use tags to find objects outside of artifact repository
which is always good to have.
In Murano project we use Glance tags to find correct images which are
required by specific applications. It will be great to extend this to other
objects like networks, routers and flavors so that application write can
specify kind of object are required for his application.

Thanks,
Georgy


On Fri, May 30, 2014 at 11:45 AM, Zane Bitter <zbitter at redhat.com> wrote:

> On 29/05/14 18:42, Tripp, Travis S wrote:
>
>> Hello everyone!
>>
>> At the summit in Atlanta we demonstrated the “Graffiti” project
>> concepts.  We received very positive feedback from members of multiple
>> dev projects as well as numerous operators.  We were specifically asked
>> multiple times about getting the Graffiti metadata catalog concepts into
>> Glance so that we can start to officially support the ideas we
>> demonstrated in Horizon.
>>
>> After a number of additional meetings at the summit and working through
>> ideas the past week, we’ve created the initial proposal for adding a
>> Metadata Catalog to Glance for capabilities and tags.  This is distinct
>> from the “Artifact Catalog”, but we do see that capability and tag
>> catalog can be used with the artifact catalog.
>>
>> We’ve detailed our initial proposal in the following Google Doc.  Mark
>> Washenberger agreed that this was a good place to capture the initial
>> proposal and we can later move it over to the Glance spec repo which
>> will be integrated with Launchpad blueprints soon.
>>
>> https://docs.google.com/document/d/1cS2tJZrj748ZsttAabdHJDzkbU9nM
>> L5S4oFktFNNd68
>>
>> Please take a look and let’s discuss!
>>
>> Also, the following video is a brief recap of what was demo’ d at the
>> summit.  It should help to set a lot of understanding behind the ideas
>> in the proposal.
>>
>> https://www.youtube.com/watch?v=Dhrthnq1bnw
>>
>> Thank you!
>>
>> Travis Tripp (HP)
>>
>> Murali Sundar (Intel)
>>
>> *A Few Related Blueprints *
>>
>>
>> https://blueprints.launchpad.net/horizon/+spec/instance-
>> launch-using-capability-filtering
>>
>> https://blueprints.launchpad.net/horizon/+spec/tagging
>>
>> https://blueprints.launchpad.net/horizon/+spec/faceted-search
>>
>> https://blueprints.launchpad.net/horizon/+spec/host-
>> aggregate-update-metadata
>>
>> https://blueprints.launchpad.net/python-cinderclient/+spec/
>> support-volume-image-metadata
>>
>
> +1, this is something that will be increasingly important to
> orchestration. The folks working on the TOSCA (and others) -> HOT
> translator project might be able to comment in more detail, but basically
> as people start wanting to write templates that run on multiple clouds
> (potentially even non-OpenStack clouds) some sort of catalog for
> capabilities will become crucial.
>
> cheers,
> Zane.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Georgy Okrokvertskhov
Architect,
OpenStack Platform Products,
Mirantis
http://www.mirantis.com
Tel. +1 650 963 9828
Mob. +1 650 996 3284
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140530/b17d68ee/attachment.html>