openstack/openstack-ansible
Code Issues Proposed changes
Files
39280be7dd3cb606ac0e46c6f400f2331e9e0c7b
openstack-ansible/doc/source/upgrade-guide/reference-scripts.rst
Nish Patwa 39280be7dd [DOCS] Added dynamic content to Upgrade guide from conf.py 
Modified conf.py that replaces certain variables with the strings
as per the release name. Thus it makes easier to update the document
whenever release changes.

Closes-Bug: 1620275

Change-Id: I3b9457fc9e193e6a4b417d935b8588b4d0a7e450
2016-09-18 19:46:42 +00:00

1.5 KiB
Raw Blame History

Scripts

This section describes scripts that are used in the upgrade process in detail.

Within the main scripts directory there is a upgrade-utilities directory, which contains additional scripts that facilitate the initial upgrade process.

run-upgrade.sh

This script controls the overall upgrade process for deployers choosing not to do so manually.

It provides the following environment variables:

  • SCRIPTS_PATH - path to the top level scripts directory
  • MAIN_PATH - openstack_ansible root directory.
  • UPGRADE_PLAYBOOKS - 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 of the form . For example, once the script has processed the file /etc/openstack_deploy/user_variables.yml, it creates . This indicates to OpenStack-Ansible to skip this step on successive runs. The script itself does not check for this file.

Called by config-change-playbook

View Git Blame Copy Permalink