openstack
/
charm-deployment-guide
Code Issues Proposed changes

Add operation: scale down nova-compute 

Add an operation task form scaling down nova-compute

Minor changes to the Keystone password operation page

Change-Id: I7f7ab8f0d734f76ede3b04fc1298db7db8ac7938
This commit is contained in:
Peter Matulis 2021-05-13 16:13:45 -04:00
parent 5de7fe29d2
commit a84ebc73a5
3 changed files with 115 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
deploy-guide/source/operational-tasks.rst
View File

@ -6,7 +6,9 @@ This page lists operational tasks that can be applied to a Charmed OpenStack
cloud. Generally speaking, the cloud should be in a healthy state prior to
having these operations applied to it.
* `Change Keystone admin password`_
* `Change the Keystone admin password`_
* `Scale down the nova-compute application`_
.. LINKS
.. _Change Keystone admin password: ops-change-keystone-password.html
.. _Change the Keystone admin password: ops-change-keystone-password.html
.. _Scale down the nova-compute application: ops-scale-down-nova-compute.html

6
deploy-guide/source/ops-change-keystone-password.rst
View File

@ -1,8 +1,8 @@
:orphan:
==============================
Change Keystone admin password
==============================
==================================
Change the Keystone admin password
==================================
Preamble
--------

108
deploy-guide/source/ops-scale-down-nova-compute.rst Normal file
View File

@ -0,0 +1,108 @@
:orphan:
=======================================
Scale down the nova-compute application
=======================================
Preamble
--------
Scaling down the nova-compute application implies the removal of one or more
nova-compute units (i.e. compute nodes). This is easily done with generic Juju
commands and actions available to the nova-compute charm.
.. warning::
Make sure that all VMs hosted on the target compute node have been either
deleted or migrated to another node.
Procedure
---------
List the nova-compute units
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Display the nova-compute units:
.. code-block:: none
juju status nova-compute
This article will be based on the following output:
.. code-block:: console
Unit Workload Agent Machine Public address Ports Message
nova-compute/0* active idle 15 10.5.0.5 Unit is ready
ntp/0* active idle 10.5.0.5 123/udp chrony: Ready
ovn-chassis/0* active idle 10.5.0.5 Unit is ready
nova-compute/1 active idle 16 10.5.0.24 Unit is ready
ntp/2 active idle 10.5.0.24 123/udp chrony: Ready
ovn-chassis/2 active idle 10.5.0.24 Unit is ready
nova-compute/2 active idle 17 10.5.0.10 Unit is ready
ntp/1 active idle 10.5.0.10 123/udp chrony: Ready
ovn-chassis/1 active idle 10.5.0.10 Unit is ready
.. tip::
You can use the :command:`openstack` client to map compute nodes to
nova-compute units by IP address: ``openstack hypervisor list``.
Remove the node
~~~~~~~~~~~~~~~
Remove the compute node from the cloud by referring to its corresponding unit,
here ``nova-compute/0``:
.. code-block:: none
juju run-action --wait nova-compute/0 remove-from-cloud
The workload status of the unit can be checked with:
.. code-block:: none
juju status nova-compute/0
Sample output:
.. code-block:: console
Unit Workload Agent Machine Public address Ports Message
nova-compute/0* blocked idle 15 10.5.0.5 Unit was removed from the cloud
ntp/0* active idle 10.5.0.5 123/udp chrony: Ready
ovn-chassis/0* active idle 10.5.0.5 Unit is ready
At this point (before the unit is actually removed from the model with the
:command:`remove-unit` command) the process can be reverted with the
``register-to-cloud`` action, followed by the ``enable`` action. This
combination will restart nova-compute services and enable nova-scheduler to run
new VMs on the unit.
Remove the unit
~~~~~~~~~~~~~~~
Now that the compute node has been logically removed at the OpenStack level,
remove its unit from the model:
.. code-block:: none
juju remove-unit nova-compute/0
Request the status of the application once more:
.. code-block:: none
juju status nova-compute
The unit's removal should be confirmed by its absence in the output:
.. code-block:: console
Unit Workload Agent Machine Public address Ports Message
nova-compute/1* active idle 16 10.5.0.24 Unit is ready
ntp/2* active idle 10.5.0.24 123/udp chrony: Ready
ovn-chassis/2 active idle 10.5.0.24 Unit is ready
nova-compute/2 active idle 17 10.5.0.10 Unit is ready
ntp/1 active idle 10.5.0.10 123/udp chrony: Ready
ovn-chassis/1* active idle 10.5.0.10 Unit is ready