<div dir="ltr">><span style="font-family:Calibri,sans-serif;font-size:14.399999618530273px">My observation has been that Murano has changed from a Windows focused Deployment Service >to a Metadata Application Catalog Workflow thing (I fully admit this may be an invalid >observation). It's unclear to me what OpenStack pain/use-cases is to be solved by "complex >object composition, description of data types, contracts..." </span><div>
<span style="font-family:Calibri,sans-serif;font-size:14.399999618530273px"><br></span></div><div><span style="font-family:Calibri,sans-serif;font-size:14.399999618530273px">Murano is intended to provide high level definition of Applications which will include description of specific application requirements (like input parameters, external dependencies) as well as low level scripts, heat snippets and workflows which will be required to manage application.</span></div>
<div><span style="font-family:Calibri,sans-serif;font-size:14.399999618530273px"><br></span></div><div><span style="font-family:Calibri,sans-serif;font-size:14.399999618530273px">Object composition is required to address application diversity. We expect to be an integration layer for numerous different application from different OS and areas like WebServices, BigData, SAP, Enterprise specific apps. In order to decrease amount of work for Application author we will provide a way to reuse existing applications by extending them via object composition. Inside Murano we provide a library of workflows and requirements for general application classes. This library has workflows for instance creation, networking and app deployments. This will help application author to write only application specific stuff. For example if I need to publish my web service based on Tomcat I will create a new application class which has tomcat as a parent and then I will add my application specific parameters like App URL and will add deployment script which will download App war file and put it to Tomcat app directory. All other stuff will be done automatically by existing workflows for tomcat application.</span></div>
<div><br></div><div>You can imagine this as a nested Heat template inclusion but with ability to override and\or extend it. The ability to add a workflow actually looks like a dynamic Heat resource type generation as you can specify actions and associated workflows. These actions can be triggered by external events to provide an ability of application life cycle management.</div>
<div><br></div><div>Thanks</div><div>Georgy</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 17, 2014 at 4:41 PM, Keith Bray <span dir="ltr"><<a href="mailto:keith.bray@rackspace.com" target="_blank">keith.bray@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div><br>
</div>
<div>Can someone elaborate further on the things that Murano is intended to solve within the OpenStack ecosystem? My observation has been that Murano has changed from a Windows focused Deployment Service to a Metadata Application Catalog Workflow thing (I
fully admit this may be an invalid observation). It's unclear to me what OpenStack pain/use-cases is to be solved by "complex object composition, description of data types, contracts..." </div>
<div><br>
</div>
<div>Your thoughts would be much appreciated.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>-Keith</div>
<div><br>
</div>
<span>
<div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span>Renat Akhmerov <<a href="mailto:rakhmerov@mirantis.com" target="_blank">rakhmerov@mirantis.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, February 17, 2014 1:33 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Murano] Need a new DSL for Murano<br>
</div><div><div class="h5">
<div><br>
</div>
<div>
<div style="word-wrap:break-word">
<div style="margin:0px;font-size:13px;font-family:'Helvetica Neue'">Clint, </div>
<div style="margin:0px;font-size:13px;font-family:'Helvetica Neue'"><br>
</div>
<div style="margin:0px;font-size:13px;font-family:'Helvetica Neue'">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:</div>
<div style="margin:0px">
<ul>
<li><font face="Helvetica Neue">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 were going to rename this component to be more precise about
it.</font></li><li><font face="Helvetica Neue">Mistral DSL doesn’t seem to be a good option for solving tasks that Murano is intended to solve. Specifically I mean things like complex object composition, description of data types, contracts and so on. Like Alex and
Stan mentioned Murano DSL tends to grow into a full programming language</font><span style="font-family:'Helvetica Neue';font-size:small">.</span></li><li><span style="font-family:'Helvetica Neue';font-size:small">Most likely Mistral will be used in Murano for implementation, at least we see where it would be valuable. But Mistral is not so matured yet, we need to keep working hard and be patient :)</span></li>
</ul>
<div><br>
</div>
<div><span style="font-family:'Helvetica Neue';font-size:small">Anyway, we keep thinking on how to make both languages look similar or at least the possibility to use them seamlessly, if needed (call Mistral workflows from Murano DSL or vice versa).</span></div>
<div>
<div><br>
</div>
</div>
</div>
<div>
<div>Renat Akhmerov</div>
<div>@ Mirantis Inc.</div>
</div>
<br>
<div>
<div>On 16 Feb 2014, at 05:48, Clint Byrum <<a href="mailto:clint@fewbar.com" target="_blank">clint@fewbar.com</a>> wrote:</div>
<br>
<blockquote type="cite">Excerpts from Alexander Tivelkov's message of 2014-02-14 18:17:10 -0800:<br>
<blockquote type="cite">Hi folks,<br>
<br>
Murano matures, and we are getting more and more feedback from our early<br>
adopters. The overall reception is very positive, but at the same time<br>
there are some complaints as well. By now the most significant complaint is<br>
is hard to write workflows for application deployment and maintenance.<br>
<br>
Current version of workflow definition markup really have some design<br>
drawbacks which limit its potential adoption. They are caused by the fact<br>
that it was never intended for use for Application Catalog use-cases.<br>
<br>
</blockquote>
<br>
Just curious, is there any reason you're not collaborating on Mistral<br>
for this rather than both having a workflow engine?<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</blockquote>
</div>
<br>
</div>
</div>
</div></div></span>
</div>
<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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><font color="#999999"><span style="background-color:rgb(255,255,255)">Georgy Okrokvertskhov<br>
Architect,<br><span style="font-family:arial;font-size:small">OpenStack Platform Products,</span><br>
Mirantis</span><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</font><br></div>
</div>