Page MenuHomePhabricator

Some Machine Learning clusters do not support IPv6
Closed, DeclinedPublic

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!

  • ores[2001-2009].codfw.wmnet
  • ores[1001-1009].eqiad.wmnet
  • oresrdb2002.codfw.wmnet
  • oresrdb[1001-1002].eqiad.wmnet

Event Timeline

crusnov triaged this task as Medium priority.Jan 4 2021, 6:38 PM

@akosiaris does this mean we need to upgrade ores hosts to buster?

@akosiaris does this mean we need to upgrade ores hosts to buster?

No, most definitely not. If we want, we can add IPv6 to those nodes as they are. But given there is no urgency for this and the fact the cluster in in maintenance mode pending replacement with Lift Wing, I 'd say we don't need to, we would just be wasting time on infrastructure that will be decommissioned. @crusnov, per your commet in the task, I am setting this as Declined for the reasons above.

Note that oresrdb2002.codfw.wmnet and oresrdb[1001-1002].eqiad.wmnet don't exist anymore. They have been removed from the infrastructure, see T254240 and T254238.