[openstack-dev] [Heat][Murano][TOSCA] Murano team contrib. to Heat TOSCA activities

Georgy Okrokvertskhov gokrokvertskhov at mirantis.com
Mon Mar 10 19:21:37 UTC 2014


Hi Randall,

I saw only the original XML based TOSCA 1.0 standard, I heard that there is
a new YAML based version but I did not see it.

The original TOSCA standard covered all aspects with TOSCA topology
templates (Heat templates) and TOSCA Plans (workflows). I hope they will
still use this approach. Mirantis is going to join OASIS and participate in
TOSCA standard development too.

As for Mistral, then it will have its own format for defining a tasks and
flows. Murano can perfectly coexists with Mistral as it provides an
application specific workflows. It is possible to define different actions
for Application like Application.backup and this action can be called by
Mistral to run a backup on schedule.


Thanks,
Georgy




On Mon, Mar 10, 2014 at 11:51 AM, Randall Burt
<randall.burt at rackspace.com>wrote:

>
> On Mar 10, 2014, at 1:26 PM, Georgy Okrokvertskhov <
> gokrokvertskhov at mirantis.com>
>  wrote:
>
> > Hi,
> >
> > Thomas and Zane initiated a good discussion about Murano DSL and TOSCA
> initiatives in Heat. I think will be beneficial for both teams to
> contribute into TOSCA.
>
> Wasn't TOSCA developing a "simplified" version in order to converge with
> HOT?
>
> > While Mirantis is working on organizational part for OASIS. I would like
> to understand what is the current view on the TOSCA and HOT relations.
> > It looks like TOSCA can cover all aspects of declarative components HOT
> templates and imperative workflows which can be covered by Murano. What do
> you think about that?
>
> Aren't workflows covered by Mistral? How would this be different than
> including mistral support in Heat?
>
> > I think TOSCA format can be used a a descriptions of Applications and
> heat-translator can actually convert TOSCA descriptions to both HOT and
> Murano files which can be then used for actual Application deployment. Both
> Het and Murano workflows can coexist in Orchestration program and cover
> both declarative templates and imperative workflows use cases.
> >
> > --
> > Georgy Okrokvertskhov
> > Architect,
> > OpenStack Platform Products,
> > 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
Architect,
OpenStack Platform Products,
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/20140310/71f3e080/attachment.html>


More information about the OpenStack-dev mailing list