Open Stack

Hey Thomas!

That's an amazing list!   :-D

Okay, I'll drop by on IRC anytime soon to chat with you guys, tk for the
invite!

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.

I think that we need to start with the simplest configuration possible,
that I think it is this one:


8- Provider Networking - upstream SLAAC support:
https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac


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?!

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)...


Here it is:

Ultimate OpenStack IceHouse Guide - IPv6-Friednly:
https://gist.github.com/tmartinx/9177697


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:

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

...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).

BTW, which extra options for "subnet-create", the blueprint
ipv6-provider-nets-slaac covers, if any?

"--ipv6_ra_mode XXX --ipv6_address_mode YYY" ?

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.

Cheers!
Thiago


On 11 April 2014 03:26, Thomas Goirand <zigo at debian.org> wrote:

> On 04/08/2014 03:10 AM, Martinx - ¥¸¥§©`¥à¥º wrote:
> > Hi Thomas!
> >
> > It will be a honor for me to join Debian OpenStack packaging team! I'm
> > in!!     :-D
> >
> > Listen, that "neutron-ipv6.patch" I have, doesn't apply against
> > "neutron-2014.1.rc1", here is it:
> >
> > neutron-ipv6.patch: http://paste.openstack.org/show/74857/
> >
> > I generated it from the commands that Xuhan Peng told me to do, few
> > posts back, which are:
> >
> > --
> > git fetch https://review.openstack.org/openstack/neutron
> > refs/changes/49/70649/15
> > git format-patch -1 --stdout FETCH_HEAD > neutron-ipv6.patch
> > --
> >
> > But, as Collins said, even if the patch applies successfully against
> > neutron-2014.1.rc1 (or newer), it will not pass the tests, so, there is
> > still a lot of work to do, to enable Neutron with IPv6 but, I think we
> > can start working on this patches and start testing whatever is already
> > there (related to IPv6).
> >
> > Best!
> > Thiago
>
> Hi Thiago,
>
> It's my view that we'd better keep each patch separated, so that they
> can evolve over time, as they are accepted or fixed in
> review.openstack.org. On the Debian packaging I do, each and every patch
> has to comply with the DEP3 patch header specifications [1].
> Specifically, I do insist that the "Origin:" field is set with the
> correct gerrit review URL, so that we can easily find out which patch
> comes from where. The "Last-Update" field is also important, so we know
> which version of the patch is in.
>
> Also, at eNovance, we are currently in the process of selecting which
> patch should get in, and which patch shouldn't. Currently, we are
> tracking the below patches:
>
> 1. Support IPv6 SLAAC mode in dnsmasq
> https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-slaac
>    Patchset: Add support to DHCP agent for BP ipv6-two-attributes:
> https://review.openstack.org/#/c/70649/
>
> 2. Bind dnsmasq in qrouter- namespace.
>
> https://blueprints.launchpad.net/neutron/+spec/dnsmasq-bind-into-qrouter-namespace
>    Patchset: Add support to DHCP agent for BP ipv6-two-attributes:
> https://review.openstack.org/#/c/70649/
>
> 3. IPv6 Feature Parity
> https://blueprints.launchpad.net/neutron/+spec/ipv6-feature-parity
>    Definition: Superseded.
>
> 4. Two Attributes Proposal to Control IPv6 RA Announcement and Address
> Assignment
>    https://blueprints.launchpad.net/neutron/+spec/ipv6-two-attributes
>    Patchset: Create new IPv6 attributes for Subnets.
> https://review.openstack.org/#/c/52983/
>    Patchset: Add support to DHCP agent for BP ipv6-two-attributes.
> https://review.openstack.org/70649
>    Patchset: Calculate stateless IPv6 address.
> https://review.openstack.org/56184
>    Patchset: Permit ICMPv6 RAs only from known routers.
> https://review.openstack.org/#/c/72252/
>
> 5. Support IPv6 DHCPv6 Stateless mode in dnsmasq
>
> https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateless
>    Patchset: Add support to DHCP agent for BP ipv6-two-attributes:
> https://review.openstack.org/#/c/70649/
>
> 6. Support IPv6 DHCPv6 Stateful mode in dnsmasq
> https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateful
>    Patchset: Add support to DHCP agent for BP ipv6-two-attributes:
> https://review.openstack.org/#/c/70649/
>
> 7. Support IPv6 DHCPv6 Relay Agent
>
> https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-relay-agent
>    Definition: Drafting.
>
> 8. Provider Networking - upstream SLAAC support
> https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac
>    Patchset: Ensure that that all fixed ips for a port belong to a
> subnet using DHCP. https://review.openstack.org/#/c/64578/
>
> 9. Store both LLA and GUA on router interface port
>
>
> https://blueprints.launchpad.net/neutron/+spec/ipv6-lla-gua-router-interface
>    Definition: New
>
> 10. Add RADVD to router namespaces to serve ipv6 RAs when required
>     https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra
>     Definition: New
>
> 11. Allow multiple subnets on gateway port for router
>
>
> https://blueprints.launchpad.net/neutron/+spec/allow-multiple-subnets-on-gateway-port
>     Patchset: Add support for dual-stack (IPv4 and IPv6) on external
> gateway. https://review.openstack.org/#/c/77471/
>     Definition: Review
>
> It is my own personal view that we shouldn't care about DHCPv6, and that
> only RADVD is important, though maybe my colleagues will have a
> different view. Also, it is very important that we only use patches that
> have a reasonable chance to be merged, or at least for which the
> functionality will for sure get in Juno.
>
> The current plan is that my colleagues (sridhar and Sylvain Afchain,
> which are both reacheable on IRC as SridharG and safchain in
> #openstack-neutron) will work on grabbing each patch, reviewing it and
> evaluating it, then rewrite the patch header, and finally send me a
> patchset to apply on top of Icehouse. It's much better that it is them,
> rather than me, that works on that, as they are specialists of Neutron,
> while I'm a specialist of Debian packaging.
>
> Your input on this process is very much welcome here. Your thoughts?
>
> Cheers,
>
> Thomas Goirand (zigo)
>
> [1] http://dep.debian.net/deps/dep3/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140412/9f33ef4f/attachment.html>