Open Stack

Hi,

I think BP is a right way to organize this. I will submit BP for metadata
service from our side too.

Thanks
Georgy


On Wed, Dec 11, 2013 at 3:53 PM, Randall Burt <randall.burt at rackspace.com>wrote:

> On Dec 11, 2013, at 5:44 PM, Georgy Okrokvertskhov <
> gokrokvertskhov at mirantis.com>
>  wrote:
>
> > Hi,
> >
> > 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
> http://www.youtube.com/watch?v=Yi4gC4ZhvPg Here is a link  to a detailed
> specification of PoC for metadata repository currently implemented in
> Murano.
> >
> > 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.
> >
> > 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.
> >
> > Thanks,
> > Georgy
>
> 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?
>
> > On Mon, Dec 9, 2013 at 3:24 AM, Thierry Carrez <thierry at openstack.org>
> wrote:
> > Vishvananda Ishaya wrote:
> > > On Dec 6, 2013, at 10:07 AM, Georgy Okrokvertskhov
> > > <gokrokvertskhov at mirantis.com <mailto:gokrokvertskhov at mirantis.com>>
> wrote:
> > >
> > >> I am really inspired by this thread. Frankly saying, Glance for Murano
> > >> was a kind of sacred entity, as it is a service with a long history in
> > >> OpenStack.  We even did not think in the direction of changing Glance.
> > >> Spending a night with these ideas, I am kind of having a dream about
> > >> unified catalog where the full range of different entities are
> > >> presented. Just imagine that we have everything as  first class
> > >> citizens of catalog treated equally: single VM (image), Heat template
> > >> (fixed number of VMs\ autoscaling groups), Murano Application
> > >> (generated Heat templates), Solum assemblies
> > >>
> > >> Projects like Solum will highly benefit from this catalog as it can
> > >> use all varieties of VM configurations talking with one service.
> > >> This catalog will be able not just list all possible deployable
> > >> entities but can be also a registry for already deployed
> > >> configurations. This is perfectly aligned with the goal for catalog to
> > >> be a kind of market place which provides billing information too.
> > >>
> > >> OpenStack users also will benefit from this as they will have the
> > >> unified approach for manage deployments and deployable entities.
> > >>
> > >> I doubt that it could be done by a single team. But if all teams join
> > >> this effort we can do this. From my perspective, this could be a part
> > >> of Glance program and it is not necessary to add a new program for
> > >> that. As it was mentioned earlier in this thread an idea of market
> > >> place for images in Glance was here for some time. I think we can
> > >> extend it to the idea of creating a marketplace for a deployable
> > >> entity regardless of the way of deployment. As Glance is a core
> > >> project which means it always exist in OpenStack deployment it makes
> > >> sense to as a central catalog for everything.
> > >
> > > +1
> >
> > +1 too.
> >
> > I don't think that Glance is collapsing under its current complexity
> > yet, so extending Glance to a general catalog service that can serve
> > more than just reference VM images makes sense IMHO.
> >
> > --
> > Thierry Carrez (ttx)
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> > --
> > Georgy Okrokvertskhov
> > Technical Program Manager,
> > Cloud and Infrastructure Services,
> > Mirantis
> > http://www.mirantis.com
> > Tel. +1 650 963 9828
> > Mob. +1 650 996 3284
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Georgy Okrokvertskhov
Technical Program Manager,
Cloud and Infrastructure Services,
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/20131211/ffef329c/attachment.html>