tripleo-heat-templates

History

Florian Fuchs 44b1f51419 Create default deployment plan Currently no default plan is created during a container-based undercloud deployment. This patch creates a default deployment plan if both of two conditions apply: - The /usr/share/openstack-tripleo-heat-templates directory exists (We need the templates to create the plan) - There is no container named `overcloud` in swift yet (If a deployment is run more than once we don't want to recreate the default plan) Closes-Bug: #1798590 Change-Id: Id03631432b1fedd75ee3ddba67bfe7d5d6049a07		2018-10-29 10:24:43 +01:00
..
default.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
example_run_on_update.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
example.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
README	Wire in Controller pre-deployment extraconfig	2015-07-06 10:56:11 -04:00
standalone_post.sh	standalone run a post config to generate a clouds.yaml	2018-07-09 21:06:48 +00:00
standalone_post.yaml	Fix standalone home dir variable	2018-08-22 07:51:25 -06:00
undercloud_ctlplane_network.py	Use /usr/bin/env python to autodetect python	2018-05-24 10:22:39 +05:30
undercloud_post.sh	Create default deployment plan	2018-10-29 10:24:43 +01:00
undercloud_post.yaml	Fix enabled tripleo-validations check	2018-08-16 11:44:45 +02:00

This tree contains additional configuration which happens "post deployment",
e.g after the OpenStack service configuration has been completed.