Description of problem:
After running instack-install-undercloud and when ~/deploy-overcloudrc file is created there is no CONTROLSCALE variable defined in it. If we support scaling out control nodes we should add this variable (default to CONTROLSCALE=1) too. Or otherwise put into instack documentation that a user should set/add CONTROLSCALE=X for scaling out ctrl nodes.
Note that there is an important bug related to scaling controller nodes:
Version-Release number of selected component (if applicable):
Jan, Please coordinate with the unified cli effort to make sure the supported scaleout configuration is supported as intended. The instack-install-overcloud shouldn't have additional enhancements made if we are working on a replacement.
(In reply to chris alfonso from comment #3)
> Jan, Please coordinate with the unified cli effort to make sure the
> supported scaleout configuration is supported as intended. The
> instack-install-overcloud shouldn't have additional enhancements made if we
> are working on a replacement.
In the new unified CLI there is a support for scaling out all of default roles including controllers:
So it's possible now to specify number of controller nodes with "--control-scale" argument when deploying overcloud.
Verified with python-rdomanager-oscplugin-0.0.8-18.el7ost.noarch:
instack-deploy-overcloud is not in use anymore, using the unified-cli we're sending '--control-scale 3' as part of the 'openstack overcloud deploy' like in the following example:
openstack overcloud deploy --plan-uuid 5eaecf2f-3c52-4fa7-b4a1-138d5822d83c --control-scale 3 --compute-scale 1 --ceph-storage-scale 1 --block-storage-scale 0 --swift-storage-scale 0 -e /home/stack/network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml --network-cidr 172.16.17.0/24 --floating-ip-cidr 10.19.184.0/24
--floating-ip-start=10.19.184.101 --floating-ip-end=10.19.184.150 --bm-network-gateway=10.19.184.254
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.