[temurin-compliance] Set up two new Linux/s390x machines for Temurin Compliance

Summary

As per https://github.com/adoptium/infrastructure/issues/2673 Marist are moving to a new provisioning system for their Linux/s390x systems and decommissioning old machines - we would like to get two new servers in place to replace the ones currently in the temurin compliance jenkins instance

Steps to reproduce

n/a

What is the current bug behavior?

n/a

What is the expected correct behavior?

The following new machines are set up as per the other TC machines and available in jenkins. Machines are:

• 148.100.74.16 (Ubuntu 22.04)
• 148.100.74.223 (RHEL7)

eclipse webmaster ssh key has been added to the linux1 user on both with the ability to sudo to root.

Relevant logs and/or screenshots

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Provider is expecting to decomission the two old servers at end of September so we want the new ones active and tested before then if possible.