Difference between revisions of "Tripleo-upgrades-fs-variables"
(Created page with "This is the table with the mapping from the ansible role "tripleo-upgrades" variables to the type of upgrade executed. mixed_upgrade is u n is the value of the variable "rel...") |
(→Upgrades job change injection points) |
||
(39 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | + | == 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 === | |
− | |||
− | |||
− | |||
− | |||
− | |||
{| class="wikitable" | {| class="wikitable" | ||
Line 14: | Line 12: | ||
! Fs variable | ! Fs variable | ||
! Undercloud | ! Undercloud | ||
− | ! Overcloud | + | ! Overcloud |
+ | ! Role tags | ||
|- | |- | ||
− | | overcloud_upgrade | + | | |
+ | overcloud_upgrade: true | ||
+ | mixed_upgrade: true | ||
| n | | n | ||
| n - 1 -> 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" | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |||
+ | ! Package type | ||
+ | ! Upgrade type | ||
+ | ! Upgrade direction | ||
+ | ! U INSTALL | ||
+ | ! U UPGRADE | ||
+ | ! O DEPLOY | ||
+ | ! O UPGRADE | ||
|- | |- | ||
− | | | + | | undercloud only (tht, python-tripleoclient) |
− | | n | + | | mixed |
− | | n - 1 > n | + | | n -1 -> n |
+ | | X | ||
+ | | not run | ||
+ | | irrelevant | ||
+ | | irrelevant | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | mixed | ||
+ | | n -> n + 1 | ||
+ | | not possible | ||
+ | | not possible | ||
+ | | not possible | ||
+ | | not possible | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | undercloud only | ||
+ | | n -1 -> n | ||
+ | | | ||
+ | | X | ||
+ | | not run | ||
+ | | not run | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | undercloud only | ||
+ | | n -> n + 1 | ||
+ | | X | ||
+ | | | ||
+ | | not run | ||
+ | | not run | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | mixed minor update | ||
+ | | h -> h (noop) | ||
+ | | X | ||
+ | | not run | ||
+ | | irrelevant | ||
+ | | irrelevant | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | mixed minor update | ||
+ | | h -1 -> h | ||
+ | | not a priority | ||
+ | | not a priority | ||
+ | | not a priority | ||
+ | | not a priority | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | mixed minor update | ||
+ | | h -> h + 1 | ||
+ | | not possible (*) | ||
+ | | not possible | ||
+ | | not possible | ||
+ | | not possible | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | full upgrade | ||
+ | | n - 1 -> n | ||
+ | | | ||
+ | | X | ||
+ | | irrelevant | ||
+ | | irrelevant | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | full upgrade | ||
+ | | n -> n + 1 | ||
+ | | X | ||
+ | | | ||
+ | | irrelevant | ||
+ | | irrelevant | ||
+ | |- | ||
+ | |||
+ | | All (**) | ||
+ | | full upgrade | ||
+ | | n - 1 -> n | ||
+ | | | ||
+ | | X | ||
+ | | | ||
+ | | X | ||
+ | |- | ||
+ | |||
+ | | All | ||
+ | | full upgrade | ||
+ | | n -> n + 1 | ||
+ | | X | ||
+ | | | ||
+ | | X | ||
+ | | | ||
+ | |- | ||
+ | |||
+ | | undercloud only (tht, python-tripleoclient) | ||
+ | | full update | ||
+ | | h -> h | ||
+ | | | ||
+ | | X | ||
+ | | irrelevant | ||
+ | | irrelevant | ||
|- | |- | ||
− | | | + | | All |
− | | | + | | full update |
− | | | + | | h -> h |
+ | | | ||
+ | | X | ||
+ | | | ||
+ | | X | ||
|- | |- | ||
− | | | + | | undercloud + overcloud (e.g. nova, any other project) |
− | | | + | | full update |
− | | | + | | h -1 -> h |
+ | | not a priority | ||
+ | | not a priority | ||
+ | | not a priority | ||
+ | | not a priority | ||
|- | |- | ||
− | | | + | |
− | | | + | |} |
− | | noop | + | |
+ | (*) we already install n in undercloud so we are not really testing any upgrade in undercloud | ||
+ | |||
+ | (**) if a change is only in undercloud only repo, then we can always inject changes, but they will not be used. So it's safe to do it anyway. | ||
+ | |||
+ | === Specific releases upgraded at ci jobs === | ||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! 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 | ||
|} | |} |
Latest revision as of 12:57, 25 May 2018
Contents
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 | X | not run | irrelevant | irrelevant |
undercloud only (tht, python-tripleoclient) | mixed | n -> n + 1 | not possible | not possible | not possible | not possible |
undercloud only (tht, python-tripleoclient) | undercloud only | n -1 -> n | X | not run | not run | |
undercloud only (tht, python-tripleoclient) | undercloud only | n -> n + 1 | X | not run | not run | |
undercloud only (tht, python-tripleoclient) | mixed minor update | h -> h (noop) | X | not run | irrelevant | irrelevant |
undercloud only (tht, python-tripleoclient) | mixed minor update | h -1 -> h | not a priority | not a priority | not a priority | not a priority |
undercloud only (tht, python-tripleoclient) | mixed minor update | h -> h + 1 | not possible (*) | not possible | not possible | not possible |
undercloud only (tht, python-tripleoclient) | full upgrade | n - 1 -> n | X | irrelevant | irrelevant | |
undercloud only (tht, python-tripleoclient) | full upgrade | n -> n + 1 | X | irrelevant | irrelevant | |
All (**) | full upgrade | n - 1 -> n | X | X | ||
All | full upgrade | n -> n + 1 | X | X | ||
undercloud only (tht, python-tripleoclient) | full update | h -> h | X | irrelevant | irrelevant | |
All | full update | h -> h | X | X | ||
undercloud + overcloud (e.g. nova, any other project) | full update | h -1 -> h | not a priority | not a priority | not a priority | not a priority |
(*) we already install n in undercloud so we are not really testing any upgrade in undercloud
(**) if a change is only in undercloud only repo, then we can always inject changes, but they will not be used. So it's safe to do it anyway.
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 |