[one-users] More ipv6 network questions
Ruben S. Montero
rsmontero at opennebula.org
Mon Mar 31 03:28:12 PDT 2014
Hi Steven,
This is a limitation of the current model. We use the MAC address to
generate the host id using the EUI64. With the 64 bits from the host plus
the prefixes we derive the IPv6 addresses. That's the reason for not
storing the link local address, it is just derived from the MAC as in
linux. Basically it is assuming a stateless auto-configuration model.
Ranged leases only accepts MAC and IP. Just filled an issue to implement
this [1]. Till this is implemented the workaround is to set the IPv6
hardcoded in the context of the VM template.
Cheers
Ruben
[1] http://dev.opennebula.org/issues/2818
On Wed, Mar 26, 2014 at 11:04 PM, Steven Timm <timm at fnal.gov> wrote:
>
>
> A followup--I did find an example in the documentation but it is only for
> "RANGED" IPv6 network. I need a FIXED IPv6 network.
>
> I saw that when I set an IP6_GLOBAL PREFIX in the network
> file it would then append the ipv6-ified mac address of the
> machine and construct an IP6_GLOBAL for me. But that's not what I want.
>
> Would like to do something like this:
> LEASES = [ IP="131.225.41.182", MAC="54:52:00:02:0B:01",
> IP6_GLOBAL="2001:400:2410:29::182" ]
> LEASES = [ IP="131.225.41.183", MAC="54:52:00:02:0B:02",
> IP6_GLOBAL="2001:400:2410:29::183"]
> LEASES = [ IP="131.225.41.184", MAC="54:52:00:02:0B:03",
> IP6_GLOBAL="2001:400:2410:29::184" ]
> LEASES = [ IP="131.225.41.185", MAC="54:52:00:02:0B:04",
> IP6_GLOBAL="2001:400:2410:29::185" ]
> LEASES = [ IP="131.225.41.186", MAC="54:52:00:02:0B:05",
> IP6_GLOBAL="2001:400:2410:29::186" ]
>
> But this doesn't work. the IP6_GLOBAL in the LEASES field is ignored.
>
> Is there any IPV6-related field that is accepted in the LEASES
> field of a fixed-network network template? This is of some urgency.
> (I promised my users who depend on ipv6 cloud vm's I would have them
> up this morning local time and it is now quitting time today).
>
> Steve
>
>
>
> On Wed, 26 Mar 2014, Steven Timm wrote:
>
>
>> Below is the network template that I used to
>> successfully create the IPV4 side of a dual stack ipv4/ipv6 network
>> in one4.4.
>>
>>
>> -bash-4.1$ cat static-ipv6-net
>> NAME = "Static_IPV6_Public"
>> TYPE = FIXED
>>
>> #Now we'll use the cluster private network (physical)
>> BRIDGE = br0
>> DNS = 131.225.0.254
>> GATEWAY = 131.225.41.200
>> NETWORK_MASK = 255.255.255.128
>> LEASES = [ IP="131.225.41.132", MAC="00:16:3E:06:01:01" ]
>>
>> ------------------------------------------
>>
>> and here's what I get back:
>>
>> -bash-4.1$ onevnet show 1
>> VIRTUAL NETWORK 1 INFORMATION
>> ID : 1
>> NAME : Static_IPV6_Public
>> USER : oneadmin
>> GROUP : oneadmin
>> CLUSTER : -
>> TYPE : FIXED
>> BRIDGE : br0
>> VLAN : No
>> USED LEASES : 0
>>
>> PERMISSIONS
>> OWNER : um-
>> GROUP : ---
>> OTHER : ---
>>
>> VIRTUAL NETWORK TEMPLATE
>> DNS="131.225.0.254"
>> GATEWAY="131.225.41.200"
>> NETWORK_MASK="255.255.255.128"
>>
>> FREE LEASES
>> LEASE=[ MAC="00:16:3e:06:01:01", IP="131.225.41.132",
>> IP6_LINK="fe80::216:3eff:fe06:101", USED="0", VID="-1" ]
>>
>> VIRTUAL MACHINES
>>
>> ID USER GROUP NAME STAT UCPU UMEM HOST TIME
>>
>> ------------------------------------------------------------
>> I have several questions:
>>
>> 1) Does the OpenNebula head node also have to have access to the
>> IPv6 network too, or just the VM hosts?
>>
>> 2) Is there any way to specify on a host by host basis
>> the IPV6 address as well as the IPV4 address? I.e. for
>> this host fgt1x1.fnal.gov IPV4 is 131.225.41.132 and
>> IPV6 Global address is 2001:400:2410:29::132
>>
>> It's puzzling because in the "leases" database table there
>> is only room for id, ipv4 address, and body.
>> the "IP6_LINK" field above is not anywhere stored in the database
>> and yet it shows.
>>
>> 3) Do the contextualization rpms as distributed with ONE4.0 and greater
>> handle the
>> process of setting up IPV6 addresses as part of contextualization?
>> If so, what fields should we put in the CONTEXT section
>> to set these values?
>>
>> Any help is appreciated as getting the ipv6 VM's up and running
>> is of some urgency. Right now I am forced to configure
>> the ipv6 addresses by hand once the VM is up.
>>
>> Steve Timm
>>
>> ------------------------------------------------------------------
>> Steven C. Timm, Ph.D (630) 840-8525
>> timm at fnal.gov http://home.fnal.gov/~timm/
>> Fermilab Scientific Computing Division, Scientific Computing Services
>> Quad.
>> Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing
>>
>>
> ------------------------------------------------------------------
> Steven C. Timm, Ph.D (630) 840-8525
> timm at fnal.gov http://home.fnal.gov/~timm/
> Fermilab Scientific Computing Division, Scientific Computing Services Quad.
> Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
> --
> <http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
> --
> Ruben S. Montero, PhD
> Project co-Lead and Chief Architect<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
> OpenNebula - Flexible Enterprise Cloud Made Simple
> <http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
> www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140331/993f8608/attachment-0002.htm>
More information about the Users
mailing list