<div dir="ltr">Hey Thomas!<div><br></div><div>That's an amazing list! :-D</div><div><br></div><div>Okay, I'll drop by on IRC anytime soon to chat with you guys, tk for the invite!</div><div><br></div><div>About DHCPv6 support, yes, I agree with you, it can be postponed (in fact, I don't think I'll ever use it). Radvd should be enough for me.<br>
</div><div><br></div><div>I think that we need to start with the simplest configuration possible, that I think it is this one:</div><div><br></div><div><br></div><div>8- Provider Networking - upstream SLAAC support: <a href="https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac">https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac</a><div>
<br></div><div><br></div><div>Please, Collins, can you confirm this for us: is this above blueprint the easiest to achieve (or almost)?! If not, which one is closest to be ready for tests?!</div></div><div><br></div><div>
Nevertheless, from what I'm seeing, that this is, in fact, the simplest blueprint / topology we can start testing, so, I'm finishing a "Quick Guide" for our tests (more commits to it comming - cleanup). It perfect fits into the proposed blueprint topology, which is "upstream router" (no L3, no gre/vxlan tunnels, no Floating IPs, no NAT even for IPv4)...</div>
<div><br></div><div><br></div><div>Here it is:</div><div><br></div><div>Ultimate OpenStack IceHouse Guide - IPv6-Friednly: <a href="https://gist.github.com/tmartinx/9177697">https://gist.github.com/tmartinx/9177697</a></div>
<div><br></div><div><br></div><div>My current plan is, if you guys can read this page (not all of it) for a moment, at the step "5.2.1. Creating the Flat Neutron Network", I would like to do, basically this:</div>
<div><br></div><div><div>neutron subnet-create --ip-version 6 --tenant-id $ADMIN_TENANT_ID sharednet1 2001:db8:1:1::/64 --dns_nameservers list=true 2001:4860:4860::8844 2001:4860:4860::8888</div></div><div><br></div><div>
...Into that "Simple Flat Network" Right after applying the patch for "upstream SLAAC / ipv6-provider-nets-slaac" at the IceHouse lab I have, it is up and running now. You guys can easily replicated it with 3 KVM Virtual Machines (1 gateway (dual-stacked) / 1 controller / 1 compute).</div>
<div><br></div><div>BTW, which extra options for "subnet-create", the blueprint ipv6-provider-nets-slaac covers, if any?</div><div><br></div><div>"--ipv6_ra_mode XXX --ipv6_address_mode YYY" ?<br></div>
<div><br></div><div>Here at my lab, my "upstream SLAAC" already have radvd ready, IPv6 connectivity okay and etc, I think I have everything ready to start testing it.</div><div><br></div><div>Cheers!</div><div>
Thiago</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 11 April 2014 03:26, Thomas Goirand <span dir="ltr"><<a href="mailto:zigo@debian.org" target="_blank">zigo@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 04/08/2014 03:10 AM, Martinx - ジェームズ wrote:<br>
> Hi Thomas!<br>
><br>
> It will be a honor for me to join Debian OpenStack packaging team! I'm<br>
> in!! :-D<br>
><br>
> Listen, that "neutron-ipv6.patch" I have, doesn't apply against<br>
> "neutron-2014.1.rc1", here is it:<br>
><br>
> neutron-ipv6.patch: <a href="http://paste.openstack.org/show/74857/" target="_blank">http://paste.openstack.org/show/74857/</a><br>
><br>
> I generated it from the commands that Xuhan Peng told me to do, few<br>
> posts back, which are:<br>
><br>
> --<br>
> git fetch <a href="https://review.openstack.org/openstack/neutron" target="_blank">https://review.openstack.org/openstack/neutron</a><br>
> refs/changes/49/70649/15<br>
> git format-patch -1 --stdout FETCH_HEAD > neutron-ipv6.patch<br>
> --<br>
><br>
> But, as Collins said, even if the patch applies successfully against<br>
> neutron-2014.1.rc1 (or newer), it will not pass the tests, so, there is<br>
> still a lot of work to do, to enable Neutron with IPv6 but, I think we<br>
> can start working on this patches and start testing whatever is already<br>
> there (related to IPv6).<br>
><br>
> Best!<br>
> Thiago<br>
<br>
</div>Hi Thiago,<br>
<br>
It's my view that we'd better keep each patch separated, so that they<br>
can evolve over time, as they are accepted or fixed in<br>
<a href="http://review.openstack.org" target="_blank">review.openstack.org</a>. On the Debian packaging I do, each and every patch<br>
has to comply with the DEP3 patch header specifications [1].<br>
Specifically, I do insist that the "Origin:" field is set with the<br>
correct gerrit review URL, so that we can easily find out which patch<br>
comes from where. The "Last-Update" field is also important, so we know<br>
which version of the patch is in.<br>
<br>
Also, at eNovance, we are currently in the process of selecting which<br>
patch should get in, and which patch shouldn't. Currently, we are<br>
tracking the below patches:<br>
<br>
1. Support IPv6 SLAAC mode in dnsmasq<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-slaac" target="_blank">https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-slaac</a><br>
Patchset: Add support to DHCP agent for BP ipv6-two-attributes:<br>
<a href="https://review.openstack.org/#/c/70649/" target="_blank">https://review.openstack.org/#/c/70649/</a><br>
<br>
2. Bind dnsmasq in qrouter- namespace.<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/dnsmasq-bind-into-qrouter-namespace" target="_blank">https://blueprints.launchpad.net/neutron/+spec/dnsmasq-bind-into-qrouter-namespace</a><br>
Patchset: Add support to DHCP agent for BP ipv6-two-attributes:<br>
<a href="https://review.openstack.org/#/c/70649/" target="_blank">https://review.openstack.org/#/c/70649/</a><br>
<br>
3. IPv6 Feature Parity<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/ipv6-feature-parity" target="_blank">https://blueprints.launchpad.net/neutron/+spec/ipv6-feature-parity</a><br>
Definition: Superseded.<br>
<br>
4. Two Attributes Proposal to Control IPv6 RA Announcement and Address<br>
Assignment<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/ipv6-two-attributes" target="_blank">https://blueprints.launchpad.net/neutron/+spec/ipv6-two-attributes</a><br>
Patchset: Create new IPv6 attributes for Subnets.<br>
<a href="https://review.openstack.org/#/c/52983/" target="_blank">https://review.openstack.org/#/c/52983/</a><br>
Patchset: Add support to DHCP agent for BP ipv6-two-attributes.<br>
<a href="https://review.openstack.org/70649" target="_blank">https://review.openstack.org/70649</a><br>
Patchset: Calculate stateless IPv6 address.<br>
<a href="https://review.openstack.org/56184" target="_blank">https://review.openstack.org/56184</a><br>
Patchset: Permit ICMPv6 RAs only from known routers.<br>
<a href="https://review.openstack.org/#/c/72252/" target="_blank">https://review.openstack.org/#/c/72252/</a><br>
<br>
5. Support IPv6 DHCPv6 Stateless mode in dnsmasq<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateless" target="_blank">https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateless</a><br>
Patchset: Add support to DHCP agent for BP ipv6-two-attributes:<br>
<a href="https://review.openstack.org/#/c/70649/" target="_blank">https://review.openstack.org/#/c/70649/</a><br>
<br>
6. Support IPv6 DHCPv6 Stateful mode in dnsmasq<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateful" target="_blank">https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateful</a><br>
Patchset: Add support to DHCP agent for BP ipv6-two-attributes:<br>
<a href="https://review.openstack.org/#/c/70649/" target="_blank">https://review.openstack.org/#/c/70649/</a><br>
<br>
7. Support IPv6 DHCPv6 Relay Agent<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-relay-agent" target="_blank">https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-relay-agent</a><br>
Definition: Drafting.<br>
<br>
8. Provider Networking - upstream SLAAC support<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac" target="_blank">https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac</a><br>
Patchset: Ensure that that all fixed ips for a port belong to a<br>
subnet using DHCP. <a href="https://review.openstack.org/#/c/64578/" target="_blank">https://review.openstack.org/#/c/64578/</a><br>
<br>
9. Store both LLA and GUA on router interface port<br>
<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/ipv6-lla-gua-router-interface" target="_blank">https://blueprints.launchpad.net/neutron/+spec/ipv6-lla-gua-router-interface</a><br>
Definition: New<br>
<br>
10. Add RADVD to router namespaces to serve ipv6 RAs when required<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra" target="_blank">https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra</a><br>
Definition: New<br>
<br>
11. Allow multiple subnets on gateway port for router<br>
<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/allow-multiple-subnets-on-gateway-port" target="_blank">https://blueprints.launchpad.net/neutron/+spec/allow-multiple-subnets-on-gateway-port</a><br>
Patchset: Add support for dual-stack (IPv4 and IPv6) on external<br>
gateway. <a href="https://review.openstack.org/#/c/77471/" target="_blank">https://review.openstack.org/#/c/77471/</a><br>
Definition: Review<br>
<br>
It is my own personal view that we shouldn't care about DHCPv6, and that<br>
only RADVD is important, though maybe my colleagues will have a<br>
different view. Also, it is very important that we only use patches that<br>
have a reasonable chance to be merged, or at least for which the<br>
functionality will for sure get in Juno.<br>
<br>
The current plan is that my colleagues (sridhar and Sylvain Afchain,<br>
which are both reacheable on IRC as SridharG and safchain in<br>
#openstack-neutron) will work on grabbing each patch, reviewing it and<br>
evaluating it, then rewrite the patch header, and finally send me a<br>
patchset to apply on top of Icehouse. It's much better that it is them,<br>
rather than me, that works on that, as they are specialists of Neutron,<br>
while I'm a specialist of Debian packaging.<br>
<br>
Your input on this process is very much welcome here. Your thoughts?<br>
<br>
Cheers,<br>
<br>
Thomas Goirand (zigo)<br>
<br>
[1] <a href="http://dep.debian.net/deps/dep3/" target="_blank">http://dep.debian.net/deps/dep3/</a><br>
<br>
</blockquote></div><br></div>