-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decomission GoDaddy servers #1781
Comments
Have marked all windows test machines offline to test the impact of losing them |
Before moving bastillion, we have to be sure that all firewall rules are updated so that we don't shut us out. Apart from that it would be great if we could move everything to the final destination for Adoptium. |
infra-godaddy-ubuntu1604-x64-2 (bastillion) has been migrated to a digitalocean host (but as per Andreas' comments we need to do an update before shutting down the old server |
In order to test a way of increasing capacity, I have provisioned a new 24-core Linux/x64 system and am trialling running it with multiple docker containers (each limited to 4 CPU/6Gb to stop the system test suites taking over) that can be used for building or running tests. These are defined with various suffices on https://ci.adoptopenjdk.net/computer/docker-packet-ubuntu2004-x64-1 (suffix indicates the OS, the host/kernel is Ubuntu 20.04). I've left it running for tonight's pipelines after disabling most of the godaddy xLinux test systems, so that should show us how well it copes. At the time of writing (during the JDK8 pipelines) it's running with a load of about 30 (3 of the images are actively using 4 full CPUs) and using about 10Gb of RAM. [EDIT: Proposal for the above, and more details, are in #1809 ] |
You can go ahead from my side and remove the old bastillion machine. |
We expect to be shortly losing our machines hosted with godaddy. I am doing some initial experimentation by marking the test machines offline hosted with them with a
-3
or-4
suffix to see what the impact on pipeline execution time is overnight. Windows and Linux/x64 are generally good for capacity so I do not expect these to become a limiting factor. If this is ok then I'll look at dropping the-2
machines too.Full list of systems that will be affected (checks in the boxes mean they are now offline)
fpm&&ubuntu
for packaging (dup of scaleway so marking offline)And these ones which may I believe are not in use:
The text was updated successfully, but these errors were encountered: