[ops-guide] Removes remaining instances of rpc

Also makes the repo public for contributor access

Change-Id: I1db347d8a521577d22d0afed65384ee3bd19a494
Implements: blueprint create-ops-guide
This commit is contained in:
Alexandra Settle 2016-12-22 16:14:44 +00:00
parent c22366d0e7
commit c6c06c5c9b
4 changed files with 8 additions and 32 deletions

View File

@ -2,8 +2,6 @@
Galera cluster maintenance
==========================
maintenance-tasks/ops-galera-recovery.rst
Routine maintenance includes gracefully adding or removing nodes from
the cluster without impacting operation and also starting a cluster
after gracefully shutting down all nodes.

View File

@ -40,15 +40,15 @@ needed in an environment, it is possible to create additional nodes.
.. code:: console
# /opt/rpc-openstack/openstack-ansible/playbooks/inventory/dynamic_inventory.py > /dev/null
# /opt/openstack-ansible/playbooks/inventory/dynamic_inventory.py > /dev/null
#. Create the ``/root/add_host.limit`` file, which contains all new node
host names.
.. code:: console
# /opt/rpc-openstack/openstack-ansible/scripts/inventory-manage.py \
-f /opt/rpc-openstack/openstack-ansible/playbooks/inventory/dynamic_inventory.py \
# /opt/openstack-ansible/scripts/inventory-manage.py \
-f /opt/openstack-ansible/playbooks/inventory/dynamic_inventory.py \
-l |awk -F\| '/<NEW COMPUTE NODE>/ {print $2}' |sort -u | tee /root/add_host.limit
#. Run the ``setup-everything.yml`` playbook with the
@ -65,26 +65,6 @@ needed in an environment, it is possible to create additional nodes.
# openstack-ansible setup-everything.yml --limit @/root/add_host.limit
# openstack-ansible --tags=openstack-host-hostfile setup-hosts.yml
#. Run the rpc-support playbooks.
.. code:: console
# ( cd /opt/rpc-openstack/rpcd/playbooks ; openstack-ansible rpc-support.yml )
#. Generate a new impersonation token, and add that token after the
`maas_auth_token` variable in the ``user_rpco_variables_overrides.yml``
file.
.. code:: console
- Update maas_auth_token /etc/openstack_deploy/user_rpco_variables_overrides.yml
#. Run the MaaS playbook on the deployment host.
.. code:: console
# ( cd /opt/rpc-openstack/rpcd/playbooks ; openstack-ansible setup-maas.yml
--limit @/root/add_host.limit )
Test new nodes
~~~~~~~~~~~~~~
@ -110,7 +90,7 @@ cluster.
If necessary, also modify the ``used_ips`` stanza.
#. If the cluster is utilizing Telemetry/Metering (Ceilometer),
#. If the cluster is utilizing Telemetry/Metering (ceilometer),
edit the ``/etc/openstack_deploy/conf.d/ceilometer.yml`` file and add the
host to the ``metering-compute_hosts`` stanza.
@ -134,8 +114,8 @@ To remove a compute host, follow the below procedure.
.. note::
This guide describes how to remove a compute node from an OSA environment
completely. Perform these steps with caution, as the compute node will no
This guide describes how to remove a compute node from an OpenStack-Ansible
environment completely. Perform these steps with caution, as the compute node will no
longer be in service after the steps have been completed. This guide assumes
that all data and instances have been properly migrated.

View File

@ -56,9 +56,6 @@ follow these steps.
#. Log into the ``infra01`` server.
#. Change to the ``/opt/rpc-openstack/openstack-ansible`` directory.
#. Change to the ``/opt/openstack-ansible`` directory.
#. The ``scripts`` directory contains scripts used in the installation.
Generally, directories and subdirectories under ``rpcd``
contain files related to RPCO. For example, the
``rpcd/playbooks`` directory contains the RPCO playbooks.

View File

@ -21,6 +21,7 @@ review.
.. toctree::
:maxdepth: 1
draft-operations-guide/index
upgrade-guide/index
developer-docs/index
inventory/index