Chapter 7. Creating the overcloud
When your custom environment files are ready, you can specify which flavors and nodes each role uses and then execute the deployment.
7.1. Assigning nodes and flavors to roles
Planning an overcloud deployment involves specifying how many nodes and which flavors to assign to each role. Like all Heat template parameters, these role specifications are declared in the
parameter_defaults section of your environment file (in this case,
For this purpose, use the following parameters:
Table 7.1. Roles and Flavors for Overcloud Nodes
|Heat Template Parameter||Description|
The number of Controller nodes to scale out
The flavor to use for Controller nodes (
The number of Compute nodes to scale out
The flavor to use for Compute nodes (
The number of Ceph storage (OSD) nodes to scale out
The flavor to use for Ceph Storage (OSD) nodes (
The number of dedicated Ceph MON nodes to scale out
The flavor to use for dedicated Ceph MON nodes (
The number of dedicated Ceph MDS nodes to scale out
The flavor to use for dedicated Ceph MDS nodes (
OvercloudCephMdsFlavor parameters (along with the
ceph-mds flavors) will only be valid if you created a custom
CephMds role, as described in Chapter 3, Deploying Other Ceph Services on dedicated nodes.
For example, to configure the overcloud to deploy three nodes for each role (Controller, Compute, Ceph-Storage, and CephMon), add the following to your
parameter_defaults: ControllerCount: 3 OvercloudControlFlavor: control ComputeCount: 3 OvercloudComputeFlavor: compute CephStorageCount: 3 OvercloudCephStorageFlavor: ceph-storage CephMonCount: 3 OvercloudCephMonFlavor: ceph-mon CephMdsCount: 3 OvercloudCephMdsFlavor: ceph-mds
7.2. Initiating overcloud deployment
During undercloud installation, set
generate_service_certificate=false in the
undercloud.conf file. Otherwise, you must inject a trust anchor when you deploy the overcloud. For more information about how to inject a trust anchor, see Enabling SSL/TLS on Overcloud Public Endpoints in the Advanced Overcloud Customization guide.
The creation of the overcloud requires additional arguments for the
openstack overcloud deploy command. For example:
$ openstack overcloud deploy --templates -r /home/stack/templates/roles_data_custom.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-rgw.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-mds.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-network.yaml \ -e /home/stack/templates/storage-config.yaml \ -e /home/stack/templates/ceph-config.yaml \ --ntp-server pool.ntp.org
The above command uses the following options:
--templates- Creates the Overcloud from the default Heat template collection (namely,
-r /home/stack/templates/roles_data_custom.yaml- Specifies the customized roles definition file from Chapter 3, Deploying Other Ceph Services on dedicated nodes, which adds custom roles for either Ceph MON or Ceph MDS services. These roles allow either service to be installed on dedicated nodes.
-e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml- Sets the director to create a Ceph cluster. In particular, this environment file will deploy a Ceph cluster with containerized Ceph Storage nodes.
-e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-rgw.yaml- Enables the Ceph Object Gateway, as described in Section 4.2, “Enabling the Ceph Object Gateway”.
-e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-mds.yaml- Enables the Ceph Metadata Server, as described in Section 4.1, “Enabling the Ceph Metadata server”.
-e /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml- Enables the Block Storage Backup service (
cinder-backup), as described in Section 4.4, “Configuring the Backup Service to use Ceph”.
-e /usr/share/openstack-tripleo-heat-templates/environments/docker.yaml- Configures Docker for the Red Hat OpenStack Platform.
-e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml- Enables high availability deployment of Controller nodes.
-e /usr/share/openstack-tripleo-heat-templates/environments/docker-network.yaml- Configures network settings.
-e /home/stack/templates/storage-config.yaml- Adds the environment file containing your custom Ceph Storage configuration.
-e /home/stack/templates/ceph-config.yaml- Adds the environment file containing your custom Ceph cluster settings, as described in Chapter 5, Customizing the Ceph Storage cluster.
--ntp-server pool.ntp.org- Sets our NTP server.
You can also use an answers file to invoke all your templates and environment files. For example, you can use the following command to deploy an identical overcloud:
$ openstack overcloud deploy -r /home/stack/templates/roles_data_custom.yaml \ --answers-file /home/stack/templates/answers.yaml --ntp-server pool.ntp.org
In this case, the answers file
templates: /usr/share/openstack-tripleo-heat-templates/ environments: - /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml - /usr/share/openstack-tripleo-heat-templates/environments/ceph-rgw.yaml - /usr/share/openstack-tripleo-heat-templates/environments/ceph-mds.yaml - /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml - /home/stack/templates/storage-config.yaml - /home/stack/templates/ceph-config.yaml
For more information, see Including Environment Files in Overcloud Creation.
For a full list of options, run:
$ openstack help overcloud deploy
For more information, see Creating the Overcloud with the CLI Tools in the Director Installation and Usage guide.
The overcloud creation process begins and the director provisions your nodes. This process takes some time to complete. To view the status of the overcloud creation, open a separate terminal as the
stack user and run:
$ source ~/stackrc $ openstack stack list --nested