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
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 -
(not for usage questions)
openstack-dev@lists.openstack.org
Date: Monday, February 17, 2014 1:33 AM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Murano] Need a new DSL for Murano
Clint,
We're collaborating
@lists.openstack.org
Subject: Re: [openstack-dev] [Murano] Need a new DSL for Murano
Clint,
We're collaborating with Murano. We may need to do it in a way that others
could see it though. There are several things here:
* Murano doesn’t really have a “workflow engine” similar to Mistral’s.
People get
17, 2014 1:33 AM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Murano] Need a new DSL for Murano
Clint,
We're collaborating with Murano. We may need to do it in a way that
others could see it though
Clint,
We're collaborating with Murano. We may need to do it in a way that others
could see it though. There are several things here:
Murano doesn’t really have a “workflow engine” similar to Mistral’s. People get
confused with that but it’s just a legacy terminology, I think Murano folks
Hi Joshua,
Thank you very much for you feedback!
This is really a great question, and it was the first question we've asked
ourselves when we started thinking about this new design.
We've considered both options: to have our own syntax (python-like,
java-like, something-else-like) or to use YAML.
Just to add my 2 cents.
1. YAML is already familiar to OpenStack developers as Heat and others use
it. So at least the syntax (not to mess with semantics) doesn't have to be
learned.
2. YAML parser is very flexible an can be extended with additional types or
constructs like Key: filename.yaml to
Excerpts from Alexander Tivelkov's message of 2014-02-14 18:17:10 -0800:
Hi folks,
Murano matures, and we are getting more and more feedback from our early
adopters. The overall reception is very positive, but at the same time
there are some complaints as well. By now the most significant
Hi folks,
Murano matures, and we are getting more and more feedback from our early
adopters. The overall reception is very positive, but at the same time
there are some complaints as well. By now the most significant complaint is
is hard to write workflows for application deployment and
An honest question,
U are mentioning what appears to be the basis for a full programming language
(variables, calling other workflows - similar to functions) but then u mention
this is being stuffed into yaml.
Why?
It appears like u might as well spend the effort and define a grammar and
11 matches
Mail list logo
