Difference between revisions of "Tripleo-upgrades-fs-variables"
| Line 4: | Line 4: | ||
* The the "_step" variables are only used by the legacy role "overcloud-upgrade", and this is only used by the jjb tripleo-quickstart-upgrade-baremetal-builder | * The the "_step" variables are only used by the legacy role "overcloud-upgrade", and this is only used by the jjb tripleo-quickstart-upgrade-baremetal-builder | ||
* The containerized_overcloud_upgrade and containerized_undercloud_upgrade just state if we want to go to a containerized, but from a release point of view doesn't matter. | * The containerized_overcloud_upgrade and containerized_undercloud_upgrade just state if we want to go to a containerized, but from a release point of view doesn't matter. | ||
| + | * The role tags are selected at toci, and they control the flow of execution in the upgrades. | ||
=== Type of upgrades executed === | === Type of upgrades executed === | ||
Revision as of 06:58, 8 May 2018
Tripleo upgrades releases control variables
- They are used at tqe, tripleo-upgrade and toci
- The the "_step" variables are only used by the legacy role "overcloud-upgrade", and this is only used by the jjb tripleo-quickstart-upgrade-baremetal-builder
- The containerized_overcloud_upgrade and containerized_undercloud_upgrade just state if we want to go to a containerized, but from a release point of view doesn't matter.
- The role tags are selected at toci, and they control the flow of execution in the upgrades.
Type of upgrades executed
| Fs variable | Undercloud | Overcloud | Role tags |
|---|---|---|---|
overcloud_upgrade: true mixed_upgrade: true |
n | n - 1 -> n | TODO |
ffu_overcloud_upgrade: true mixed_upgrade: true |
n + 3 | n -> n + 3 | TODO |
undercloud_upgrade: true |
n -> n + 1 | noop | TODO |
