[one-users] Network Configuration - IP assignment

Fri Jan 20 18:15:43 PST 2012

Thanks for the reply Ruben and Javier. I agree that delegating MAC address assignment to individual KVM hosts is not really the best approach. However, from the documentation I got a sense that OpenNebula 'must' assign MAC address to the VM which I found little bit confusing.  Thanks for clarifying the details.

--
Shantanu.

On Jan 18, 2012, at 3:50 PM, Ruben S. Montero wrote:

Hi,

The reason for using OpenNebula to assign MAC addresses mainly applies for distributed environments (more than one hypervisor).

Note that you not only need the hypervisor  to assign the MAC address but also guarantee that the MAC address has not been assigned  by other KVM in your infrastructure (in the same VLAN).  This can be done to some extent by configuring the MAC ranges (if the hypervisor supports that) but at the price of greatly reducing the placement of your VMs. Also you may find multiple benefits of controlling the MAC ranges over letting the hypervisor to assign them randomly.

Cheers

Ruben

On Wed, Jan 18, 2012 at 8:52 PM, Shantanu Pavgi <pavgi at uab.edu<mailto:pavgi at uab.edu>> wrote:

I think most hypervisors can assign MAC address dynamically on their own. I haven't used Xen so I am not sure about it, but KVM and VMware ESXi can auto-generate MAC addresses. Also, the VMware ESXi has a separate range for manually (non-ESXi) assigned MAC addresses [1] [2].

See:
1. http://kb.vmware.com/kb/507
2. http://libvirt.org/drvesx.html#macaddresses

On Jan 17, 2012, at 10:50 AM, Javier Fontan wrote:

I was not aware of kvm assigning MAC addresses. If that setup suits
your needs then go for it, You should have no problem with it.

On Tue, Jan 17, 2012 at 5:24 PM, Shantanu Pavgi <pavgi at uab.edu<mailto:pavgi at uab.edu>> wrote:

Thanks for the reply Javier.

I was able to create a VM by specifying only network interface name in the NIC section. I left MAC address assignment over to the hypervisor (KVM) which assigns MAC address to a VM if it's not specified in the VM definition file. So in this case OpenNebula didn't have any knowledge of the MAC and IP address assigned to this VM. I am not sure whether this will impact OpenNebula's VM management functionality though. Any thoughts?

Following is an example VM definition. OpenNebula version: 3.0.

{{{
# Capacity section
NAME = ttylinux-01
MEMORY = 128
CPU = 1

# OS and Boot section
OS = [
 ARCH = i686,
 BOOT = hd ]

FEATURES = [ acpi = "no" ]

# Graphics I/O
GRAPHICS = [
 TYPE = "vnc",
 PORT = "-1",
 keymap = "en-us" ]

# Disk devices
DISK = [
 IMAGE_ID = "0" ]

# Network interface
NIC = [
  BRIDGE = br0 ]
}}}

--
Shantanu

On Jan 16, 2012, at 5:05 AM, Javier Fontan wrote:

Hello,

Even if the VM's wont get the IP's form OpenNebula the MAC address
must be generated. Internally MAC addresses are tied to Virtual
Network leases so a place in a Virtual Network is needed. Just add a
class B or C network and everything should work ok.

You can also manually generate the mac addresses and you wont need the
Virtual Network, in VM template:

NIC=[MAC="00:02:01:23:45:67", IP="10.0.0.1", BRIDGE="br0"]

But this is more cumbersome as you will need to manually generate
different mac addresses for every interface.

Bye

On Mon, Jan 16, 2012 at 1:50 AM, Shantanu Pavgi <pavgi at uab.edu<mailto:pavgi at uab.edu>> wrote:

I am not following how OpenNebula handles network configuration for the VMs. I am trying to create a virtual network using network config file as follows:
{{{
NAME = "Test Network"
TYPE = RANGED
BRIDGE = br0
PUBLIC=" yes"
}}}

In my test setup I have a DHCP server for IP address assignment. So I did not put NETWORK_ADDRESS and NETWORK_SIZE values, thinking OpenNebula doesn't need to know about it. However I got following error upon 'onvnet create' command.

{{{
[VirtualNetworkAllocate] Error allocating a new virtual network. No NETWORK_ADDRESS in template for Virtual Network.
}}}

I am not sure what values should I provide in a network definition file if IP address and MAC address assignment is not going to be handled by OpenNebula. How does OpenNebula use NETWORK_ADDRESS and NETWORK_SIZE values during VM deployment?

--
Thanks,
Shantanu
_______________________________________________
Users mailing list
Users at lists.opennebula.org<mailto:Users at lists.opennebula.org>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

--
Javier Fontán Muiños
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org<http://www.OpenNebula.org/> | jfontan at opennebula.org<mailto:jfontan at opennebula.org> | @OpenNebula
_______________________________________________
Users mailing list
Users at lists.opennebula.org<mailto:Users at lists.opennebula.org>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

--
Javier Fontán Muiños
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org<http://www.OpenNebula.org/> | jfontan at opennebula.org<mailto:jfontan at opennebula.org> | @OpenNebula

_______________________________________________
Users mailing list
Users at lists.opennebula.org<mailto:Users at lists.opennebula.org>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

--
Dr. Ruben Santiago Montero
Associate Professor (Profesor Titular), Complutense University of Madrid

URL: http://dsa-research.org/doku.php?id=people:ruben
Weblog: http://blog.dsa-research.org/?author=7
_______________________________________________
Users mailing list
Users at lists.opennebula.org<mailto:Users at lists.opennebula.org>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120121/d77c462d/attachment-0003.htm>