Hyperconverged Infrastructure Guide

Procedure

1. Prepare the predefined custom overcloud role for hyperconverged nodes, ComputeHCI.
2. Configure resource isolation.
3. Map storage management network ports to NICs.
4. Deploy the overcloud.
5. (Optional) Scale the hyperconverged nodes.

Procedure

1. Generate a custom roles_data.yaml file that includes ComputeHCI, along with other roles you intend to use for the overcloud:

   $ openstack overcloud roles generate -o /home/stack/roles_data.yaml Controller ComputeHCI Compute CephStorage

   For more information about custom roles, see Composable Services and Custom Roles and Examining the roles_data file.

2. Create a new heat template named ports.yaml in ~/templates.

3. Configure port assignments for the ComputeHCI role by adding the following configuration to the ports.yaml file:

   resource_registry:
     OS::TripleO::ComputeHCI::Ports::ExternalPort: /usr/share/openstack-tripleo-heat-templates/network/ports/<ext_port_file>.yaml
     OS::TripleO::ComputeHCI::Ports::InternalApiPort: /usr/share/openstack-tripleo-heat-templates/network/ports/internal_api.yaml
     OS::TripleO::ComputeHCI::Ports::StoragePort: /usr/share/openstack-tripleo-heat-templates/network/ports/storage.yaml
     OS::TripleO::ComputeHCI::Ports::TenantPort: /usr/share/openstack-tripleo-heat-templates/network/ports/tenant.yaml
     OS::TripleO::ComputeHCI::Ports::StorageMgmtPort: /usr/share/openstack-tripleo-heat-templates/network/ports/<storage_mgmt_file>.yaml

   • Replace <ext_port_file> with the name of the external port file. Set to "external" if you are using DVR, otherwise set to "noop". For details on DVR, see Configure Distributed Virtual Routing (DVR).

   • Replace <storage_mgmt_file> with the name of the storage management file. Set to one of the following values:

     Value	Description
     storage_mgmt	Use if you do not want to select from a pool of IPs, and your environment does not use IPv6 addresses.
     storage_mgmt_from_pool	Use if you want the ComputeHCI role to select from a pool of IPs.
     storage_mgmt_v6	Use if your environment uses IPv6 addresses.
     storage_mgmt_from_pool_v6	Use if you want the ComputeHCI role to select from a pool of IPv6 addresses

     For more information, see Basic network isolation.

4. Create a flavor for the ComputeHCI role:

   $ openstack flavor create --id auto --ram 6144 --disk 40 --vcpus 4 computeHCI

5. Configure the flavor properties:

   $ openstack flavor set --property "cpu_arch"="x86_64" \
   --property "capabilities:boot_option"="local" \
   --property "resources:CUSTOM_BAREMETAL"="1" \
   --property "resources:DISK_GB"="0" \
   --property "resources:MEMORY_MB"="0" \
   --property "resources:VCPU"="0" computeHCI

6. Map the flavor to a new profile:

   $ openstack flavor set --property "capabilities:profile"="computeHCI" computeHCI

7. Retrieve a list of your nodes to identify their UUIDs:

   $ openstack baremetal node list

8. Tag nodes into the new profile:

   $ openstack baremetal node set --property capabilities='profile:computeHCI,boot_option:local' <UUID>

   For more information, see Manually Tagging the Nodes and Assigning Nodes and Flavors to Roles.

9. Add the following configuration to the node-info.yaml file to associate the computeHCI flavor with the ComputeHCI role:

   parameter_defaults:
     OvercloudComputeHCIFlavor: computeHCI
     ComputeHCICount: 3

Procedure

1. Copy the compute.yaml heat template file for your environment from the /usr/share/openstack-tripleo-heat-templates/network/config directory. The following options are available:

   • single-nic-vlans
   • single-nic-linux-bridge-vlans
   • multiple-nics

   • bond-with-vlans

     See the README.md in each template’s directory for details on the NIC configuration.

2. Create a new directory within `~/templates called nic-configs.
3. Paste your copy of the compute.yaml template into ~/templates/nic-configs/ and rename it to compute-hci.yaml.

4. Check the parameters: section of ~/templates/nic-configs/compute-hci.yaml for the following definition:

   StorageMgmtNetworkVlanID:
     default: 40
     description: Vlan ID for the storage mgmt network traffic.
     type: number

   Add the StorageMgmtNetworkVlanID definition if it is not already in the compute-hci.yaml file.

5. Map StorageMgmtNetworkVlanID to a specific NIC on each HCI node. For example, if you chose to trunk VLANs to a single NIC, then add the following entry to the network_config: section of ~/templates/nic-configs/compute-hci.yaml:

             type: vlan
             device: em2
             mtu: 9000
             use_dhcp: false
             vlan_id: {get_param: StorageMgmtNetworkVlanID}
             addresses:
               -
                 ip_netmask: {get_param: StorageMgmtIpSubnet}

   Note

   Set MTU to 9000 (jumbo frames) when mapping a NIC to StorageMgmtNetworkVlanID to improve the performance of Red Hat Ceph Storage. For more information, see Configure MTU Settings in Director and Configuring jumbo frames.

6. Create a networking environment file called ~/templates/network.yaml.

7. Add the following configuration to the network.yaml file:

   resource_registry:
   OS::TripleO::ComputeHCI::Net::SoftwareConfig: /home/stack/templates/nic-configs/compute-hci.yaml

   This file will be used later to invoke the customized Compute NIC template (~/templates/nic-configs/compute-hci.yaml) during overcloud deployment.