When the control plane has a separate NIC connected to ToR for Device Management to control various devices like iDRAC, switches and PowerVault, separate switches for management and host network are used. Omnia will run the management network POD for this network. An additional unmanaged switch is needed as a pass through switch.
Depending on internet access for host nodes, there are two ways to achieve a dedicated NIC setup:
base_vars.ymlbecome optional variables as the control plane is not required to be a gateway to the network. The network design would follow the below diagram:
base_vars.ymlare used to indicate that the control plane is the gateway for all compute nodes to get internet access. Since all public network traffic will be routed through the control plane, the user may have to take precautions to avoid bottlenecks in such a set-up.
Depending on the user input in
base_vars.yml, the below table explains the outcomes of running
control_plane.yml to configure the network:
|network_interface_type||device_config_support||idrac_support||Outcome||One Touch Config Support|
|Dedicated||TRUE||TRUE||Omnia will assign IPs to all the management ports of the different devices. iDRAC and PXE provisioning is supported. Here, ethernet, InfiniBand and powervault configurations are supported.||Yes|
|TRUE||FALSE||An assert failure on control_plane_common will manifest and Omnia Control Plane will fail.||No|
|FALSE||TRUE||Assuming the device_ip_list is populated, mgmt_container will not be used to assign the IPs to all the mgmt ports as a device_ip_list indicates that IP assignment is already done. However, ethernet, InfiniBand, powervault configurations are supported.||Yes|
|FALSE||FALSE||No IPs will be assigned by Omnia. Provisioning will only be through PXE.||No|
device_config_supportis false (ie, no management container is set up), no IPs will be assigned by Omnia. If a device IP list is provided, provisioning will only be through PXE.