<div dir="ltr">Thomas, It is great that 'heat-translator' project would have a session at the Atlanta Summit! We are definitely interested in TOSCA and how it is translated to the HOT.</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, May 5, 2014 at 9:21 PM, Thomas Spatzier <span dir="ltr"><<a href="mailto:thomas.spatzier@de.ibm.com" target="_blank">thomas.spatzier@de.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi all,<br>
<br>
I mentioned in some earlier mail that we have started to implement a TOSCA<br>
YAML to HOT translator on stackforge as project "heat-translator". We have<br>
been lucky to get a session allocated in the context of the "Open source @<br>
OpenStack" program for the Atlanta summit, so I wanted to share this with<br>
the Heat community to hopefully attract some interested people. Here is the<br>
session link:<br>
<br>
<a href="http://openstacksummitmay2014atlanta.sched.org/event/c94698b4ea2287eccff8fb743a358d8c#.U2e-zl6cuVg" target="_blank">http://openstacksummitmay2014atlanta.sched.org/event/c94698b4ea2287eccff8fb743a358d8c#.U2e-zl6cuVg</a><br>
<br>
While there is some focus on TOSCA, the goal of discussions would also be<br>
to find a reasonable design for sitting such a translation layer on-top of<br>
Heat, but also identify the relations and benefits for other projects, e.g.<br>
how Murano use cases that include workflows for templates (which is part of<br>
TOSCA) could be addressed long term. So we hope to see a lot of interested<br>
folks there!<br>
<br>
Regards,<br>
Thomas<br>
<br>
PS: Here is a more detailed description of the session that we submitted:<br>
<br>
1) Project Name:<br>
heat-translator<br>
<br>
2) Describe your project, including links to relevent sites, repositories,<br>
bug trackers and documentation:<br>
We have recently started a stackforge project [1] with the goal to enable<br>
the deployment of templates defined in standard format such as OASIS TOSCA<br>
on top of OpenStack Heat. The Heat community has been implementing a native<br>
template format 'HOT' (Heat Orchestration Templates) during the Havana and<br>
Icehouse cycles, but it is recognized that support for other standard<br>
formats that are sufficiently aligned with HOT are also desirable to be<br>
supported.<br>
Therefore, the goal of the heat-translator project is to enable such<br>
support by translating such formats into Heat's native format and thereby<br>
enable a deployment on Heat. Current focus is on OASIS TOSCA. In fact, the<br>
OASIS TOSCA TC is currently working on a TOSCA Simple Profile in YAML [2]<br>
which has been greatly inspired by discussions with the Heat team, to help<br>
getting TOSCA adoption in the community. The TOSCA TC and the Heat team<br>
have also be in close discussion to keep HOT and TOSCA YAML aligned. Thus,<br>
the first goal of heat-translator will be to enable deployment of TOSCA<br>
YAML templates thru Heat.<br>
Development had been started in a separate public github repository [3]<br>
earlier this year, but we are currently in the process of moving all code<br>
to the stackforge projects<br>
<br>
[1] <a href="https://github.com/stackforge/heat-translator" target="_blank">https://github.com/stackforge/heat-translator</a><br>
[2]<br>
<a href="https://www.oasis-open.org/committees/document.php?document_id=52571&wg_abbrev=tosca" target="_blank">https://www.oasis-open.org/committees/document.php?document_id=52571&wg_abbrev=tosca</a><br>
[3] <a href="https://github.com/spzala/heat-translator" target="_blank">https://github.com/spzala/heat-translator</a><br>
<br>
3) Please describe how your project relates to OpenStack:<br>
Heat has been working on a native template format HOT to replace the<br>
original CloudFormation format as the primary template of the core Heat<br>
engine. CloudFormation shall continue to be supported as one possible<br>
format (to protect existing content), but it is desired to move such<br>
support out of the core engine into a translation layer. This is one<br>
architectural move that can be supported by the heat-translator project.<br>
Furthermore, there is desire to enable standardized formats such OASIS<br>
TOSCA to run on Heat, which will also be possible thru heat-translator.<br>
<br>
In addition, recent discussions [4] in the large OpenStack orchestration<br>
community have shown that several groups (e.g. Murano) are looking at<br>
extending orchestration capabilities beyond Heat functionality, and in the<br>
course of doing this also extend current template formats. It has been<br>
suggested in mailing list posts that TOSCA could be one potential format to<br>
center such discussions around instead of several groups developing their<br>
own orchestration DSLs. The next version of TOSCA with its simple profile<br>
in YAML is very open for input from the community, so there is a great<br>
opportunity to shape the standard in a way to address use cases brought up<br>
by the community. Willingness to join discussions with the TOSCA TC have<br>
already been indicated by several companies contributing to OpenStack.<br>
Therefore we think the heat-translator project can help to focus such<br>
discussions.<br>
<br>
[4]<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2014-March/028957.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-March/028957.html</a><br>
<br>
4) How do you plan to use the time and space?<br>
Give attendees an overview of current developments of the TOSCA Simple<br>
Profile in YAML and how we are aligning this with HOT.<br>
Give a quick summary of current code.<br>
Discuss next steps and long term direction of the heat-translator project:<br>
alignment with Heat, parts that could move into Heat, parts that would stay<br>
outside of Heat etc.<br>
Collect use cases from other interested groups (e.g. Murano), and discuss<br>
that as potential input for the project and also ongoing TOSCA standards<br>
work.<br>
Discuss if and how this project could help to address requirements of<br>
different groups.<br>
Discuss and agree on a design to (1) meet important requirements based on<br>
those discussions, and (2) to best enable collaborative development with<br>
the community.<br>
<br>
<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>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Serg Melikyan, Senior Software Engineer at Mirantis, Inc.<br></div><div><a href="http://mirantis.com/" target="_blank">http://mirantis.com</a> | <a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a><br>
<div><br>+7 (495) 640-4904, 0261</div><div>+7 (903) 156-0836</div></div></div>
</div>