Open Stack

In fact, neutron accepted the following command:

---
root at controller:~# neutron subnet-create --ip-version 6 --disable-dhcp
--tenant-id 5e0106fa81104c5cbe21e1ccc9eb1a36 sharednet1
2001:1291:2bf:fffb::/64
Created a new subnet:
+------------------+-------------------------------------------------------------------------------------+
| Field            | Value
                              |
+------------------+-------------------------------------------------------------------------------------+
| allocation_pools | {"start": "2001:1291:2bf:fffb::2", "end":
"2001:1291:2bf:fffb:ffff:ffff:ffff:fffe"} |
| cidr             | 2001:1291:2bf:fffb::/64
                              |
| dns_nameservers  |
                              |
| enable_dhcp      | False
                              |
| gateway_ip       | 2001:1291:2bf:fffb::1
                              |
| host_routes      |
                              |
| id               | 8685c917-e8df-4741-987c-6a531dca9fcd
                             |
| ip_version       | 6
                              |
| name             |
                              |
| network_id       | 17cda0fb-a59b-4a7e-9d96-76d0670bc95c
                             |
| tenant_id        | 5e0106fa81104c5cbe21e1ccc9eb1a36
                             |
+------------------+-------------------------------------------------------------------------------------+
---

Where "gateway_ip 2001:1291:2bf:fffb::1" is my "upstream SLAAC" router
(radvd stopped for now).

Diving: I think I'll put my OVS bridge "br-eth0" (bridge_mappings =
physnet1:br-eth0) on top of a VLAN but, I'll not tell OpenStack to use
"vlan", I'll keep using "flat" but, on top of a "hidden" vlan... eheh   :-P

I'll keep testing to see how far I can go...    :-)

Cheers!


On 12 April 2014 00:42, Martinx - ジェームズ <thiagocmartinsc at gmail.com> wrote:

> Hey guys!
>
> My OpenStack Instance have IPv6 connectivity! Using ML2 / Simple Flat
> Network... For the first time ever! Look:
>
> ---
> administrative at controller:~$ nova boot --image
> 70f335e3-798b-4031-9773-a640970a8bdf --key-name Key trusty-1
>
> administrative at controller:~$ ssh -i ~/test.pem ubuntu at 10.33.14.21
>
> ubuntu at trusty-1:~$ sudo ip -6 a a 2001:1291:2bf:fffb::300/64 dev eth0
>
> ubuntu at trusty-1:~$ sudo ip -6 r a default via 2001:1291:2bf:fffb::1
>
> ubuntu at trusty-1:~$ ping6 -c 1 google.com
>
> PING google.com(2800:3f0:4004:801::1000) 56 data bytes
> 64 bytes from 2800:3f0:4004:801::1000: icmp_seq=1 ttl=54 time=55.1 ms
>
> --- google.com ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 55.121/55.121/55.121/0.000 ms
>
> -
> # From my Laptop (and from another IPv6 block):
> testuser at macbuntu:~$ telnet 2001:1291:2bf:fffb::300 22
> Trying 2001:1291:2bf:fffb::300...
> Connected to 2001:1291:2bf:fffb::300.
> Escape character is '^]'.
> SSH-2.0-OpenSSH_6.6p1 Ubuntu-2
> ---
>
> But, OpenStack / Neutron isn't aware of that fixed IPv6 (
> 2001:1291:2bf:fffb::300) I just configured within the trusty-1 Instance,
> so, I think we just need:
>
> - Blueprint ipv6-provider-nets-slaac ready;
> - Start radvd on upstream router (2001:1291:2bf:fffb::1).
>
> Am I right?!
>
> In fact, apparently, Security Groups is also working! I can ssh into
> "trusty-1" through IPv6 right now, but can't access port 80 of it (it is
> closed buy 22 is open to the world)...
>
> Maybe it will also work with VLANs...
>
> BTW, I just realized that both the physical servers, controllers, networks
> and compute nodes and etc, can be installed under a single IPv6 /64 subnet!
> Since the openstack will random generate the MAC address (plus SLAAC),
> IPv6s will never conflict.
>
> Best!
> Thiago
>
>
> On 12 April 2014 00:09, Thomas Goirand <zigo at debian.org> wrote:
>
>> On 04/11/2014 10:52 PM, Collins, Sean wrote:
>> > Many of those patches are stale - please join us in the subteam IRC
>> > meeting if you wish to coordinate development of IPv6 features, so that
>> > we can focus on updating them and getting them merged. At this point
>> > simply applying them to the Icehouse tree is not enough.
>>
>> When and where is the next meeting?
>>
>> Thomas
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140412/160228df/attachment.html>