For config-download we create a set of dummy DeployedServer
resources that has default software_config_transport property
(POLL_SERVER_CFN) which unnecessarily creates ec2 credentials
for these resources. We've dropped heat_cfn service from
undercloud, so change these to use POLL_SERVER_HEAT instead.
(cherry picked from commit 03aa8b10f6)
The new master branch should point now to rocky.
So, HOT templates should specify that they might contain features
for rocky release 
Also, this submission updates the yaml validation to use only latest
heat_version alias. There are cases in which we will need to set
the version for specific templates i.e. mixed versions, so there
is added a variable to assign specific templates to specific heat_version
aliases, avoiding the introductions of error by bulk replacing the
the old version in new releases.
As in FFU the SoftwareDeployment and StructuredDeployment
resources are being overwritten by the
config-download-software/structured resources, if the
name property is not defined when using one of these
resources a 'Property name not assigned' error will
Add support for the SshKnownHostsDeployment resources to
config-download. Since the deployment resources relied on Heat outputs,
they were not supported with the default handling from tripleo-common
that relies on the group_vars mechanism.
Instead, this patch refactors the templates to add the known hosts
entries as global_vars to deploy_steps_playbook.yaml, and then includes
the new tripleo-ssh-known-hosts role from tripleo-common to apply the
same configuration that the Heat deployment did.
Since these deployments no longer need to be triggered when including
config-download-environment.yaml, a mapping is added that can be
overridden to OS::Heat::None to disable the deployment resources when
The default behavior when not using config-download remains unchanged.
Presently, "openstack overcloud config download" does not support all
Deployment resources, only those included in the RoleData and are
natively of type group:ansible.
This patch adds support for also pulling all the deployment data for
OS::Heat::SoftwareDeployment (singular) resources applied to individual
servers of any group type. Those resources are mapped to a new nested
stack via the config-download-environment.yaml environment.
The nested stack has the same interface as a SoftwareDeployment but only
creates a OS::Heat::Value resource. The "config download" code will be
updated in a separate patch to read the deployment data from these Value
resources and apply them via ansible.
The related tripleo-common patch (which depends on this patch) is:
implements: blueprint ansible-config-download