openstack
/
tripleo-docs
Code Issues Proposed changes

Merge "Node scaling now covered by baremetal_provision"

This commit is contained in:
Zuul 2022-11-14 13:51:51 +00:00 committed by Gerrit Code Review
parent ef5f3ed708 9bc4ab7bf8
commit 2522113767
1 changed files with 3 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
deploy-guide/source/post_deployment/scale_roles.rst
View File

@ -4,33 +4,6 @@ Scaling overcloud roles
=======================
If you want to increase or decrease resource capacity of a running overcloud,
you can start more servers of a selected role or delete some servers if
capacity should be decreased. To set the capacity for the compute role,
first an environment file should be created::
$ cat ~/environment.yaml
parameter_defaults:
  ComputeCount: 5
Then following command can be used to deploy it::
openstack overcloud deploy --templates [templates dir] \
-e <full environment> -e ~/environment.yaml
.. note::
It is especially important to remember that you **must** include all
environment files that were used to deploy the overcloud. Make sure
you pass those in addition to your customization environments at the
end (`environment.yaml`).
.. note::
Scaling out assumes that newly added nodes has already been
registered in Ironic.
.. note::
When scaling down random servers of specified role will be deleted, how to
delete specific nodes is described in :ref:`delete_nodes`.
.. note::
The different scale parameters can be seen in the output of::
openstack help overcloud deploy
capacity should be decreased. This is now covered by the new Baremetal
provisioning process. Please refer to the following document for this node
scaling procedure :doc:`../provisioning/baremetal_provision`