Hello. [tl;dr] It is hard to read dependencies from the heat templates, for humans, without accessing Heat deployed your stacks live. So robots for the rescue!
Original topic [0]. Also there is related blog post [1]. The latter [2] expects your changes under test to be deployed live and queries Heat API, IIUC. While the former [3] can be used "offline" and helps to visualize dependency graph *very* fast, but didn't work for me as is (tried with tripleo heat templates Ocata). I reworked it a little bit [4] to fit my needs with t-h-t, which is I want to know which things is followed by which another things and so on, especially while those things is being changed all the time these days of containers and unicorns :) I hope this reworked tool can as well help other folks who wanted to know how tripleo heat templates deployment graph looks like and how to move things across that graph w/o troubles and w/o asking too many questions to Steven Hardy (like I did initially) haha. Kudos Alexis and Lars for great tools! [0] https://goo.gl/ajUMSi [1] http://blog.oddbit.com/2014/09/02/visualizing-heat-stacks/ [2] https://github.com/larsks/dotstack [3] https://github.com/lxsli/heat-viz [4] https://github.com/bogdando/heat-viz -- Best regards, Bogdan Dobrelya, Irc #bogdando __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
