We need to add a comment that using this method is going to blacklist index (while scaling in would not). Reference: https://access.redhat.com/solutions/4315261 Reported by: rh.cbenon1 https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/director_installation_and_usage/scaling-overcloud-nodes#annotations:ce582533-69d0-46ad-848b-17973e77a1dc
Also: https://access.redhat.com/solutions/4232971 Basically, to make sure RoleCount is adjusted to include the new node, and we also need to scale up with: parameter_defaults: <RoleName>RemovalPolicies: [] <RoleName>RemovalPoliciesMode: update And re-run deploy by replacing template above with: parameter_defaults: <RoleName>RemovalPoliciesMode: append
A valid point was raised at our compute triage meeting is that we don't use the terms black/white list anymore. We need to use deny/allow list.
Updated content available on the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/director_installation_and_usage/assembly_scaling-overcloud-nodes#proc_removing-or-replacing-a-compute-node_scaling-overcloud-nodes https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/director_installation_and_usage/assembly_scaling-overcloud-nodes#proc_removing-or-replacing-a-compute-node_scaling-overcloud-nodes https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/scaling-overcloud-nodes#removing-or-replacing-a-compute-node