<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Hey Pavlov,
<div><br>
</div>
<div>The main aim of this effort is to allow a more efficient template catalog management, not unlike what is given in [2]. As a service to our customers, Rackspace maintains a catalog of useful templates[3] which are also exposed to the user through the UI.
The template authors of these templates had expressed difficulties in having to maintain several templates depending on resource availability, account-type etc., so they asked for the ability to use Jinja templating system to instead include everything in
one Heat "meta-template" (Heat Template + Jinja, I’m not sure if that term is used for something else already :-) ). e.g. [4] shows a very simple case of having to choose between two templates depending upon the availability of Neutron on the network.</div>
<div><br>
</div>
<div>I hope that clarifies things a bit. Let me know if you have more questions!</div>
<div><br>
</div>
<div>Thanks!</div>
<div>-Pratik </div>
<div><br>
</div>
<div>[3] <a href="https://github.com/rackspace-orchestration-templates">https://github.com/rackspace-orchestration-templates</a> </div>
<div>[4] <a href="https://github.com/rackspace-orchestration-templates/jinja-test/blob/master/jinja-test.yaml">https://github.com/rackspace-orchestration-templates/jinja-test/blob/master/jinja-test.yaml</a><br>
<div>
<div>On Feb 2, 2015, at 1:44 PM, Pavlo Shchelokovskyy <<a href="mailto:pshchelokovskyy@mirantis.com">pshchelokovskyy@mirantis.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">
<div>Hi Pratik,<br>
<br>
</div>
what would be the aim for this templating? I ask since we in Heat try to keep the imperative logic like e.g. if-else out of heat templates, leaving it to other services. Plus there is already a spec for a heat template function to repeat pieces of template
structure [1].<br>
<div>
<div><br>
I can definitely say that some other OpenStack projects that are consumers of Heat will be interested - Trove already tries to use Jinja templates to create Heat templates [2], and possibly Sahara and Murano might be interested as well (I suspect though the
latter already uses YAQL for that).<br>
<br>
[1] <a href="https://review.openstack.org/#/c/140849/">https://review.openstack.org/#/c/140849/</a><br>
[2] <a href="https://github.com/openstack/trove/blob/master/trove/templates/default.heat.template">
https://github.com/openstack/trove/blob/master/trove/templates/default.heat.template</a><br>
<br>
</div>
<div>Best regards,<br>
</div>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature">
<div dir="ltr">Pavlo Shchelokovskyy
<div>Software Engineer</div>
<div>Mirantis Inc</div>
<div><a href="http://www.mirantis.com/" target="_blank">www.mirantis.com</a></div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Mon, Feb 2, 2015 at 8:29 PM, Pratik Mallya <span dir="ltr">
<<a href="mailto:pratik.mallya@rackspace.com" target="_blank">pratik.mallya@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Heat Developers,<br>
<br>
As part of an internal development project at Rackspace, I implemented a mechanism to allow using Jinja templating system in heat templates. I was hoping to give a talk on the same for the upcoming summit (which will be the first summit after I started working
on openstack). Have any of you worked/ are working on something similar? If so, could you please contact me and we can maybe propose a joint talk? :-)<br>
<br>
Please let me know! It’s been interesting work and I hope the community will be excited to see it.<br>
<br>
Thanks!<br>
-Pratik<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</body>
</html>