875c5e4e6e
1. Move minor upgrade content from the install guide to the upgrade guide 2. Revise the overview section to include minor upgrades 3. Restructure the upgrade guide for improved information flow 4. Add configure-keystone.rst to the old install guide that was accidently removed in https://review.openstack.org/#/c/328095/ Change-Id: I602ef4a4f95f5ff46ee9b9eaaaa6ccdfd637d1dc Implements: blueprint osa-install-guide-overhaul
3.4 KiB
Upgrade playbooks
This section describes the playbooks that are used in the upgrade process in further detail.
Within the main scripts directory there is an upgrade-utilities directory,
which contains an additional playbooks directory. These playbooks
facilitate the upgrade process.
ansible_fact_cleanup.yml
This calls a script to removes files in
/etc/openstack_deploy/ansible_facts/
deploy-config-changes.yml
This playbook backs up the /etc/openstack_deploy
directory before changing the configuration.
/etc/openstack_deploy copies once to
/etc/openstack_deploy.NEWTON.
user-secrets-adjustment.yml
This playbook ensures that the user secrets file is updated based on the example file in the main repository, making it possible to guarantee all secrets move into the upgraded environment and generate appropriately. This adds only new secrets, such as those necessary for new services or new settings added to existing services. Values set previously are not changed.
repo-server-pip-conf-removal.yml
The presence of pip.conf locks down all Python
installations to packages on the repo server. If pip.conf
exists on the repo server, it creates a circular dependency, causing
build failures.
old-hostname-compatibility.yml
This playbook ensures an alias is created for old hostnames that may not be RFC 1034 or 1035 compatible. Using a hostname alias allows agents to continue working in cases where the hostname is also the registered agent name. This playbook is only needed for upgrades of in-place upgrades of existing nodes or if a node is replaced or rebuilt it will be brought into the cluster using a compliant hostname.
setup-infrastructure.yml
The playbooks directory contains the
setup-infrastructure.yml playbook. The
run-upgrade.sh script calls
setup-insfrastructure.yml with specific arguments to
upgrade MariaDB and RabbitMQ.
For example, to run an upgrade for both components at once, run the following commands:
# openstack-ansible setup-infrastructure.yml -e 'rabbitmq_upgrade=true' \
# -e 'galera_upgrade=true'The rabbitmq_upgrade variable tells the
rabbitmq_server role to upgrade RabbitMQ.
Note
The RabbitMQ server role installs patch releases automatically,
regardless of the value of rabbitmq_upgrade. This variable
only controls upgrading the major or minor versions.
Upgrading RabbitMQ in the Newton release is optional. The
run-upgrade.sh script does not automatically upgrade it. To
upgrade RabbitMQ, insert the rabbitmq_upgrade: true line
into a file, such as:
/etc/openstack_deploy/user_variables.yml.
The galera_upgrade variable tells the
galera_server role to remove the current version of MariaDB
and Galera and upgrade to the 10.x series.
memcached-flush.yml
Sends "flush_all" to memcached with the help of nc.