openstack/openstack-ansible
Code Issues Proposed changes

Fixing some typos in documentation

Browse Source 
Correcting numbering order in
doc/source/install-guide/app-minorupgrade.rst

Change-Id: Ib4fd0d991d94e3a29bd135ffdcb6ec40cf226214
Closes-Bug: 1543645
This commit is contained in:
Ala Raddaoui
2016-02-09 22:36:07 +00:00
parent 03db583b6e
commit bb662fc2b2
1 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
doc/source/install-guide/app-minorupgrade.rst
View File

@@ -11,50 +11,50 @@ A minor upgrade will typically require the execution of the following:
#. Change directory into the repository clone root directory
.. code-block:: shell-session
.. code-block:: shell-session
# cd /opt/openstack-ansible
#. Update the git remotes
.. code-block:: shell-session
.. code-block:: shell-session
# git fetch --all
#. Checkout the latest tag (the below tag is an example)
.. code-block:: shell-session
.. code-block:: shell-session
# git checkout 12.0.1
#. Update all the dependent roles to the latest versions
.. code-block:: shell-session
.. code-block:: shell-session
# ./scripts/bootstrap-ansible.sh
#. Change into the playbooks directory
.. code-block:: shell-session
.. code-block:: shell-session
# cd playbooks
#. Update the Hosts
.. code-block:: shell-session
.. code-block:: shell-session
# openstack-ansible setup-hosts.yml
#. Update the Infrastructure
.. code-block:: shell-session
.. code-block:: shell-session
# openstack-ansible -e rabbitmq_upgrade=true \
setup-infrastructure.yml
8. Update all OpenStack Services
#. Update all OpenStack Services
.. code-block:: shell-session
.. code-block:: shell-session
# openstack-ansible setup-openstack.yml
@@ -62,16 +62,16 @@ Note that if you wish to scope the upgrades to specific OpenStack components
then each of the component playbooks may be executed and scoped using groups.
For example:
1. Update only the Compute Hosts
#. Update only the Compute Hosts
.. code-block:: shell-session
.. code-block:: shell-session
# openstack-ansible os-nova-install.yml --limit nova_compute
2. Update only a single Compute Host. Note that skipping the 'nova-key' tag is
#. Update only a single Compute Host. Note that skipping the 'nova-key' tag is
necessary as the keys on all compute hosts will not be gathered.
.. code-block:: shell-session
.. code-block:: shell-session
# openstack-ansible os-nova-install.yml --limit <node-name> \
--skip-tags 'nova-key'
@@ -80,43 +80,43 @@ If you wish to see which hosts belong to which groups, the
``inventory-manage.py`` script will show all groups and their hosts.
For example:
1. Change directory into the repository clone root directory
#. Change directory into the repository clone root directory
.. code-block:: shell-session
.. code-block:: shell-session
# cd /opt/openstack-ansible
2. Show all groups and which hosts belong to them
#. Show all groups and which hosts belong to them
.. code-block:: shell-session
.. code-block:: shell-session
# ./scripts/inventory-manage.py -G
3. Show all hosts and which groups they belong to
#. Show all hosts and which groups they belong to
.. code-block:: shell-session
.. code-block:: shell-session
# ./scripts/inventory-manage.py -g
You may also see which hosts a playbook will execute against, and which tasks
will be executed:
1. Change directory into the repository clone playbooks directory
#. Change directory into the repository clone playbooks directory
.. code-block:: shell-session
.. code-block:: shell-session
# cd /opt/openstack-ansible/playbooks
2. See the hosts in the nova_compute group which a playbook will execute against
#. See the hosts in the nova_compute group which a playbook will execute against
.. code-block:: shell-session
.. code-block:: shell-session
# openstack-ansible os-nova-install.yml --limit nova_compute \
--list-hosts
3. See the tasks which will be executed on hosts in the nova_compute group
#. See the tasks which will be executed on hosts in the nova_compute group
.. code-block:: shell-session
.. code-block:: shell-session
# openstack-ansible os-nova-install.yml --limit nova_compute \
--skip-tags 'nova-key' \