Stewart X Addison

Initial thoughts: - docker-packet-amd-1 and docker-packet-intel-1: Provide direct replacements for both as docker hosts - ESXi/Solaris and the test-packet-u1604 ones: Two replacement servers running some hypervisor for running "real" VMs...

Note that at the moment [the machines we use for our Linux/x64 performance runs](https://ci.adoptopenjdk.net/label/ci.role.perf&&hw.arch.x86&&sw.os.linux/) are on those bare metal machines. If we switch to a virtualised systems we will need...

@vielmetti do these requirements look feasible? Sounds like the emag system will be fully decomissioned so that one can be ignored in the above comments.

@vielmetti Great! Are you ok for me to start creating more on-demand machines in our `t1.replacement` project now and starting to move over? Is there anything I need to do...

@vielmetti Any preference on which locations we should use for the new ones? Most of our existing ones are in AM or DA with one in NY - a similar...

> https://metal.equinix.com/developers/capacity-dashboard/ Oh nice - hadn't seen that before - thanks :-) FYI I've given @Haroon-Khel from the team access to the project so he will be looking at assisting...

Your local ssh client (on the machine you're connecting from) likely does not support the algorithms which the Solaris 10 default install does. Three options: 1. Start up a docker...

FYI I have an s390x dockerhost system now available at 148.100.74.237 which we can set up and put some systems on. It only has eight cores so I don't want...

We may have to just stick to the licensed "real" SLES systems for now sine they should have most of the tools in the default repositories. We could see if...

I'm a little nervous about using the SLES15 repo for SLES12 -do you know how many packages it needs to pull from there? Would be good to list them.