Hey Pavlov,

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.

I hope that clarifies things a bit. Let me know if you have more questions!


[3] https://github.com/rackspace-orchestration-templates
On Feb 2, 2015, at 1:44 PM, Pavlo Shchelokovskyy 
<pshchelokovs...@mirantis.com<mailto:pshchelokovs...@mirantis.com>> wrote:

Hi Pratik,

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].

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).

[1] https://review.openstack.org/#/c/140849/

Best regards,

Pavlo Shchelokovskyy
Software Engineer
Mirantis Inc

On Mon, Feb 2, 2015 at 8:29 PM, Pratik Mallya 
<pratik.mal...@rackspace.com<mailto:pratik.mal...@rackspace.com>> wrote:
Hello Heat Developers,

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? :-)

Please let me know! It’s been interesting work and I hope the community will be 
excited to see it.


OpenStack Development Mailing List (not for usage questions)

OpenStack Development Mailing List (not for usage questions)

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to