Page MenuHomePhabricator

Some Traffic clusters apparently do not support IPv6
Open, LowPublic

Description

Greetings!

During importation of DNS into Netbox as part of the transition to automation, we discovered some clusters do not have IPv6 DNS entries, which we interpreted as intentional (given that this was the mechanism used to prevent potential clients from accessing the IPv6 interfaces on the machine, if a given service did not support IPv6), and prevented from being imported into automation.

We are now triaging these clusters for their potential at supporting IPv6 in the future, so below are hosts which were left out of IPv6 DNS which we think that your team is responsible for. If you could take some time to put any information you have about supporting IPv6 on these clusters, specific plans for doing so, or if it will not in the forseeable future be possible to do so, it would be greatly appreciated!

If any of these machines don't belong to you let us know on this ticket or the parent task (T253173), thanks!

  • lvs[2007-2010].codfw.wmnet
  • lvs[1013-1016].eqiad.wmnet
  • lvs[4005-4007].ulsfo.wmnet

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Joe triaged this task as Low priority.Jan 5 2021, 7:52 AM
Joe added a subscriber: Joe.

I will let the traffic folks answer as well, but first of all I think you should clarify a bit better the wording of the task. For instance, I struggle to understand what "some clusters do not have IPv6 DNS entries" means in this context. Specifically, you're naming servers in eqiad, codfw and ulsfo, and a quick query returns:

$ for dc in eqiad codfw ulsfo; do N="text-lb.$dc.wikimedia.org"; IP6=$(dig +short -t AAAA $N); echo $N $IP6; done
text-lb.eqiad.wikimedia.org 2620:0:861:ed1a::1
text-lb.codfw.wikimedia.org 2620:0:860:ed1a::1
text-lb.ulsfo.wikimedia.org 2620:0:863:ed1a::1
$ for dc in eqiad codfw ulsfo; do N="upload-lb.$dc.wikimedia.org"; IP6=$(dig +short -t AAAA $N); echo $N $IP6; done
upload-lb.eqiad.wikimedia.org 2620:0:861:ed1a::2:b
upload-lb.codfw.wikimedia.org 2620:0:860:ed1a::2:b
upload-lb.ulsfo.wikimedia.org 2620:0:863:ed1a::2:b

which are the public IPV6 addresses to reach all of our services.

So my guess is you're just not seeing an IPv6 address associated with the aforementioned load balancers?

(Also setting the priority to low as this is not an ongoing production problem, correct me if I'm wrong).

The point of the project is to get as many hosts to have an IPv6 address (and, obviously, to be functional on that address) as we can, and, in general, for it to be default to have IPv6 addresses in DNS. If it's not appropriate for a particular cluster, that's a valid outcome.

In this case the load balancer servers listed above indeed do not have IPv6 DNS. This ticket requests any information needed to add these hosts's IPv6 addresses to our DNS or to prompt the actions required to do so.

The point of the project is to get as many hosts to have an IPv6 address (and, obviously, to be functional on that address) as we can, and, in general, for it to be default to have IPv6 addresses in DNS. If it's not appropriate for a particular cluster, that's a valid outcome.

In this case the load balancer servers listed above indeed do not have IPv6 DNS. This ticket requests any information needed to add these hosts's IPv6 addresses to our DNS or to prompt the actions required to do so.

Just to be extra clear, I mean host addresses throughout this.

BBlack added a subscriber: BBlack.

The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all tickets that aren't are neither part of our current planned work nor clearly a recent, higher-priority emergent issue. This is simply one step in a larger task cleanup effort. Further triage of these tickets (and especially, organizing future potential project ideas from them into a new medium) will occur afterwards! For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!