![Jesse Pretorius](/assets/img/avatar_default.png)
Boss drum, motivating rhythm of life with the healing, rhythmic synergy. More seriously, this patch re-arranges the documentation structure to conform to the structure outlined in [1]. With it, some changes are made to effectively transition the links and simplify the sphinx configuration. The Mitaka/Liberty documentation links are removed as they are no longer available. [1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html Change-Id: Icc985de3af4de5ea7a5aa01b6e6f6e524c67f11b
1.7 KiB
Scripts
This section describes in detail the scripts that are used in the upgrade process.
Within the main scripts
directory there is an upgrade-utilities
directory,
which contains additional scripts that facilitate the initial upgrade
process.
run-upgrade.sh
The run-upgrade.sh
script controls the overall upgrade
process for deployers who do not want to upgrade manually. It provides
the following environment variables:
SCRIPTS_PATH
- The path to the top level scripts directoryMAIN_PATH
- Theopenstack_ansible
root directory.UPGRADE_PLAYBOOKS
- The path to the playbooks used in upgrading
The upgrade script also bootstraps OpenStack-Ansible (using
bootstrap-ansible.sh
) in order to provide the new role
dependencies introduced in the series.
migrate_openstack_vars.py
Upstream decisions influenced the change of some variable names in .
This script replaces any instances of these strings in the variable
override files matching the pattern
/etc/openstack_deploy/user_*.yml
. Variable names within
comments are updated.
This script creates files in the form
VARS_MIGRATED_<filename>
and places them in
directory. For example, after the script processes the
/etc/openstack_deploy/user_variables.yml
file, it creates
the VARS_MIGRATED_user_variables.yml
file in the directory.
This indicates to OpenStack-Ansible to skip this step on successive
runs. The script itself does not check for this file.
This script is called by the config-change-playbook
.