OpenStack midplane and use of the Fusionsphere opstack planning and design need to have which network plane, each plane mainly take those services.
Communication plane Description Interoperability requirements
Internal_base FusionSphere OpenStack internal management and PXE installation network. The plane is untag plane. The plane is a Layer 2 network and does not support Layer 3 communication.
External_api An external API management plane that is connected to an external network through which internal virtual machines can be accessed from external networks. Need to communicate with the management plane three layers.
External_om The internal OM management plane is connected to the external network. The network can be connected to the external network through the internal network. The VRM node of the FusionCompute and the management plane of the host are interconnected. The VNC is used to access the virtual machine to connect to the UDS service. The FusionCompute management node is connected to the FTP service. Need to communicate with the management plane three layers
External_base can currently be replaced with the External_OM plane.
The FusionSphere OpenStack and the FusionCompute host need to communicate with each other through the plane. The Rabbitmq service and the FNM are used to collect the network information of the FusionCompute.
Management plane The VRM node of the FusionCompute and the management network plane where the host resides. Need and
External_om Layer 3 interworking.
Communication plane Description Interoperability requirements
Storage_data The internal storage plane when using KVM resources. It can be used to access FusionStorage and other storage device networks.
