Open Stack

Hi Dmitry,

I agree with you on this vision, however we have to think more on the
terminology: "Service Catalog" in OpenStack relates to Keystone (where by
"Service" we mean Openstack's infrastructure-level services).
I understand your concerns on "runtime lifecycle" vs "code-to-binary"
lifecycle though - it is absolutely valid, and we do not want to have any
overlap with Solum in this matter.

--
Regards,
Alexander Tivelkov


On Mon, Feb 24, 2014 at 1:47 PM, Dmitry <meytin at gmail.com> wrote:

> I think this is the great new service which will accompany OpenStack Solum
> similarly as Bosh is accompanying Cloud Foundry and CloudForms is
> accompanying OpenShift.
> I wouldn't call it the Application Catalog but the Service Catalog,
> because of the primary focus on the Service Life-cycle management (in
> opposite to application lifecycle management which is focused on
> "code-to-binary", execution, remote debugging and log grabbing etc).
> In order to make Murano the real Service Catalog, it should support (over
> DSL) run-time events processing such as service scaling (up/out/in/down),
> healing, replication, live-migration etc.
> In addition, it should support a "template" creation which could be used
> by Solum similar to Heroku BuildPack.
> I would happy to hear your opinion on how you envision the Murano's
> roadmap.
>
> Thanks,
> Dmitry
>
> _______________________________________________
> 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/20140224/69b7d8a4/attachment.html>