Page MenuHomePhabricator

Determine usefulness of questionable hosts found in 2025-02-06 audit
Closed, ResolvedPublic

Description

@bd808 did an audit of the VMs in the deployment-prep project on 2025-02-06. That audit produced https://etherpad.wikimedia.org/p/what-services-are-in-deployment-prep and updated https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/Help#Infrastructure

The questionable instances found were:

Event Timeline

bd808 changed the task status from Open to In Progress.Feb 7 2025, 12:40 AM
bd808 claimed this task.
bd808 triaged this task as Medium priority.

Mentioned in SAL (#wikimedia-releng) [2025-02-07T00:42:36Z] <bd808> Shutoff deployment-parsoid14 to see if anything breaks/anyone yells (T385849)

Mentioned in SAL (#wikimedia-releng) [2025-02-07T00:42:36Z] <bd808> Shutoff deployment-parsoid14 to see if anything breaks/anyone yells (T385849)

https://simple.wikipedia.beta.wmflabs.org/w/index.php?title=User:Bd808/Sandbox&oldid=3289437 worked, so very likely it is an unused host other than being a scap target and having various stale service names pointed at it.

Change #1117997 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):

[operations/puppet@production] deployment-prep: Remove parsoid things from hiera

https://gerrit.wikimedia.org/r/1117997

deployment-bastion.deployment-prep.eqiad1.wikimedia.cloud is not needed. The system has been shut down and can be removed at any time

Regarding: deployment-parsoid14: parsoid-external-ci-access.beta.wmflabs.org points to it. Have we verified nothing in CI is talking to it nowadays?

Regarding: deployment-parsoid14: parsoid-external-ci-access.beta.wmflabs.org points to it. Have we verified nothing in CI is talking to it nowadays?

No, but this is why I turned the instance off rather than rushing to delete it. If that service name is found to be in use we can probably point it at another MediaWiki instance in deployment-prep since there was nothing but normal MediaWiki running on the instance.

deployment-alert01 can be binned :-) was one day going to be an alertmanager host iirc

It has been 2 weeks since I shutdown deployment-parsoid14 and nobody has turned it back on, so I think I can safely remove all 3 servers next week.

Mentioned in SAL (#wikimedia-releng) [2025-02-28T16:36:55Z] <bd808> Deleted deployment-bastion.deployment-prep.eqiad1.wikimedia.cloud (T385849)

Mentioned in SAL (#wikimedia-releng) [2025-02-28T16:37:53Z] <bd808> Deleted deployment-alert01.deployment-prep.eqiad1.wikimedia.cloud (T385849)

Mentioned in SAL (#wikimedia-releng) [2025-02-28T16:39:46Z] <bd808> Deleted parsoid-external-ci-access.wmcloud.org proxy (T385849)

Mentioned in SAL (#wikimedia-releng) [2025-02-28T16:40:45Z] <bd808> Deleted deployment-parsoid14.deployment-prep.eqiad1.wikimedia.cloud (T385849)

Mentioned in SAL (#wikimedia-releng) [2025-02-28T16:43:28Z] <bd808> Deleted now dangling parsoid.svc.deployment-prep.eqiad1.wikimedia.cloud. DNS record (T385849)

Change #1117997 merged by RLazarus:

[operations/puppet@production] deployment-prep: Remove parsoid things from hiera

https://gerrit.wikimedia.org/r/1117997