Each of the different architectures has different network requirements. You should use, at least, network electronics supporting ?1Gbit connectivity
In the following table we are disclosing the details to each scenario:
Architecture
Requirements
Sample diagram
Single Node
This configuration is designed for quick tests and Openstack capabilities verification. For its setup, the server in which is running need 1 NICs. The network connected interface will be also serve as the virtual machines platform access interface. Hence, this configuration does not differentiate between Public Network and Management Network, not being suitable for production solutions.
Dual Node
This configuration is designed for small environments and Openstack proofs of concept. Network requirements are very similar those of the single node scenario, with a significant difference: the 'disconnected' interface of the previous architecture does not exist in the Controller Node and it is now used to connect with the new Compute Nodes that are connected to the solution.
For its deployment, we recommend two different network segments:
Management Network: Connects all architecture nodes with the controller..
Service Network: Connects Compute Nodes amongst them and with nova-network to provide service.
You can opt by a solution to share the same switch with or without VLAN tagging, depending on the network requirements defined by the network administrator.
We suggest not to use two different phisical switches for these netwotks, it is not logic if we look at the recomended size for this architecture.
Standard Multi Node
This configuration is designed for small Openstack production environments. The Dual Node configuration requirements are taken as reference, and two highly recommended Service Networks can be optionally added for real environment:
Storage Network: Connects Compute Nodes with Volume Nodes. This is a network particularily dedicated to block devices data transfers It is recommended to use networks over 1Gb.
Public Network: Connects internet/intranet with the platfor through the Network Node. It should be connected to a infrastructure that allow public IP addresses asignment without compromising platform security (perimeter firewall usage).
You can opt by a solution that shares the same switch, with or without VLAN tagging, depending on the network requirements defined by the network administrator.
We suggest to use two different phisical switches for these netwotks, depending on the needs of isolation and security identified for each client.
Advanced Multi Node
In this mode, the reference architecture for Standard Multi Node is used. Please contact us for deployments of this nature.
