daz 875c5e4e6e [docs] Revise upgrade guide structure
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
2016-06-16 14:46:55 +10:00

132 lines
3.1 KiB
ReStructuredText

.. _minor-upgrades:
==============
Minor upgrades
==============
.. note:: To avoid issues and simplify troubleshooting during an upgrade,
first disable the security hardening role by setting your
variable ``apply_security_hardening`` to ``False`` in the
:file:`user_variables.yml` file.
A minor upgrade typically requires the following steps:
#. Change directory into the repository clone root directory:
.. code-block:: console
# cd /opt/openstack-ansible
#. Ensure your OpenStack-Ansible code is on the latest Newton release tag (14.x.x):
.. code-block:: console
# git checkout stable/newton
# LATEST_TAG=$(git describe --abbrev=0 --tags)
# git checkout ${LATEST_TAG}
#. Update all the dependent roles to the latest version:
.. code-block:: console
# ./scripts/bootstrap-ansible.sh
#. Change into the playbooks directory:
.. code-block:: console
# cd playbooks
#. Update the hosts:
.. code-block:: console
# openstack-ansible setup-hosts.yml
#. Update the infrastructure:
.. code-block:: console
# openstack-ansible -e rabbitmq_upgrade=true \
setup-infrastructure.yml
#. Update all OpenStack services:
.. code-block:: console
# openstack-ansible setup-openstack.yml
.. note::
Scope upgrades to specific OpenStack components by
executing each of the component playbooks using groups.
For example:
#. Update only the Compute hosts:
.. code-block:: console
# openstack-ansible os-nova-install.yml --limit nova_compute
#. Update only a single Compute host:
.. note::
Skipping the ``nova-key`` tag is necessary as the keys on
all Compute hosts will not be gathered.
.. code-block:: console
# openstack-ansible os-nova-install.yml --limit <node-name> \
--skip-tags 'nova-key'
To see which hosts belong to which groups, the
``inventory-manage.py`` script shows all groups and their hosts.
For example:
#. Change directory into the repository clone root directory:
.. code-block:: console
# cd /opt/openstack-ansible
#. Show all groups and which hosts belong to them:
.. code-block:: console
# ./scripts/inventory-manage.py -G
#. Show all hosts and which groups they belong:
.. code-block:: console
# ./scripts/inventory-manage.py -g
To see which hosts a playbook will execute against, and to see which
tasks will execute.
#. Change directory into the repository clone playbooks directory:
.. code-block:: console
# cd /opt/openstack-ansible/playbooks
#. See the hosts in the ``nova_compute`` group which a playbook executes against:
.. code-block:: console
# openstack-ansible os-nova-install.yml --limit nova_compute \
--list-hosts
#. See the tasks which will be executed on hosts in the ``nova_compute`` group:
.. code-block:: console
# openstack-ansible os-nova-install.yml --limit nova_compute \
--skip-tags 'nova-key' \
--list-tasks
--------------
.. include:: navigation.txt