It is possible to perform a stack validate after jinja2 processing.
There is already an action existing [1] do it and get the results. But
the results are not easy to consume, so it required to flatten the
heat resource tree and parameters. This has been done already in UI,
and i have added a patch for doing it in tripleo-common [2]. The
output of this flattening will look like [3][4].

I am not sure if this is what you are expecting.

Regards,
Saravanan KR

[1] 
https://github.com/openstack/tripleo-common/blob/master/tripleo_common/actions/parameters.py#L71
[2] https://review.openstack.org/#/c/450021/
[3] http://paste.openstack.org/show/600292/
[4] http://paste.openstack.org/show/600293/

On Tue, Mar 28, 2017 at 2:13 AM, Dan Sneddon <[email protected]> wrote:
> I've been trying to figure out a workflow for previewing the results of
> importing custom templates in an overcloud deployment (without actually
> deploying). For instance, I am overriding some parameters using custom
> templates, and I want to make sure those parameters will be expressed
> correctly when I deploy.
>
> I know about "heat stack-preview", but between the complexity of the
> overcloud stack and the jinja2 template processing, I can't figure out a
> way to preview the entire overcloud stack.
>
> Is this possible? If not, any hints on what would it take to write a
> script that would accomplish this?
>
> --
> Dan Sneddon         |  Senior Principal Software Engineer
> [email protected] |  redhat.com/openstack
> dsneddon:irc        |  @dxs:twitter
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to