Current state of Build WG owned machines #4498

Idea came out of a recent Build WG meeting to evaluate where our single points of failure are in the Build WG owned machines/providers. In the screenshots from the host-map tool the rows in green highlight where we have machines on two or more providers.

Infra

No redundancy on any of these:

Azure

• infra-azure-ubuntu2404-x64-1 aka rsync

DigitalOcean

• infra-digitalocean-ubuntu1804-x64-1 aka gzemnid. Is gzemnid still required? #4501
• infra-digitalocean-ubuntu1804-x64-2 aka unofficial-builds. https://unofficial-builds.nodejs.org/
• infra-digitalocean-ubuntu1804-x64-3 aka metrics. Unsure if still needed.
• infra-digitalocean-ubuntu2204-x64-1 aka CI. The test Jenkins server used for testing pull requests.
• infra-digitalocean-ubuntu2204-x64-2 aka www. Staging server. Critical for releases.

IBM Cloud

• infra-ibm-ubuntu2004-x64-1 aka ansible. AWX instance, see Remove ansible.nodejs.org #4487.
• infra-ibm-ubuntu2404-x64-1 aka ci-release. Our Release Jenkins server. Critical for releases.
• infra-mnx-ubuntu2204-x64-1 aka backup-2.
• infra-softlayer-debian8-x64-1 aka registry-mirror. I have no idea what this is. It also doesn't appear to exist in our IBM Cloud account -- maybe it was deleted but not removed from the inventory? ansible: remove registry-mirror from inventory #4500

Rackspace

• infra-rackspace-debian12-x64-1 aka gh-bot. This is the server for https://github.com/nodejs/github-bot and used to bridge between Jenkins and GitHub (CI runs to PR status checks).

Release

node tools/host-map/ release

• AIX and Linux x64 are the only platforms we have redundancy for. All other platforms are dependent on a single provider.
  • Although for x64 we run two jobs (rhel8/9-x64-release and rhel8/9-release-sources) so the two machines help run those in parallel.
• Although ubuntu2404_docker-x64 looks like we have redundancy, we're actually running different containers on the two hosts
  • alpine container on the IBM host
  • cross compilers for armv7 (only for Node.js 22) on the mnx host
• ibmi and zos machines are unused (we don't currently release on those platforms) but are hosted at providers specific to those platforms (so not taking anything away potentially from the other platforms).

Test

node tools/host-map/ test

• For Linux x64 we're reliant on DigitalOcean and IBM Cloud, although some of the platforms are not offered as options on IBM Cloud so we're reliant on DO (e.g. Debian 13, the Fedoras).