Jump to: navigation, search

Difference between revisions of "Tripleo-upgrades-fs-variables"

Line 1: Line 1:
 +
== Tripleo upgrades releases control variables ==
 +
 
* They are used at tqe, tripleo-upgrade and toci
 
* 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 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.
  
Actual permutation of variables that defines the install/deploy and upgrade release:
+
=== Type of upgrades executed ===
  
 
{| class="wikitable"
 
{| class="wikitable"

Revision as of 06:50, 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.

Type of upgrades executed

Fs variable Undercloud Overcloud
 overcloud_upgrade: true 
 mixed_upgrade: true      
n n - 1 -> n
  ffu_overcloud_upgrade: true
  mixed_upgrade: true
n + 3 n -> n + 3
  undercloud_upgrade: true
n -> n + 1 noop