Steve Baker 1733d74392 Set the name property for all deployment resources ... There are two reasons the name property should always be set for deployment resources: - The name often shows up in logs, files and API calls, the default derived name is long and unhelpful - Sorting by name determines the merge order of os-apply-config, and the execution order of puppet/shell scripts (note this is different to resource dependency order) so leaving the default name results in an undetermined order which could lead to unpredictable deployment of configs This change simply sets the name to the resource name, but a future change should prepend each name with a run-parts style 2 digit prefix so that the order is explicitly stated. Documentation for extraconfig needs to clearly state what prefix is needed to override which merge/execution order. For existing overcloud stacks, heat currently replaces deployment resources when the name changes, so this change Depends-On: I95037191915ccd32b2efb72203b146897a4edbc9 Change-Id: Ic4bcd56aa65b981275c3d4214588bfc4de63b3b0		2015-12-10 14:48:04 +13:00
..
firstboot	Merge "Add local docker registry support"	2015-11-20 17:28:48 +00:00
README-containers.md	Change the Atomic image name so it's less specific	2015-11-10 13:28:30 -05:00
compute-post.yaml	Set the name property for all deployment resources	2015-12-10 14:48:04 +13:00
copy-etc.sh	Docker compute role configured via Puppet	2015-10-08 07:34:26 -04:00
generate_json_config.sh	Update docker compute environment to use json config	2015-11-02 19:30:37 +00:00