Chapter 7. Creating the overcloud
Chapter 7. Creating the overcloud When your custom environment files are ready, you can specify the flavors and nodes that each role uses and then execute the deployment. The following subsections explain both steps in greater detail. 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, ~/templates/storage-config.yaml ). For this purpose, use the following parameters: Table 7.1. Roles and Flavors for Overcloud Nodes Heat Template Parameter Description ControllerCount The number of Controller nodes to scale out OvercloudControlFlavor The flavor to use for Controller nodes ( control ) ComputeCount The number of Compute nodes to scale out OvercloudComputeFlavor The flavor to use for Compute nodes ( compute ) CephStorageCount The number of Ceph storage (OSD) nodes to scale out OvercloudCephStorageFlavor The flavor to use for Ceph Storage (OSD) nodes ( ceph-storage ) CephMonCount The number of dedicated Ceph MON nodes to scale out OvercloudCephMonFlavor The flavor to use for dedicated Ceph MON nodes ( ceph-mon ) CephMdsCount The number of dedicated Ceph MDS nodes to scale out OvercloudCephMdsFlavor The flavor to use for dedicated Ceph MDS nodes ( ceph-mds ) Important The CephMonCount , CephMdsCount , OvercloudCephMonFlavor , and OvercloudCephMdsFlavor parameters (along with the ceph-mon and ceph-mds flavors) will only be valid if you created a custom CephMON and CephMds role, as described in Chapter 3, Deploying 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 : Note See Creating the Overcloud with the CLI Tools from the Director Installation and Usage guide for a more complete list of Heat template parameters. 7.2. Initiating overcloud deployment Note 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, as described in Enabling SSL/TLS on Overcloud Public Endpoints in the Advanced Overcloud Customization guide. Note If you want to add Ceph Dashboard during your overcloud deployment, see Chapter 8, Adding the Red Hat Ceph Storage Dashboard to an overcloud deployment . The creation of the overcloud requires additional arguments for the openstack overcloud deploy command. For example: The above command uses the following options: --templates - Creates the overcloud from the default heat template collection, /usr/share/openstack-tripleo-heat-templates/ . -r /home/stack/templates/roles_data_custom.yaml - Specifies the customized roles definition file from Chapter 3, Deploying 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 deploys 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/cinder-backup.yaml - Enables the Block Storage Backup service ( cinder-backup ), as described in Section 4.2.1, "Configuring the Backup Service to use Ceph" . -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 the NTP server. Tip 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: In this case, the answers file /home/stack/templates/answers.yaml contains: See Including environment files in an overcloud deployment for more details. For a full list of options, run: For more information, see Configuring a basic 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:
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 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/cinder-backup.yaml -e /home/stack/templates/storage-config.yaml -e /home/stack/templates/ceph-config.yaml --ntp-server pool.ntp.org openstack overcloud deploy -r /home/stack/templates/roles_data_custom.yaml --answers-file /home/stack/templates/answers.yaml --ntp-server pool.ntp.org 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/cinder-backup.yaml - /home/stack/templates/storage-config.yaml - /home/stack/templates/ceph-config.yaml openstack help overcloud deploy source ~/stackrc openstack stack list --nested