On 24.04.2017 5:07, Steve Baker wrote: > Could you please try the "--format dot" formatter for the "openstack stack > resource list" command? It may meet your needs now, and I'm sure patches > would be welcome to the dot formatter to control what diagrams get > generated.
Thanks, I will try that once I'll be deploying a fully operational environment. The use case I described is primarily for *offline* graphs building to view before/after changes for patchsets or bugs like [0],[1],[2]. As offline I mean there is no cloud deployed, or only a semi-operational (under)cloud without Heat, like development bits deployed as a separate elements under test. Also note, that the given use case shortens code-to-live for dependency graphs from ~2h to an instant results (no need to wait for deployments). It can't process nested stacks though. A user should follow up on depicted FooConfig graph nodes. For example, the graph node NodeExtraConfigPost hides as: "environments/undercloud.yaml: OS::TripleO::NodeExtraConfigPost: ../extraconfig/post_deploy/undercloud_post.yaml" This makes things complicated to track offline, but still can be helpful for some cases w/o heavy usage of nested stacks. [0] https://review.openstack.org/#/c/448602 [1] https://review.openstack.org/#/c/456310/ [2] https://bugs.launchpad.net/tripleo/+bug/1677652 -- 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
