Tree:
885715855b
master
stable/train
stable/wallaby
0.0.1
0.1.0
0.1.1
0.2.0
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.5.6
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.7.7
0.7.8
0.7.9
0.8.0
0.8.1
0.8.10
0.8.11
0.8.12
0.8.13
0.8.14
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
0.8.8
0.8.9
1.0.0
10.0.0
10.1.0
10.2.0
10.3.0
10.4.0
10.5.0
10.6.0
10.6.1
10.6.2
11.0.0
11.1.0
11.2.0
11.3.0
11.3.1
11.4.0
11.5.0
11.6.0
12.0.0
12.1.0
12.2.0
12.3.0
12.4.0
12.4.1
12.4.2
12.4.3
12.4.4
12.4.5
12.4.6
12.5.0
12.6.0
12.7.0
13.0.0
13.1.0
13.2.0
13.3.0
13.4.0
13.5.0
13.6.0
14.0.0
14.1.0
14.1.1
14.1.2
14.2.0
14.3.0
15.0.0
15.1.0
16.0.0
2.0.0
2.1.0
2.2.0
5.0.0
5.0.0.0b1
5.0.0.0b2
5.0.0.0b3
5.0.0.0rc1
5.0.0.0rc2
5.0.0.0rc3
5.1.0
5.2.0
5.3.0
5.3.1
5.3.10
5.3.11
5.3.12
5.3.13
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
6.0.0
6.0.0.0b1
6.0.0.0b2
6.0.0.0rc1
6.0.0.0rc2
6.1.0
6.2.0
6.2.1
6.2.10
6.2.11
6.2.12
6.2.13
6.2.14
6.2.15
6.2.16
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8
6.2.9
7.0.0
7.0.0.0b1
7.0.0.0b2
7.0.0.0b3
7.0.0.0rc1
7.0.0.0rc2
7.0.1
7.0.10
7.0.11
7.0.12
7.0.13
7.0.14
7.0.15
7.0.16
7.0.17
7.0.18
7.0.2
7.0.3
7.0.4
7.0.5
7.0.6
7.0.7
7.0.8
7.0.9
8.0.0
8.0.0.0b1
8.0.0.0b2
8.0.0.0b3
8.0.0.0rc1
8.0.1
8.0.2
8.0.3
8.0.4
8.0.5
8.0.6
8.0.7
8.1.0
8.2.0
8.3.0
8.3.1
8.4.0
8.4.1
9.0.0
9.0.0.0b1
9.0.0.0b2
9.0.0.0b3
9.0.0.0b4
9.0.0.0rc1
9.0.0.0rc2
9.1.0
9.2.0
9.3.0
9.4.0
9.4.1
liberty-eol
mitaka-eol
newton-eol
ocata-em
ocata-eol
pike-em
pike-eol
queens-em
queens-eol
rocky-em
rocky-eol
stein-em
stein-eol
train-em
ussuri-em
ussuri-eol
victoria-em
victoria-eol
${ noResults }
5 Commits (885715855b19ec71ab362d92233478f3afb5a696)
Author | SHA1 | Message | Date |
---|---|---|---|
|
44ef2a3ec1 |
Change template names to rocky
The new master branch should point now to rocky. So, HOT templates should specify that they might contain features for rocky release [1] 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. [1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b |
4 years ago |
|
57c2c3d698 |
Add defaults into name property for config-download.
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 be displayed. Change-Id: Iade84cc85f61d73d4c3d53473cdc235f912187ad Closes-Bug: #1766908 |
4 years ago |
|
088d5c12f0 |
Support SshKnownHostsDeployment with config-download
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 using config-download. The default behavior when not using config-download remains unchanged. Closes-Bug: #1746336 Change-Id: Ia334fe6adc9a8ab228f75cb1d0c441c1344e2bd9 |
4 years ago |
|
927495fe3d |
Change template names to queens
The new master branch should point now to queens instead of pike. So, HOT templates should specify that they might contain features for queens release [1] [1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#queens Change-Id: I7654d1c59db0c4508a9d7045f452612d22493004 |
5 years ago |
|
a0e6d30ca2 |
Config download support for standalone deployments
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: I7d7f6b831b8566390d8f747fb6f45e879b0392ba implements: blueprint ansible-config-download Change-Id: Ic2af634403b1ab2924c383035f770453f39a2cd5 |
5 years ago |