The Red Hat OpenStack Platform13 Director documentation explains the additional template configuration needed to deploy Ironic
services in the overcloud. There is no new template configuration that is specific to the Cisco Application Centric
Infrastructure (ACI) ML2 plug-in integration for OpenStack, when used with Ironic services.
If you use virtual port channels (vPCs) to connect the bare metal servers, then the Port Channel Policy assigned to the Leaf
Interface Policy Group must have only the following control parameters:
The Port Channel Policy should have the mode configured for “LACP Active.” This configuration is needed because bare metal
instances only use a single NIC when Unified Extensible Firmware Interface (UEFI) boots and attaches to bare metal networks.
Both ports are used when connecting to tenant networks. Also, the "Suspend Individual Port" option should be disabled.
If a custom composable network is used for the Ironic services, then an endpoint group (EPG) and bridge domain must be created
in Cisco ACI to implement that network. This is the same for any undercloud network implemented in Cisco ACI, as described in the section “Setting Up the Cisco APIC and the Network” section in the Cisco ACI Installation Guide for Red Hat OpenStack Using the OpenStack Platform 13 Director guide.
Regardless of where the Ironic services are created—for example, on the undercloud control network or on a custom composable
network—a subnet must be configured in the bridge domain that implements the undercloud network hosting the Ironic services.
This subnet must have a CIDR IP address that matches the subnet used for the undercloud network.
For example, if the control plane network is used for the service (default), the default value for the subnet is 1.100.1.0/24.
Therefore, some IP address on this subnet should be used as the CIDR configured in the subnet in this bridge domain.
The following diagram shows the different paths that the controller should use to reach the bare metal networks. The red arrow
going from the Controller to the Bare Metal networks shows the path that needs to be established (as opposed to the default
route). The two-headed black arrows show connections: the controller is connected to the internal, control, and management
networks, and the control and storage networks are connected to the bare metal networks.
 Note |
When using the control network for Ironic services, the IP address should be something other than 1.100.1.1, because the OpenStack
Platform allocates this IP address for the undercloud virtual machine (VM).
|
This subnet configured in the bridge domain is used as the next-hop IP address for routes that are added after deployment
so that the Ironic services can reach the bare metal networks.