Open Stack

This is the current concept, but as far as I know the ability to create the
application marketplace (multiple services from multiple vendors) and
integration with Murano was discussed and pending Murano incubation
acceptance. The same concept can fit ServiceVM service - multiple VNFs from
multiple vendors.


On Mon, May 26, 2014 at 11:26 AM, Nikhil Manchanda <nikhil at manchanda.me>wrote:

>
> Isaku Yamahata writes:
>
> > [...]
> >> 2) Service Catalog - to accommodate multiple VNF services. Question: the
> >> same problem exists with Trove which need a catalog for multiple
> concrete
> >> DB implementations. Do you know which solution they will take for Juno?
> >
> > Regarding to Trove, I don't know.
> > Any Trove developer, can you comment on it?
> >
>
> Trove doesn't require multiple entries in the service catalog to support
> multiple datastore implementations. Trove internally has a concept of
> datastore type (e.g. mysql, redis, etc) and version; the same Trove
> service (at the same endpoint) is able to provision DB instances
> according to the type and version specified in the instance-create
> request.
>
> Additionally, operators also have the option of setting a default type /
> version so users don't need to explicitly specify this information as
> part of the create request.
>
> Thanks,
> Nikhil
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140526/fc6886a9/attachment.html>