
Containerized UC becomes a default installation method. Adjust the documentation to indicate that and note about instack undercloud deprecation. Clarify containers registry configuration steps and undercloud config params for it. Document the shared bits of the deployment framework leveraging overcloud and undercloud deployments. Say a few words for the CLI interface openstack tripleo deploy --standalone, used underneath instack-backwards-compatible undercloud installations. Change-Id: I2352e31857f4044eced87607c8d53841af62df32 Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
4.4 KiB
Updating Undercloud Components
Note
Instack-undercloud is deprecated in Rocky cycle. Instack undercloud
can only be upgraded to containerized undercloud. See ../containers_deployment/undercloud
for backward
compatibility related information.
Before upgrading the undercloud, it is highly suggested to perform a
backup <../controlplane_backup_restore/01_undercloud_backup>
of the undercloud and validate that a restore works fine.Remove all Delorean repositories:
Note
You may wish to backup your current repos before disabling them
mkdir -p /home/stack/REPOBACKUP sudo mv /etc/yum.repos.d/delorean* /home/stack/REPOBACKUP
sudo rm /etc/yum.repos.d/delorean*
Enable new Delorean repositories:
Clean the yum cache to ensure only the new repos are used
sudo yum clean all sudo rm -rf /var/cache/yum
Update required package:
Validations
It is strongly recommended that you validate the state of your undercloud before starting any upgrade operations. The tripleo-validations repo has some 'pre-upgrade' validations that you can execute by following the instructions at validations to execute the "pre-upgrade" group
mistral execution-get-output $(openstack workflow execution create -f value -c ID tripleo.validations.v1.run_groups '{"group_names": ["pre-upgrade"]}')
Newton to Ocata
The following commands need to be run before the undercloud upgrade:
sudo systemctl stop openstack-* sudo systemctl stop neutron-* sudo systemctl stop openvswitch sudo systemctl stop httpd sudo yum update instack-undercloud openstack-puppet-modules openstack-tripleo-common
Ocata to Pike
Ceph
Prior to Pike, TripleO deployed Ceph with puppet-ceph. With the Pike release it is possible to use TripleO to deploy Ceph with either ceph-ansible or puppet-ceph, though puppet-ceph is deprecated. To use ceph-ansible, the CentOS Storage SIG Ceph repository must be enabled on the undercloud and the ceph-ansible package must then be installed:
sudo yum install --enablerepo=extras centos-release-ceph-jewel sudo yum install ceph-ansible
Ceph clusters deployed with Ocata via puppet-ceph will be migrated so that all of the existing Ceph services are run inside of containers. This migration will be managed not by puppet-ceph, but by ceph-ansible, which TripleO will use to control updates to the same ceph cluster after the Ocata to Pike upgrade.
Update TripleO CLI package
sudo yum update python-tripleoclient*
Run the undercloud upgrade command. This command will upgrade all packages and use puppet to apply new configuration and restart all OpenStack services
openstack undercloud upgrade
To upgrade to a containerized undercloud, just add --use-heat option:
openstack undercloud upgrade --use-heat
Note
When upgrading a containerized undercloud, it's possible to enable verbose logging with --verbose option.
Queens to Rocky and later
The containerized undercloud deployment isn't supported before Rocky release. Therefore, the upgrade is supported in Rocky, from a non containerized undercloud in Queens to a containerized undercloud in Rocky.
Note
You may wish to use time and capture the output to a file for any debug
time openstack undercloud upgrade 2>&1 | tee undercloud_upgrade.log
Note
If you added custom OVS ports to the undercloud (e.g. in a virtual testing environment) you may need to re-add them at this point.