Page MenuHomePhabricator
Create Task
Maniphest T305834

Cloud VPS: drop wmflabs names from profile::resolving::domain_search
Open, Stalled, MediumPublic
Actions

Description

This is the current value of profile::resolving::domain_search:

profile::resolving::domain_search:
  - "%{facts.networking.domain}"
  - "%{::wmcs_project}.eqiad1.wikimedia.cloud"
  - "%{::wmcs_project}.eqiad.wmflabs"
  - "eqiad.wmflabs"

We should eventually drop the legacy .wmflabs domains from there.

%{::labsproject}.eqiad.wmflabs should be simple to drop as everything found with it should be found under the %{::labsproject}.eqiad1.wikimedia.cloud domain already. eqiad.wmflabs might still be needed for some cross-domain lookups, not sure.

Related Objects
Search...

StatusSubtypeAssignedTask
 StalledNoneT305834 Cloud VPS: drop wmflabs names from profile::resolving::domain_search
 ResolvedaborreroT277653 Toolforge: add Debian Buster to the grid and eliminate Debian Stretch
 ResolvedaborreroT277866 cloud-init: figure out how to change /etc/hosts from cloud-init/vendordata
 ResolvedaborreroT278232 Toolforge: figure out how to work with the new domain in the grid
 ResolvedaborreroT278748 Toolforge: introduce support for selecting grid queue release
 ResolvedaborreroT282972 "--release is not implemented for --backend=kubernetes" with latest tools-webservice from Git
 ResolvedtaaviT288961 /usr/local/bin/webservice:109: DeprecationWarning: dist() and linux_distribution() functions are deprecated in Python 3.5
 ResolvedaborreroT300501 Toolforge grid: uwsgi in buster fails to load python3 venvs
 ResolvedtaaviT280037 Toolforge: set up monitoring tooling for stretch deprecation
 DuplicateNoneT280252 Toolforge Buster bastion no longer tab completes become command
 ResolvedtaaviT284767 Toolforge: migrate cron servers to Debian Buster
 DeclinedNoneT298089 Sort out Mono repositories for the buster grid
 ResolvedaborreroT298948 Toolforge grid deployment/management automation
 DeclinedNoneT300032 spicerack: introduce GridEngine controller
 ResolvedaborreroT301665 Toolforge jobs framework: create documentation on wikitech
 ResolvedtaaviT309525 Toolforge: Create a cookbook to decomission a SGE node
 ResolvedtaaviT309732 New SGE nodes can't talk to the grid engine master
 Resolved• nskaggsT309821 Buster webservice grid went BOOM!
 DeclinedtaaviT309902 Tiny swap on many grid nodes

Event Timeline

taavi created this task.Apr 11 2022, 11:13 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 11 2022, 11:13 AM
aborrero changed the task status from Open to Stalled.Apr 11 2022, 11:22 AM
aborrero triaged this task as Medium priority.
aborrero moved this task from Inbox to Blocked on the cloud-services-team (Kanban) board.
aborrero subscribed.

This is blocked on T277653: Toolforge: add Debian Buster to the grid and eliminate Debian Stretch, the old Debian Stretch grid relies on resolving the .eqiad.wmflabs names.

taavi added a subtask: T277653: Toolforge: add Debian Buster to the grid and eliminate Debian Stretch.Apr 11 2022, 11:45 AM
taavi closed subtask T277653: Toolforge: add Debian Buster to the grid and eliminate Debian Stretch as Resolved.Jun 27 2022, 6:18 PM
fnegri edited projects, added cloud-services-team; removed cloud-services-team (Kanban).Jan 18 2023, 7:22 PM
fnegri moved this task from Kanban to Blocked on the cloud-services-team board.
taavi updated the task description. (Show Details)Jul 6 2023, 1:32 PM
taavi added a comment.Jul 6 2023, 1:40 PM

The Stretch grid is gone. However, there are two potential issues I can see:

  • Cross-project lookups in eqiad.wmflabs.
  • There are also a few service name aliases that might cause issues:
taavi@cloudcontrol1007 ~ $ os record list 114f1333-c2c1-44d3-beb4-ebed1a91742b --sudo-project-id noauth-project --type CNAME
+--------------------------------------+----------------------------------+-------+-----------------------------------------+--------+--------+
| id                                   | name                             | type  | records                                 | status | action |
+--------------------------------------+----------------------------------+-------+-----------------------------------------+--------+--------+
| 4f5412e9-3872-46e1-8065-91d1fc253951 | tools-redis.tools.eqiad.wmflabs. | CNAME | redis.svc.tools.eqiad1.wikimedia.cloud. | ACTIVE | NONE   |
| 67d7a5c6-f1be-4f37-afab-e1034d26a4d2 | tools-redis.eqiad.wmflabs.       | CNAME | redis.svc.tools.eqiad1.wikimedia.cloud. | ACTIVE | NONE   |
| f5f147bc-3828-4f75-b187-cf560b8bff36 | tools-db.tools.eqiad.wmflabs.    | CNAME | tools.db.svc.eqiad.wmflabs.             | ACTIVE | NONE   |
+--------------------------------------+----------------------------------+-------+-----------------------------------------+--------+--------+

In theory tools-redis.tools.eqiad.wmflabs is fine since clients will just use the tools-redis.eqiad.wmflabs. However there's no such name to fallback on tools-db.tools.eqiad.wmflabs so to drop "%{::wmcs_project}.eqiad.wmflabs safely we would need to create a matching record in eqiad.wmflabs.

It'd also be nice to know how much these (and other deprecated DNS names) are being used and if we could drop them.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits