<div dir="ltr">Hi,<div><br></div><div>I think BP is a right way to organize this. I will submit BP for metadata service from our side too.</div><div><br></div><div>Thanks</div><div>Georgy</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Dec 11, 2013 at 3:53 PM, Randall Burt <span dir="ltr"><<a href="mailto:randall.burt@rackspace.com" target="_blank">randall.burt@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Dec 11, 2013, at 5:44 PM, Georgy Okrokvertskhov <<a href="mailto:gokrokvertskhov@mirantis.com">gokrokvertskhov@mirantis.com</a>><br>
<div class="im"> wrote:<br>
<br>
> Hi,<br>
><br>
> To keep this thread alive I would like to share the small screencast I've recorded for Murano Metadata repository. I would like to share with you what we have in Murano and start a conversation about metadata repository development in OpenStack. Here is a link to screencast <a href="http://www.youtube.com/watch?v=Yi4gC4ZhvPg" target="_blank">http://www.youtube.com/watch?v=Yi4gC4ZhvPg</a> Here is a link to a detailed specification of PoC for metadata repository currently implemented in Murano.<br>
><br>
> There is an etherpad (here) for new MetadataRepository design we started to write after lesson learn phase of PoC. This is a future version of repository we want to have. This proposal can be used as an initial basis for metadata repository design conversation.<br>
><br>
> It will be great if we start conversation with Glance team to understand how this work can be organized. As it was revealed in this thread, the most probable candidate for metadata repository service implementation is Glance program.<br>
><br>
> Thanks,<br>
> Georgy<br>
<br>
</div>Thanks for the link and info. I think the general consensus is this belongs in Glance, however I think details are being deferred until the mid-summit meet up in Washington D.C. (I could be totally wrong about this). In any case, I think I'll also start converting the existing HeatR blueprints to Glance ones. Perhaps it would be a good idea at this point to propose specific blueprints and have further ML discussions focused on specific changes?<br>
<div class="HOEnZb"><div class="h5"><br>
> On Mon, Dec 9, 2013 at 3:24 AM, Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>> wrote:<br>
> Vishvananda Ishaya wrote:<br>
> > On Dec 6, 2013, at 10:07 AM, Georgy Okrokvertskhov<br>
> > <<a href="mailto:gokrokvertskhov@mirantis.com">gokrokvertskhov@mirantis.com</a> <mailto:<a href="mailto:gokrokvertskhov@mirantis.com">gokrokvertskhov@mirantis.com</a>>> wrote:<br>
> ><br>
> >> I am really inspired by this thread. Frankly saying, Glance for Murano<br>
> >> was a kind of sacred entity, as it is a service with a long history in<br>
> >> OpenStack. We even did not think in the direction of changing Glance.<br>
> >> Spending a night with these ideas, I am kind of having a dream about<br>
> >> unified catalog where the full range of different entities are<br>
> >> presented. Just imagine that we have everything as first class<br>
> >> citizens of catalog treated equally: single VM (image), Heat template<br>
> >> (fixed number of VMs\ autoscaling groups), Murano Application<br>
> >> (generated Heat templates), Solum assemblies<br>
> >><br>
> >> Projects like Solum will highly benefit from this catalog as it can<br>
> >> use all varieties of VM configurations talking with one service.<br>
> >> This catalog will be able not just list all possible deployable<br>
> >> entities but can be also a registry for already deployed<br>
> >> configurations. This is perfectly aligned with the goal for catalog to<br>
> >> be a kind of market place which provides billing information too.<br>
> >><br>
> >> OpenStack users also will benefit from this as they will have the<br>
> >> unified approach for manage deployments and deployable entities.<br>
> >><br>
> >> I doubt that it could be done by a single team. But if all teams join<br>
> >> this effort we can do this. From my perspective, this could be a part<br>
> >> of Glance program and it is not necessary to add a new program for<br>
> >> that. As it was mentioned earlier in this thread an idea of market<br>
> >> place for images in Glance was here for some time. I think we can<br>
> >> extend it to the idea of creating a marketplace for a deployable<br>
> >> entity regardless of the way of deployment. As Glance is a core<br>
> >> project which means it always exist in OpenStack deployment it makes<br>
> >> sense to as a central catalog for everything.<br>
> ><br>
> > +1<br>
><br>
> +1 too.<br>
><br>
> I don't think that Glance is collapsing under its current complexity<br>
> yet, so extending Glance to a general catalog service that can serve<br>
> more than just reference VM images makes sense IMHO.<br>
><br>
> --<br>
> Thierry Carrez (ttx)<br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Georgy Okrokvertskhov<br>
> Technical Program Manager,<br>
> Cloud and Infrastructure Services,<br>
> Mirantis<br>
> <a href="http://www.mirantis.com" target="_blank">http://www.mirantis.com</a><br>
> Tel. <a href="tel:%2B1%20650%20963%209828" value="+16509639828">+1 650 963 9828</a><br>
> Mob. <a href="tel:%2B1%20650%20996%203284" value="+16509963284">+1 650 996 3284</a><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Georgy Okrokvertskhov<br>
Technical Program Manager,<br>Cloud and Infrastructure Services,<br>
Mirantis<br>
<a href="http://www.mirantis.com/" target="_blank">http://www.mirantis.com</a><br>
Tel. +1 650 963 9828<br>
Mob. +1 650 996 3284<br>
</div>