Last modified: 2014-09-24 23:41:44 UTC
Update the open stack to version which supports the ipv6 and enable it
Btw I know we discussed it and that it's not so simple, but I just wanted to keep it here so that we don't forget
And it had better occur soon, so like everything else we can test IPv6 in a Labs setup.
There's only a small amount of things we can reasonably test in Labs using IPv6 right now. LVS doesn't work in Labs yet, due to security settings in libvirt, and because of networking difficulties, so we can at best test MediaWiki, which the devs assure us works properly. We don't need to upgrade nova to add IPv6, we need to figure out how to modify its network database, since nova assumes you create an IPv6 network at the same time as the IPv4 one.
Well, some on-wiki scripts need testing and development for IPv6. http://meta.wikimedia.org/wiki/IPv6_initiative
(adjusting summary so searches on 'ipv6' will turn this up)
Added Leslie Carr since she is the network guru
how is it possible that on some projects it works? is it enabled or not
It doesn't. It's a MediaWiki hack that is acting like it's enabled.
OK, anyway, production is going to use ipv6 soon, why we can't have that on labs... do we still run old version of sw?
We don't have it enabled in openstack yet, and enabling it isn't straightforward because we created our networks before ipv6 support was available in openstack. This is on our roadmap.
The Roadmap used to contain something for Q2 like adding a second zone in Eqiad, which Ryan told me (on IRC) would be the deployment.
See bug 39781 comment 2?
Adding 58791. Toolserver is dual stack, labs still lives in the 1990's.
We'll be enabling ipv6 during the move to eqiad, but depending on OpenStack support may keep it firewalled. Last time I checked the support for this in neutron is poor.
Hi folks! Could you explain for which tools it's a blocker not to have ipv6?
(In reply to comment #15) > Hi folks! > Could you explain for which tools it's a blocker not to have ipv6? I don't think anyone claimed any such tools existed...
Ok, then I propose not to insist on ipv6 for Labs for the moment. We don't need features just because toolserver has them - we need features that tools depend on. Giving lower priority. Please give reasons if you insist/change it back.
(In reply to comment #17) > Ok, then I propose not to insist on ipv6 for Labs for the moment. I suggest you read the overview in the page linked by Jasper in comment 4 above.
Allen, I have to precise what I meant. I am trying to prioritize what is crucial *just* for Tool Labs to replace the toolserver. Features that are absolutely needed for toolserver tools to migrate. As Maarten brought in that the toolserver has ipv6, I was wondering if there are tools that can't migrate without ipv6. If this is not the case, ipv6 is no blocker for toolserver migration. I wasn't meaning that ipv6 is unimportant for the whole of Labs, sorry!
(removing as blocker to "missing feature" tracking bug; this does not block any tool migration)
http://permalink.gmane.org/gmane.org.wikimedia.labs/2651: | > Of particular interest would be to hear if there are plans to IPv6 | > enable the labs web proxy server and start publishing AAAA records for | > the dns aliases one can register in wikitech? | Our current networking stack in Labs currently makes this overcomplicated. | But there is good news: as we roll out to our new datacenter in Dallas, | we plan on having Openstack there use Neutron, which should allow us to | deploy IPv6 as well, so at the very least Dallas instances should be | IPv6 capable. | After that, upgrading Ashburn to use the same networking setup as Dallas | becomes something that can be planned for.
