When a new Virtual Machine is launched, OpenNebula will connect its virtual network interfaces (defined by
NIC attributes) to hypervisor network link devices as defined in the corresponding Virtual Network. This will allow the VM to have access to public and private networks.
OpenNebula supports the following networking modes:
Bridged. The VM NIC is added to a Linux bridge on the Host. This mode can be configured to use Security Groups and network isolation.
802.1Q VLAN. The VM NIC is added to a Linux bridge on the Host and the Virtual Network is configured to handle 802.1Q VLAN isolation.
VXLAN. The VM NIC is added to a Linux bridge on the Host and the Virtual Network implements isolation using the VXLAN encapsulation.
Open vSwitch. The VM NIC is added to a Open vSwitch bridge on the Host and the Virtual Network optionally handles 802.1Q VLAN isolation.
Open vSwitch on VXLAN. The VM NIC is added to a Open vSwitch bridge on the Host and the Virtual Network is configured to provide both isolation with VXLAN encapsulation and optionally 802.1Q VLAN.
VN_MAD of a Virtual Network determines which of the above networking modes is used.
Security Groups are not supported in the Open vSwitch modes.
How Should I Read This Chapter¶
Before reading this chapter make sure you are familiar with the Open Cloud Storage. It’s necessary to be aware of requirements for your selected storage solution in order to be able to design the network architecture of your hypervisor nodes.
Read the common Node Setup section to learn how to configure your Hosts, and then proceed to the specific section for the networking mode that you are interested in.
Next, if you are interested in optional integration with the IP Address Manager (IPAM), the external mechanism that allocates and assigns the IP addresses for the Virtual Machines, you can continue to the section about developing IPAM driver.
This chapter applies to KVM, LXC and Firecracker.