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

ESXi server at Equinix #2792

Closed
5 of 10 tasks
sxa opened this issue Oct 18, 2022 · 7 comments
Closed
5 of 10 tasks

ESXi server at Equinix #2792

sxa opened this issue Oct 18, 2022 · 7 comments

Comments

@sxa
Copy link
Member

sxa commented Oct 18, 2022

I need to request a new machine:

  • New machine operating system (e.g. linux/windows/macos/solaris/aix): ESXi
  • New machine architecture (e.g. x64/aarch32/arm32/ppc64/ppc64le/sparc): x64
  • Provider (leave blank if it does not matter): Equinix
  • Desired usage: Replacement for the existing ESXi server due to machine migration, and to use for relpacement of some of the smaller xLinux machines we currently have hosted at Equinix
  • Any unusual specification/setup required: ESXi :-)
  • How many of them are required: 2 (One to begin with, but should be duplicated with the same set of systems across both for redundancy - ideally with both in different data centres.

Please explain what this machine is needed for:

  • Part of Equinix migration to new data centres #2666 - existing servers will be decommissioned and we need to ensure the replacements are operational before then.
    To be consistent with the existing naming convention these should have a provider name of equinix_esxi in the hostname:

Guest VMs required are as follows. Specs listed are of the existing systems

  • Solaris/x64 build machine (8 core, 16GB, 250Gb) (Probably don' need this much disk ...)
  • Solaris/x64 test (AQA) machine (n/a - no current system separate from build)
  • Solaris/x64 TCK machine (4 core, 8Gb, 500Gb) (Probably doesn't need this much disk...)
  • Linux/x64 performance machine (4 core, 8Gb, 140Gb)
  • Linux/x64 TCK machine (8 core, 8Gb, 140Gb) (Also used as dockerhost, so may benefit from more RAM)

I'll create tick boxes for the second instance too:

  • Solaris/x64 build machine
  • Solaris/x64 test (AQA) machine
  • Solaris/x64 TCK machine
  • Linux/x64 performance machine
  • Linux/x64 TCK machine
@Haroon-Khel
Copy link
Contributor

Haroon-Khel commented Oct 19, 2022

@Haroon-Khel
Copy link
Contributor

@Haroon-Khel
Copy link
Contributor

@sxa The original issue #2666 (comment), there are 3 ubuntu16 machines which needed to be virtualised, im guessing theyre to be used for perf testing. Ive virtualised one https://ci.adoptopenjdk.net/computer/test-equinix_esxi-ubuntu1604-x64-1-NEW/, do we still need 2 more?

@sxa
Copy link
Member Author

sxa commented Nov 9, 2022

We should have two. I would also suggest that since we're switching to new hardware (where the perf characteristics will be different anyway) that we bump them up to ubuntu 22.04 instead of 16.04 which is now unsupported. I'd suggest one more - and possibly on the same machine purely because if we split it across AMD vs Intel with differnet characteristics the results won't be consistent. For all the others we should split them with one on each of two ESXi servers.

@Haroon-Khel
Copy link
Contributor

Haroon-Khel commented Nov 16, 2022

I've upgraded the ubuntu16 perf machine I made earlier to 2204, https://ci.adoptopenjdk.net/computer/test-equinix_esxi-ubuntu2204-x64-1-NEW/, and created a second u2204 perf machine https://ci.adoptopenjdk.net/computer/test-equinix_esxi-ubuntu2204-x64-1
2-NEW/. Both are on the intel esxi server. I'll create an AMD replica after I finish these machines. Perf sanity tests run fine on the machines

@Haroon-Khel
Copy link
Contributor

A second ESXi server has been created as the first one ran out of assignable IP addresses. On this second server, we have the 2 tck machines, solaris and ubuntu. EF are currently setting them up with an ETA of before the end of the month

@sxa
Copy link
Member Author

sxa commented Dec 1, 2022

@Haroon-Khel Can we close this now? I don't think there are any other immediate action items for it other than adding to the inventory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants