Ben Nemec 93d2f4f56c Support deploying with multiple Heat environments ... Big changes here. This will make it easier to deploy some of the more advanced OVB options like network-isolation. Instead of users having to figure out which lines in the sample env.yaml to uncomment when deploying advanced options, they will simply be able to include one environment file that contains all the appropriate parameters to turn on the option. This _should_ be backwards compatible with existing monolithic env.yaml configurations. If it is not, that is a bug. To create the option environments, a slightly modified copy of the sample environment generator from tripleo-heat-templates has been copied into the project. The sample environments should _not_ be edited directly. Instead, the definition in the sample-env-generator directory should be altered and the tool re-run to update the environment.		2017-08-09 10:03:38 -05:00
..
tests	Support deploying with multiple Heat environments	2017-08-09 10:03:38 -05:00
__init__.py	Reorganize into package and add tox for testing	2016-07-14 12:23:41 -05:00
auth.py	Use more os-client-config to handle bmc auth	2017-07-20 15:39:44 -05:00
build_nodes_json.py	Support deploying with multiple Heat environments	2017-08-09 10:03:38 -05:00
deploy.py	Support deploying with multiple Heat environments	2017-08-09 10:03:38 -05:00
openstackbmc.py	Use more os-client-config to handle bmc auth	2017-07-20 15:39:44 -05:00