Chapter 5. Mapping storage management network ports to NICs
The following procedure details how to map the storage management network ports to the physical NICs on your hyperconverged nodes.
Procedure
Copy the
compute.yamlheat template file for your environment from the/usr/share/openstack-tripleo-heat-templates/network/configdirectory. The following options are available:- single-nic-vlans
- single-nic-linux-bridge-vlans
- multiple-nics
bond-with-vlans
See the
README.mdin each template’s directory for details on the NIC configuration.
-
Create a new directory within
`~/templatescallednic-configs. -
Paste your copy of the
compute.yamltemplate into~/templates/nic-configs/and rename it tocompute-hci.yaml. Check the
parameters:section of~/templates/nic-configs/compute-hci.yamlfor the following definition:StorageMgmtNetworkVlanID: default: 40 description: Vlan ID for the storage mgmt network traffic. type: number
Add the
StorageMgmtNetworkVlanIDdefinition if it is not already in thecompute-hci.yamlfile.Map
StorageMgmtNetworkVlanIDto 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 thenetwork_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}NoteSet MTU to 9000 (jumbo frames) when mapping a NIC to
StorageMgmtNetworkVlanIDto improve the performance of Red Hat Ceph Storage. For more information, see Configure MTU Settings in Director and Configuring jumbo frames.-
Create a networking environment file called
~/templates/network.yaml. Add the following configuration to the
network.yamlfile: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.
You can use ~/templates/network.yaml to define any networking parameters, or add any customized networking heat templates. For more information, see Custom network environment file.