Chapter 4. Deploying Red Hat Hyperconverged Infrastructure for Cloud using the Red Hat OpenStack Platform Director

Procedure

1. Enter the IP address or host name of the undercloud into a web browser.

   Note

   If not using SSL, then the undercloud URL will need to use port 3000. For example: http://192.168.0.4:3000

2. Login to the Red Hat OpenStack Platform Director user interface using the correct credentials.

   

   View larger image

   
   Note

   The default user name is admin. You can obtain the admin password by running the following command:

   [stack@director ~]$ sudo hiera admin_password

   Copy to Clipboard Toggle word wrap

3. On the Plans tab, select the drop-down menu from the Overcloud plan, and select Export .

   

   View larger image

   

4. Click on the Download button.

   

   View larger image

   

   This will download a compressed tarball file to the local hard drive, which includes all the plan files.

   Important

   If you need to add or modify the files contained within the tarball file, then before importing the tarball file you must recreate the tarball file, as follows:

   Example

   tar -czf my-deployment-plan.tar.gz -C my-deployment-plan-local-files/ .

   Copy to Clipboard Toggle word wrap

   Note

   Currently, the OpenStack Platform Director interface does not support advance configuration of the plan, such as a custom network configuration. Advance configuration must be done manually by editing the files directly.

Procedure

1. Enter the IP address or host name of the undercloud into a web browser.

   Note

   If not using SSL, then the undercloud URL will need to use port 3000. For example: http://192.168.0.4:3000

2. Login to the Red Hat OpenStack Platform Director user interface using the correct credentials.

   

   View larger image

   
   Note

   The default user name is admin. You can obtain the admin password by running the following command:

   [stack@director ~]$ sudo hiera admin_password

   Copy to Clipboard Toggle word wrap

3. On the Plans tab, select the Import Plan button.

   

4. Enter Plan Name and click on the Choose File button . Browse to the location of the tarball file, and select it for import. Once the file is selected, click on the Upload Files and Create Plan button .

   

Procedure

1. Enter the IP address or host name of the undercloud into a web browser.

   Note

   If not using SSL, then the undercloud URL will need to include port 3000. For example: http://192.168.0.4:3000

2. Login to the Red Hat OpenStack Platform Director user interface using the correct credentials.

   

   View larger image

   
   Note

   The default user name is admin. You can obtain the admin password by running the following command:

   [stack@director ~]$ sudo hiera admin_password

   Copy to Clipboard Toggle word wrap

3. Select the default overcloud plan or select the Import Plan .

   

   View larger image

   

   For more information on importing a plan, see Section 4.3, “Importing an overcloud plan using the Red Hat OpenStack Platform Director”

4. From the plan configuration page, prepare the hardware by adding registered nodes.

   Figure 4.1. Example Plan Configuration Page

   

   View larger image

   

   1. Click on the Register Nodes button to registered the nodes.

      

      View larger image

      

   2. Click on the Add New Node button .

      

      View larger image

      

      Alternatively, you can prepare the nodes by customizing the instackenv.json host definition file and uploading it. To create a custom instackenv.json host definition file, see Section 5.2.2, “Registering and introspecting the hardware” and Section 5.2.3, “Setting the root device” to prepare the nodes.

   3. Fill out all the required fields, denoted by a small red asterisks, on the register node page.

   4. After all the required field are filled out, click on the Register Node button .

      

   5. Once the node is registered, select the node , and click on the Introspect Nodes button.

      

   6. Once the introspection is done, select the node , and click on the Provide Nodes button.

      

5. From the plan configuration page, edit the deployment configuration.

   1. Click on the Edit Configuration button .

      

      View larger image

      

   2. On the Overall Settings tab , click on the General Deployment Options section , and enable the HA services via Docker, Containerized Deployment, and Default Container Images.

      

      View larger image

      

   3. On the Overall Settings tab , click on the Storage section , and enable the Ceph Storage Backend .

      

      View larger image

      

      Click on the Save Changes button.

      

      View larger image

      

   4. Click on the Parameters tab , then click on the Ceph Storage Backend section to edit additional Ceph parameters.

      

      View larger image

      

      Update the CephAnsibleExtraConfig field with the following values:

      {"ceph_osd_docker_memory_limit": "5g", "ceph_osd_docker_cpu_limit": 1, "ceph_mds_docker_memory_limit": "4g", "ceph_mds_docker_cpu_limit": 1}

      Copy to Clipboard Toggle word wrap

      Update the CephConfigOverrides field with the following values.

      {"osd_recovery_op_priority": 3, "osd_recovery_max_active": 3, "osd_max_backfills": 1}

      Copy to Clipboard Toggle word wrap

      Update the CephConfigOverrides field with the following values.

      {"osd_recovery_op_priority": 3, "osd_recovery_max_active": 3, "osd_max_backfills": 1}

      Copy to Clipboard Toggle word wrap

      Set the CephPoolDefaultSize value to 3.

      Update the CephAnsibleDisksConfig field with a disk list.

      Example

      {"devices":["/dev/sda","/dev/sdb","/dev/sdc","/dev/sdd","/dev/sde","/dev/sdf","/dev/sdg","/dev/sdh","/dev/sdi","/dev/sdj","/dev/sdk","/dev/sdl"],"dedicated_devices":["/dev/sdm","/dev/sdm","/dev/sdm","/dev/sdm","/dev/sdn","/dev/sdn","/dev/sdn","/dev/sdn","/dev/sdo","/dev/sdo","/dev/sdo","/dev/sdo"],"journal_size":5120}

      Copy to Clipboard Toggle word wrap

      Note

      This disk listing is for block devices (devices) being used as OSDs, and the block devices dedicated (dedicated_devices) as OSD journals. See Section 5.5.5, “Setting the Red Hat Ceph Storage parameters” for more information.

   5. Click on the Save And Close button.

      

      View larger image

      

   6. Back on the plan configuration page, the saved configuration changes will appear under the Specify Deployment Configuration step.

      

      View larger image

      

6. Configure the roles for the hyperconverged nodes by clicking on the Manage Roles link .

   

   View larger image

   

   1. Unselect the BlockStorage , CephStorage , and Compute roles by clicking on them.

      

      View larger image

      

   2. Select the ComputeHCI role by clicking on it.

      

      View larger image

      

   3. Back on the plan configuration page, configure the Compute HCI role by clicking on the levers icon .

      

      View larger image

      

   4. On the Parameters tab, update the following parameters:

      • The ExtraConfig field with the calculated resource allocation values.

        See Appendix E, Tuning the Nova reserved memory and CPU allocation manually for how to calculate the appropriate values.

      • The ComputeHCIIPs field with all the relevant IP addresses for the environment.

        Example

        {"storage_mgmt":["172.16.2.203","172.16.2.204","172.16.2.205"],"storage":["172.16.1.203","172.16.1.204","172.16.1.205"],"tenant":["192.168.3.203","192.168.3.204","192.168.3.205"],"internal_api":["192.168.2.203","192.168.2.204","192.168.2.205"]}

        Copy to Clipboard Toggle word wrap

      • The OvercloudComputeHCIFlavor field with the following value:

        osd-compute

        Copy to Clipboard Toggle word wrap

      • The ComputeHCISchedulerHints field with the following value:

        {"capabilities:node":"hci-%index%"}

        Copy to Clipboard Toggle word wrap

   5. Click on the Save And Close button.

      

      View larger image

      

   6. Back on the plan configuration page, configure the Controller role by clicking on the levers icon .

      

      View larger image

      

   7. On the Parameters tab , update the ControllerIPs field with the relevant IP addresses.

      Example

      {"storage_mgmt":["172.16.2.200","172.16.2.201","172.16.2.202"],"storage":["172.16.1.200","172.16.1.201","172.16.1.202"],"tenant":["192.168.3.200","192.168.3.201","192.168.3.202"],"internal_api":["192.168.2.200","192.168.2.201","192.168.2.202"]}

      Copy to Clipboard Toggle word wrap

   8. On the Services tab , in the Ntp section , update the NtpServer field with the relevant NTP server name.

      

      View larger image

      

   9. Click on the Save And Close button.

      

      View larger image

      

7. Assign the number of nodes needed in the environment for each role.

   Figure 4.2. Example

   

   View larger image

   

8. From the plan configuration page, click on the Edit Configuration button .

   

   View larger image

   

   Edit the network configuration by clicking on the Network Configuration section , and select Network Isolation .

   

   1. Select one of the NIC configuration templates or use a custom plan.

      

      To customize the NICs in the environment, first you need to export the plan.

      See Section 4.2, “Exporting an overcloud plan using the Red Hat OpenStack Platform Director” on how to export a plan.

      1. Download the plan tarball file and make the necessary additions or modifications locally.

         Example

         

      2. After updating the plan tarball file, click the drop down menu and select Edit.

         

      3. Import the plan. Enter Plan Name and click on the Choose File button . Browse to the location of the tarball file, and select it for import. Once the file is selected, click on the Upload Files and Create Plan button .

         

      4. Click on the Edit Configuration button.

         

      5. On the Overall Settings tab , click on the Other section .
      6. Select the Others section and include the custom templates.

      7. Select any new or modified files from the file list.

         Example

         

      8. Click on the Parameters tab and update any of the values accordingly.

9. Now, it is time to deploy the plan. From the plan configuration page, click on the Validate and Deploy button to deploy the overcloud plan.

   

   View larger image

   
10. Wait for the overcloud deployment to finish.