<font size=2 face="sans-serif">Hi Steve, sure. Please see my reply in-line.
<br>
</font>
<br><font size=2 face="sans-serif">Thanks! </font>
<br><font size=2 face="sans-serif"><br>
Regards, <br>
Sahdev</font><font size=1 face="sans-serif"><br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Steven Hardy <shardy@redhat.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"OpenStack Development
Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">09/09/2014 05:55 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
[Heat] Request for python-heatclient project to adopt heat-translator</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi Sahdev,<br>
<br>
On Tue, Sep 02, 2014 at 11:52:30AM -0400, Sahdev P Zala wrote:<br>
> Hello guys,<br>
> <br>
> As you know, the heat-translator project was started
early this year with<br>
> an aim to create a tool to translate non-Heat templates
to HOT. It is a<br>
> StackForge project licensed under Apache 2. We have made
good progress<br>
> with its development and a demo was given at the OpenStack
2014 Atlanta<br>
> summit during a half-a-day session that was dedicated
to heat-translator<br>
> project and related TOSCA discussion. Currently the development
and<br>
> testing is done with the TOSCA template format but the
tool is designed to<br>
> be generic enough to work with templates other than TOSCA.
There are five<br>
> developers actively contributing to the development.
In addition, all<br>
> current Heat core members are already core members of
the heat-translator<br>
> project.<br>
> <br>
> Recently, I attended Heat Mid Cycle Meet Up for Juno
in Raleigh and<br>
> updated the attendees on heat-translator project and
ongoing progress. I<br>
> also requested everyone for a formal adoption of the
project in the<br>
> python-heatclient and the consensus was that it is the
right thing to do.<br>
> Also when the project was started, the initial plan was
to make it<br>
> available in python-heatclient. Hereby, the heat-translator
team would<br>
> like to make a request to have the heat-translator project
to be adopted<br>
> by the python-heatclient/Heat program.<br>
<br>
Obviously I wasn't at the meetup, so I may be missing some context here,<br>
but can you answer some questions please?<br>
<br>
- Is the scope for heat-translator only tosca simple-profile, or also the<br>
original more heavyweight tosca too?</font></tt>
<br>
<br><tt><font size=2>Heat-translator is designed to be used to translate
any non-Heat templates to HOT. However, current development is done for
the TOSCA simple-profile only and there is no plan to use it for heavyweight
TOSCA.<br>
<br>
- If it's only tosca simple-profile, has any thought been given to moving<br>
towards implementing support via a template parser plugin, rather
than<br>
baking the translation into the client?</font></tt>
<br>
<br><tt><font size=2>At the meetup, Randall and Zane also mentioned that
we should dig into the plugin and see if that can also be used for TOSCA.
However, we all agreed that translation is still good to have and if plugin
can be used that will be another option for TOSCA users.<br>
<br>
While I see this effort as valuable, integrating the translator into the<br>
client seems the worst of all worlds to me:<br>
<br>
- Any users/services not intefacing to heat via python-heatclient can't
use it</font></tt>
<br>
<br><tt><font size=2>With python-heatclient, translator will just add a
command line option i.e. something like ‘heat-translator <format to
translate e.g. tosca> <noh-heat-template.yaml>' which will provide
an output as HOT. The user needs to take the translated template and run
it with Heat.<br>
<br>
- You prempt the decision about integration with any higher level services,<br>
e.g Mistral, Murano, Solum, if you bake in the translator at the<br>
heat level.</font></tt>
<br><tt><font size=2><br>
Hopefully that won't happen. The translator can be a simple integration
at the client level and provided just as a command line option without
any added complexity. </font></tt>
<br><tt><font size=2><br>
The scope question is probably key here - if you think the translator can<br>
do (or will be able to do) a 100% non-lossy conversion to HOT using only<br>
Heat, maybe it's time we considered discussing integration into Heat the<br>
service rather than the client.</font></tt>
<br>
<br><tt><font size=2> When the project was started, there was
a discussion with Steve Baker and others on IRC that initially it is a
good idea to provide the translator tool to users via python-heatclient
and eventually, as the tool gets more mature, we can discuss to make it
available in Heat engine to provide a seamless deployment of translated
template.<br>
<br>
Conversely, if you're going to need other services to fully implement the<br>
spec, it probably makes sense for the translator to remain layered over<br>
heat (or integrated with another project which is layered over heat).</font></tt>
<br>
<br><tt><font size=2> The translator project has no dependency on
other services and hoping for the same in future.<br>
</font></tt>
<br>
<br><tt><font size=2>I hope my answers make sense. Please let me know if
you have further questions.</font></tt>
<br>
<br><tt><font size=2><br>
Thanks!<br>
<br>
Steve<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
<br>
</font></tt>
<br>