Repository navigation
Solidify Digital Ocean Partnership #4499
Description
Activity
Sad, end of an era. This support from DO dates from when they hired Mikeal and he got us a free account during very io.js days; in fact I'm pretty sure it was even before io.js when we were calling it "nodejs-forward" trying to cajole Joyent into allowing the community to contribute to moving things forward before we gave up and pressed the fork button. DO continued to be the backbone of our infra, through the merge with Node v4 and to today.
🍹 thanks for all the compute and support DO.
Reacted by Michaël Zasso, Stewart X Addison, Richard Lau, khayyam, Vinicius Lourenço, Claudio Wunder and Ashary VermayshaIf you currently have Open Source Credits that have already been granted, those credits will continue to be honored according to their existing terms and conditions. No action is required for your existing credit allocation.
Do we know how much time we have left with the existing credits?
@targos As I understand it probably about a month at current usage. I was wondering yesterday if we could get a bit more leaway by downsizing some of them if that's an option (The www server isn't heavily loaded nowadays and so is probably overspecced for example)
Copying @richardlau's list from #4498 for ease of access since it's important for this issue and shows the scale of what we're going to need to look at handling:
Infra:
- infra-digitalocean-ubuntu1804-x64-1 aka gzemnid. request: a server for Gzemnid #1540. I have no idea if anyone remembers this exists or is using it anymore.
- 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.
Release:
- One RHEL8 and one RHEL9 system
Test:
- 14 x64 machines in total including our only RHEL10/x64 systems
Is the description in https://github.com/nodejs/build#tier-1-providers still accurate, referring to hosting nodejs.org?
- DigitalOcean: a popular cloud hosting service, provides a significant amount of the resources required to run the Node.js project including key CI infrastructure/servers required to host nodejs.org.
Until the credits actually run out and we lose the machines, yes.
Reacted by Mike McCready@ryanaslett A question that needs to be asked - is there any budget around that we could use to pay for a subset of the machines to be retained once the program ends?
Of the critical infra ones,
wwwwould have to be replaced by /something/ although it could be smaller than the current machine (I wonder if we could resize it down now to save some credits in the meantime?). The CI one is of course the other system that is critical to the functioning of the project.I'd propose we remove some of the "DO exclusive" distributions from the test matrices and consider shutting them down now. I'm not sure we currently have capacity elsewhere to immediately get those working again. Based on the findings in the other table that would be:
- debian13-x64
- fedora42-x64 (now out of support anyway)
- fedora43-x64
We also have one ubuntu2404-x64 (although that has capacity elsewhere so removing it shouldn't impact things too much) and two
ubuntu2204_docker-x64systems (Only one elsewhere so we might need to keep that for now - it runs some of the Alpine containers)I'd propose we remove some of the "DO exclusive" distributions from the test matrices and consider shutting them down now. I'm not sure we currently have capacity elsewhere to immediately get those working again. Based on the findings in the other table that would be:
- debian13-x64
- fedora42-x64 (now out of support anyway)
- fedora43-x64
Not just capacity. The last time I looked we don't have the ability to either provision those or upload our own images to be able to provision those in the other existing providers we have.
We also have one ubuntu2404-x64 (although that has capacity elsewhere so removing it shouldn't impact things too much) and two
ubuntu2204_docker-x64systems (Only one elsewhere so we might need to keep that for now - it runs some of the Alpine containers)We'd need a serious rethink of our container testing strategy if we were to go down to the single machine as the IBM Cloud one is already lesser specced than the two DO ones. Or a rethink regardless.
Reacted by Stewart X AddisonI've asked about gzemnid in #4501 and in the OpenJS Foundation
#nodejs-coreSlack channel.FWIW, in numbers this is 21 out of 132 (just over 15%) of our Ansible inventory.
Reacted by Matteo CollinaWe have now removed
rhel10-x64,debian13``fedora-last-latest-x64andfedora-latest-x64` from node-test-commit-linux and announced in the #build slack channel.Deleted the following from DO:
- test-digitalocean-debian12-x64-1
- test-digitalocean-fedora43-x64-2
- test-digitalocean-fedora43-x64-2
Will leave it a day or so (Monday at the latest) to see if anyone objects to removing that from the test job so we can bring one back if needed
Deleted
- test-digitalocean-rhel10-x64-1
- test-digitalocean-rhel10-x64-2
- added a commit that references this issue
on Oct 2, 2026 Is the description in nodejs/build#tier-1-providers still accurate, referring to hosting nodejs.org?
- DigitalOcean: a popular cloud hosting service, provides a significant amount of the resources required to run the Node.js project including key CI infrastructure/servers required to host nodejs.org.
@MikeMcC399 is DigitalOcean mentioned on nodejs.org?
hey! would love to help here in any way we (https://fyrastack.com) could, is there anyone i should specifically reach out to for this?
is DigitalOcean mentioned on nodejs.org?
Yes, we list them as a partner in the README, on the homepage, on the partners page, and on the downloads page. I have opened nodejs/nodejs.org#9201 to remove those references.
Reacted by VasilyHey guys— can you shoot me your DO team?
Would love to keep ya’ll on DO while we figure out what version 2.0 of the program looks like.
Or if you open a ticket, I can find it and drop in more credits.
Reacted by ABC TaylorReacted by khayyam, jalciné, Vinicius Lourenço, Anbarasu , TotoyGamingYT, intraducine, Sreeram Venkitesh, Darkie, KD Puvvadi, Stewart X Addison and 6 moreReacted by Carlos Moro, Jintao Zhang and VasilyReacted by Stanley Masinde, jalciné, Anbarasu , intraducine, Ryan Aslett, Wolfite, marph91, gabe and VasilySad to see 😔
Hi @kvangundy , thats amazing, thank you!
The OpenJS Foundation has two teams that we manage, NodeJS (TeamID: 9e687738e57c8108a51f80ce5e879c7a8284dda3) and our OpenJS foundation one (Jquery, and several smaller projects: TeamID: 6ded9d85fae8340acaa82812f5b34857c86f7557)
We'd love to be able to stay.
Reacted by Jintao Zhang and AFCMS- changed the title
[-]Transition off of Digital Ocean[/-][+]Solidify Digital Ocean Partnership[/+]on Oct 3, 2026 Thanks, @kvangundy! We've been super grateful for Digital Ocean's support over the years and would love transition time or a new plan for our accounts with both Node.js and jQuery. Let's find a time to meet next week with my team (@ryanaslett & @bensternthal). Please shoot me an email at rginn@linuxfoundation.org and I'll work with you on scheduling a call.
Reacted by Gautam krishna R, Gürgün Dayıoğlu, Sreeram Venkitesh, Sylwester Lachiewicz, Richard Lau, Matt Cowley, khayyam, Claudio Wunder, Matteo Collina, Jintao Zhang and 2 moreThanks @kvangundy - thanks for reaching out - it's great news that you're keen to find a way to help us stay on DigitalOcean :-)
Reacted by Vasily and AFCMSLooks like Big Corp has been a little humiliated and is now trying to work this back :) it's a shame how so many large hosting companies like DO, AWS etc have built their fortunes on FOSS and cannot even allocate a few threads of compute to the community until it gets called out and PR takes a hit.
Reacted by Thomas LeclercqReacted by AFCMSGlad to see this thread resolving in a positive way @ryanaslett!
Holler if something doesn't work out here (or you know other OSS projects looking for infra resources). I'm just starting up a new open source program at Datum.net (after donating a ~$5M million per year at Packet.net to the CNCF and about 150 other open source projects). Happy to have ideas from the community.
Got a very disappointing email yesterday:
So, we're going to have to figure out what we need to do to transition off of the 21 Digital Ocean droplets we have.Additionally there are some volumes, snapshots, and backups we'll need to address.Opening this as a placeholder, I'll edit with more details.
UPDATE: Digital Ocean is going to help us work this out. See below: #4499 (comment)