When a new Virtual Machine is launched, OpenNebula will connect its network interfaces (defined by NIC attribute) to hypervisor physical devices as defined in the Virtual Network. This will allow the VM to have access to different networks, public or private.
OpenNebula supports four different networking modes:
- Bridged. The Virtual Machine is directly attached to an existing bridge in the hypervisor. This mode can be configured to use security groups and network isolation.
- VLAN. Virtual Networks are implemented through 802.1Q VLAN tagging.
- VXLAN. Virtual Networks implements VLANs using the VXLAN protocol that relies on a UDP encapsulation and IP multicast.
- Open vSwitch. Similar to the VLAN mode but using an openvswitch instead of a Linux bridge.
- Open vSwitch on VXLAN. Similar to the VXLAN mode but using an openvswitch instead of a Linux bridge.
When you create a new network you will need to add the attribute
VN_MAD to the template, specifying which of the above networking modes you want to use.
Security Groups are not supported by the Open vSwitch mode.
Each network driver has 3 different configuration actions executed before (pre) and after(post) the VM is booted, and when the VM leaves (clean) the host. Each one of those driver actions can be extended with custom programs by placing executable files inside the corresponding action folders (pre.d, post.d and clean.d) within the network driver directory.
Finally, the networking stack of OpenNebula can be integrated with an external IP address manager (IPAM). To do so, you need to develop the needed glue, for more details refer to the IPAM driver guide.
How Should I Read This Chapter¶
Before reading this chapter make sure you have read the Open Cloud Storage chapter.
Start by reading 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.
This chapter applies to KVM and LXD.