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

As a technician, you can deploy and manage the Red Hat Hyperconverged Infrastructure for Cloud solution using the Red Hat OpenStack Platform Director interface. Also, you should have a basic understanding of resource isolation, so there is not resource contention between Red Hat OpenStack Platform and Red Hat Ceph Storage.

4.1. Prerequisites

4.2. Exporting an overcloud plan using the Red Hat OpenStack Platform Director

This procedure is for exporting a deployment plan using the OpenStack Platform Director. The default deployment plan contains a common, and exportable overcloud configuration.

Prerequisites

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.

    RH OSP Director Web UI Login Screen mod
    Note

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

    [stack@director ~]$ sudo hiera admin_password
  3. On the Plans tab, select the drop-down menu 1 from the Overcloud plan, and select Export 2 .

    RH OSP Director Export Plan Menu mod
  4. Click on the Download button.

    RH OSP Director Export Plan Download mod

    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/ .

    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.

4.3. Importing an overcloud plan using the Red Hat OpenStack Platform Director

This procedure is for importing a deployment plan using the OpenStack Platform Director that has previously been exported.

Prerequisites

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.

    RH OSP Director Web UI Login Screen mod
    Note

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

    [stack@director ~]$ sudo hiera admin_password
  3. On the Plans tab, select the Import Plan button.

    RH OSP Director Import Plan Button mod

  4. Enter Plan Name 1 and click on the Choose File button 2 . 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 3 .

    RH OSP Director Import Plan Screen mod

4.4. Deploying the overcloud using the Red Hat OpenStack Platform Director

This procedure deploys the overcloud using the Red Hat OpenStack Platform Director.

Prerequisites

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.

    RH OSP Director Web UI Login Screen mod
    Note

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

    [stack@director ~]$ sudo hiera admin_password
  3. Select the default overcloud plan 1 or select the Import Plan 2 .

    RH OSP Director Manage Plans Screen Import or Overcloud Plan mod

    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

    RH OSP Director Default Plan Main Page mod
    1. Click on the Register Nodes button 1 to registered the nodes.

      RH OSP Director Overcloud Plan Workflow Screen Step1 mod
    2. Click on the Add New Node button 1 .

      RH OSP Director Adding Node Button mod

      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 1 .

      RH OSP Director Register Node Button mod

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

      RH OSP Director Introspection Button mod1

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

      RH OSP Director Introspection Button mod2

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

    1. Click on the Edit Configuration button 1 .

      RH OSP Director Overcloud Plan Workflow Screen Step2 mod
    2. On the Overall Settings tab 1 , click on the General Deployment Options section 2 , and enable the HA services via Docker, Containerized Deployment, and Default Container Images.

      RH OSP Director Configure the General Deployment Options mod
    3. On the Overall Settings tab 1 , click on the Storage section 2 , and enable the Ceph Storage Backend 3 .

      RH OSP Director Overall Settings Storage Section Enable Ceph mod

      Click on the Save Changes button.

      RH OSP Director Overall Settings Save Cancel Button Set mod
    4. Click on the Parameters tab 1 , then click on the Ceph Storage Backend section 2 to edit additional Ceph parameters.

      RH OSP Director Parameters Tab Ceph Storage Backend mod

      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}

      Update the CephConfigOverrides field with the following values.

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

      Update the CephConfigOverrides field with the following values.

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

      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}

      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.

      RH OSP Director Overall Settings Save Cancel Button Set mod
    6. Back on the plan configuration page, the saved configuration changes will appear under the Specify Deployment Configuration step.

      RH OSP Director Overcloud Plan Workflow Screen Complete Config Step2 mod
  6. Configure the roles for the hyperconverged nodes by clicking on the Manage Roles link 1 .

    RH OSP Director Manage Roles mod
    1. Unselect the BlockStorage 1 , CephStorage 2 , and Compute 3 roles by clicking on them.

      RH OSP Director Manage Roles Uncheck Default Roles mod
    2. Select the ComputeHCI 1 role by clicking on it.

      RH OSP Director Manage Roles Check ComputeHCI Role mod
    3. Back on the plan configuration page, configure the Compute HCI role by clicking on the levers icon 1 .

      RH OSP Director Configure the ComputeHCI Role mod
    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"]}

      • The OvercloudComputeHCIFlavor field with the following value:

        osd-compute
      • The ComputeHCISchedulerHints field with the following value:

        {"capabilities:node":"hci-%index%"}
    5. Click on the Save And Close button.

      RH OSP Director Overall Settings Save Cancel Button Set mod
    6. Back on the plan configuration page, configure the Controller role by clicking on the levers icon 1 .

      RH OSP Director Configure the Controller Role mod
    7. On the Parameters tab 1 , 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"]}

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

      RH OSP Director Configure the NtpServer Field mod
    9. Click on the Save And Close button.

      RH OSP Director Overall Settings Save Cancel Button Set mod
  7. Assign the number of nodes needed in the environment for each role.

    Figure 4.2. Example

    RH OSP Director Overall Assign Nodes to Each Role mod
  8. From the plan configuration page, click on the Edit Configuration button 1 .

    RH OSP Director Overcloud Plan Workflow Screen Step2 mod

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

    RH OSP Director Overall Settings Network Configuration mod

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

      RH OSP Director Select NIC Configuration mod

      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

        RH OSP Director Export Plan Download mod

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

        RH OSP Director Edit Custom Plan mod

      3. Import the plan. Enter Plan Name 1 and click on the Choose File button 2 . 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 3 .

        RH OSP Director Import Plan Screen mod

      4. Click on the Edit Configuration button.

        RH OSP Director Overcloud Plan Workflow Screen Step2 mod

      5. On the Overall Settings tab 1 , click on the Other section 2 .
      6. Select the Others section and include the custom templates.
      7. Select any new or modified files from the file list.

        Example

        RH OSP Director Include Custom Config File mod

      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.

    RH OSP Director Validate and Deploy mod
  10. Wait for the overcloud deployment to finish.

4.5. Additional Resources