OpenNebula

The Virtual Network Manager (VNM) will be responsible for the handling of IP and MAC addresses, allowing the creation of virtual networks by keeping trac of leases (a set form by one IP and one MAC valid on a particular network) and their association with virtual machines and the physical bridges the VM are using.

The data structure to articulate this manager will be a pool of networks, where each network can be either public or private and will consist on a pool of IPs and MACs.

The VNM will have a configuration file conforming with the following notation:

----8<------
oned.conf

NETWORK = [
NAME = "name of the network",
BRIDGE = "name of the physical bridge used by this NW"
TYPE = "{private|public}", --> default is private
MAC_MASK = "XX.XX.XX.XX.XX.XX/bitsInMask",
IP_MASK = "xx.xx.xx.xx/bitsInMask"
IPS = "x1.x1.x1.x1, x2.x2.x2.x2, ....." > optional
]
---->8------

In order to use one so defined network, a virtual machine must include a reference in their template, that can conform with the following schema:

-----8<------
NIC = [
NETWORK ="nw name",
TYPE ={private,public}
]
---->8-------

Upon submission, the Virtual Machine will get an IP and a MAC given by the VNM according to the network referenced in the template.

• NAME of the VirtualNetwork
• PHYSICAL NETWORK to bind
• CLASS B,C
• NETWORK ADDRESS

NIC = [NETWORK="public",TYPE="public",IP="147.96...",MAC="..."]
NIC = [NETWORK="blue",TYPE="private"]