Configure Hierarchical Port Binding
This section describes configuring the Single Root I/O Virtualization (SR-IOV) and other VLAN-based ml2 mechanism agents to work with OpFlex plug-in. The configuration is accomplished by using Hierarchical Port Binding (HPB) and should work without any special modification to the configuration. Here are the basic steps that you need to configure OpFlex with SR-IOV.
When using HPB, data path connectivity in Cisco Application Centric Infrastructure (ACI) is accomplished by creating static VLAN bindings to the EPGs for networks created by OpenStack. There maybe other configuration required for data path, for example, setting up VLAN on SR-IOV NIC or configuring OVS (or a load balancer in case of LBaaS). This is done by the third-party agent or mechanism driver (for example, sriovnicswitch).
How to create these assets:
Before you begin
To configure the data path using static VLAN bindings, ensure that the plug-in requires following assets:
-
A physical domain (physdom) with the correct VLAN pool.
-
Host-link information (which compute node fabric Ethernet interface is connected to which leaf switch port)
-
Host-link-network-label information (describing which fabric Ethernet interface on compute node is used to serve which physnet)
-
You need this information only if the deployment uses multiple physnets.
Procedure
Before deploying OpenStack Platform Overcloud, make sure you have one Physical Domain (physdom) created per each physnet required. Add pdom_ prefix to the name of physical domain created. For example for physnet1 create pdom_physnet1, and attach the right VLAN pool. You must also set NeutronNetworkVLANRanges and enable the third-party mechanism drivers using ACIMechanismDrivers parameter, make sure that the apic_aim is the last mechanism in the list. Example:
|