Skip to content
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

Closed
18 of 22 tasks
sxa opened this issue Dec 23, 2020 · 5 comments
Closed
18 of 22 tasks

Decomission GoDaddy servers #1781

sxa opened this issue Dec 23, 2020 · 5 comments
Assignees
Labels
Milestone

Comments

@sxa
Copy link
Member

sxa commented Dec 23, 2020

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)

  • infra-ubuntu1604-x64-1 (git-hg mirroring system)
  • build-rhel7-x64-1 Was GAO - now used for javafutures - testing with build-scaleway-ubuntu1604-x64-1
  • build-ubuntu1604-x64-1 fpm&&ubuntu for packaging (dup of scaleway so marking offline)
  • docker-godaddy-ubuntu1604-x64-1 No tags so likely unused - marking offline
  • test-centos7-x64-1 up to 4
  • test-debian8-x64-1 up to 4
  • test-ubuntu1604-1 up to 4
  • win2016-x64-1 up to 4 (Decomissioning 3&4 generates 4hr queues)
  • infra-godaddy-ubuntu1604-x64-2 / bastillion (now migrated) and jumpbox
  • build-godaddy-win2016-x64- (244.75 - Win/aarch64 build)

And these ones which may I believe are not in use:

  • trss.adoptopenjdk.net (OLD, unused? 246.241)
  • infra-godaddy-ubuntu1604-x64-3 (ERROR)
  • infra-godaddy-awx (Not used - 250.8)
  • test-godaddy-ubuntu2004-x64- (246.136)
  • test-godaddy-ubuntu2004-x64- (yes same name as above - 198.12.226.105)
  • test-godaddy-ubuntu2004-x64-3 (148.66.132.244)
  • build-godaddy-ubuntu1604-x64-1 (254.64) (Marked offline until I know if it is still required for anything)
  • infra-will-centos-x64- (253.143)
  • infra-will-ubuntu-x64- (253.133)
  • test-msi-install (246.82)
  • gdams-test-docker (252.27)
  • sxacross-godaddy-debian8-x86- (160.153.249.78)
@sxa
Copy link
Member Author

sxa commented Dec 24, 2020

Have marked all windows test machines offline to test the impact of losing them

@aahlenst
Copy link
Contributor

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.

@sxa
Copy link
Member Author

sxa commented Jan 4, 2021

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
**
infra-ubuntu1604-x64-1 (git mirror) has been brought up on an AWS system which we already had but it was never activated in production. Testing with 8, 11, and a skara job

@sxa sxa added this to the January 2021 milestone Jan 5, 2021
@sxa sxa pinned this issue Jan 5, 2021
@sxa
Copy link
Member Author

sxa commented Jan 5, 2021

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 ]

@aahlenst
Copy link
Contributor

You can go ahead from my side and remove the old bastillion machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants