On 16/09/14 02:49, Qiming Teng wrote:
Nice. What would be even nicer is a change to python-heatclient so that
heat resource-list has an option to output in dotfile format.
+1.
It would also be interesting to check if the dependency analysis is
capable of exploding a resource-group. Say I have
Nice work.
We discussed similar work weeks ago.
And the idea is to generate the dot file from a heat template, and then
draw figures from the dot file.
Even in the reversed direction, we can generate a heat template from a dot
based file.
Seems the community are eager to seem some heat template v
On Tue, Sep 16, 2014 at 03:34:28PM +1200, Steve Baker wrote:
> On 16/09/14 03:24, Alexis Lee wrote:
> > For your amusement,
> >
> > https://github.com/lxsli/heat-viz
> >
> > This produces HTML which shows which StructuredDeployments (boxes)
> > depends_on each other (bold arrows). It also shows
> Nice. What would be even nicer is a change to python-heatclient so that
> heat resource-list has an option to output in dotfile format.
+1.
It would also be interesting to check if the dependency analysis is
capable of exploding a resource-group. Say I have a ResourceGroup where
each resource
On 16/09/14 03:24, Alexis Lee wrote:
> For your amusement,
>
> https://github.com/lxsli/heat-viz
>
> This produces HTML which shows which StructuredDeployments (boxes)
> depends_on each other (bold arrows). It also shows the
> StructuredDeployments which StructuredConfigs (ovals) feed into (nor
For your amusement,
https://github.com/lxsli/heat-viz
This produces HTML which shows which StructuredDeployments (boxes)
depends_on each other (bold arrows). It also shows the
StructuredDeployments which StructuredConfigs (ovals) feed into (normal
arrows).
Both CFN + HOT format files should
