Page MenuHomePhabricator

Review *.tools.wmflabs.org usage in Toolforge infrastructure components
Closed, InvalidPublic

Description

Document where *.tools.wmflabs.org is used vs *.tools.eqiad.wmflabs

Reach some consensus of how each should be used and if the cluster can be simplified to use just one.

Explain why an external domain is needed for internal cluster services.

Event Timeline

I assume this is for when you want to set up a 'service' DNS name rather than one for an individual host, as projectadmins cannot modify the eqiad.wmflabs zone.

GTirloni renamed this task from Review *.tools.wmflabs.org usage in Toolforge to Review *.tools.wmflabs.org usage in Toolforge infrastructure components.Dec 5 2018, 2:18 PM

@Krenair I should clarify I mean usage of tools.wmflabs.org in basic infrastructure configuration (e.g. Kubernetes) as opposed to usage by the projects. Sorry.

Yeah I don't think that changes it. You can't just add stuff to eqiad.wmflabs as a project admin (it requires cloudadmin intervention, the space set up for manual stuff like this is .svc.eqiad.wmflabs anyway), so you're restricted to individual servers' A records under tools.eqiad.wmflabs.

GTirloni triaged this task as Low priority.