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
|
overcloud-upgrade
|
ffu_overcloud_upgrade: true
mixed_upgrade: true
|
n
|
n - 3 -> n
|
overcloud-upgrade
|
undercloud_upgrade: true
|
n -1 -> n
|
noop
|
undercloud-upgrade
|
overcloud_update: true
|
n -> n, previous-$hash -> $hash
|
update
|
overcloud-update
|
Upgrades job change injection points
This table show where and when a change in review is getting injected in the job
O UPGRADE currently really means "undercloud packages during overcloud upgrade" and ideally "undercloud packages and overcloud containers during overcloud upgrade"
In rocky+ releases it will probably mean "undercloud containers and overcloud containers during overcloud upgrade"
| Package type
|
Upgrade type
|
Upgrade direction
|
U INSTALL
|
U UPGRADE
|
O DEPLOY
|
O UPGRADE
|
| undercloud only (tht, python-tripleoclient)
|
mixed
|
n -1 -> n
|
|
not run
|
|
|
| undercloud only (tht, python-tripleoclient)
|
mixed
|
n -> n + 1
|
X
|
|
|
|
| undercloud only (tht, python-tripleoclient)
|
undercloud only
|
n -1 -> n
|
|
X
|
|
|
| undercloud only (tht, python-tripleoclient)
|
undercloud only
|
n -> n + 1
|
X
|
|
|
|
| undercloud only (tht, python-tripleoclient)
|
minor update
|
n -1 -> n
|
X
|
X
|
|
|
| undercloud only (tht, python-tripleoclient)
|
minor update
|
n -> n + 1
|
X
|
X
|
|
|
Specific releases upgraded at ci jobs
| Job Name |
Job Type |
Release |
Undercloud |
Overcloud |
environment |
voting
|
| gate-tripleo-ci-centos-7-containers-multinode-upgrades-pike-branch-nv |
multinode-1ctlr-featureset011 |
pike |
pike |
ocata -> pike |
rdo-cloud |
no
|
| gate-tripleo-ci-centos-7-containers-multinode-upgrades-pike-nv |
multinode-1ctlr-featureset011 |
pike |
pike |
ocata -> pike |
rdo-cloud |
no
|
| gate-tripleo-ci-centos-7-containers-multinode-upgrades-queens-nv |
multinode-1ctlr-featureset036 |
queens |
queens |
newton -> queens |
rdo-cloud |
no
|
| gate-tripleo-ci-centos-7-containers-to-container-upgrades-queens-nv |
multinode-1ctlr-featureset040 |
queens |
queens |
pike -> queens |
rdo-cloud |
no
|
| gate-tripleo-ci-centos-7-containers-to-container-upgrades-master |
multinode-1ctlr-featureset040 |
master |
master |
queens -> master |
rdo-cloud |
no
|
| gate-tripleo-ci-centos-7-containers-to-container-featureset051-upgrades-master |
multinode-1ctlr-featureset051 |
master |
master |
queens -> master |
rdo-cloud |
no
|
| tripleo-ci-centos-7-undercloud-upgrades |
singlenode-featureset047 |
ocata |
newton -> ocata |
noop |
rdo-cloud |
no
|
| tripleo-ci-centos-7-undercloud-upgrades |
singlenode-featureset047 |
pike |
ocata -> pike |
noop |
rdo-cloud, upstream |
no
|
| tripleo-ci-centos-7-undercloud-upgrades |
singlenode-featureset047 |
queens |
pike -> queens |
noop |
rdo-cloud, upstream |
no
|
| tripleo-ci-centos-7-undercloud-upgrades |
singlenode-featureset047 |
master |
queens -> master |
noop |
rdo-cloud, upstream |
no
|
| tripleo-ci-centos-7-containerized-undercloud-upgrades |
singlenode-featureset050 |
master |
queens->master |
noop |
upstream |
no
|
| tripleo-ci-centos-7-scenario000-multinode-oooq-container-updates |
multinode-1ctlr-featureset037 |
master |
master->master |
noop |
upstream |
yes
|
