openstack
/
tripleo-docs
Code Issues Proposed changes

Node scaling now covered by baremetal_provision 

Node scaling with ephemeral Heat no longer works this way. Instead
users should follow the baremetal_provision guide on node scaling:
https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/provisioning/baremetal_provision.html#scaling-the-overcloud

Change-Id: I7420904aef6e3ebf74a36f8a3c420482cde1b2d9
This commit is contained in:
Brendan Shephard 2022-10-20 09:05:48 +10:00
parent cb39bb97d2
commit 9bc4ab7bf8
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, 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 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, capacity should be decreased. This is now covered by the new Baremetal
first an environment file should be created:: provisioning process. Please refer to the following document for this node
scaling procedure :doc:`../provisioning/baremetal_provision`
$ 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