-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
IBMCLOUD Machine Review & Refresh #3331
Comments
FYI @sxa , @AdamBrousseau , @Haroon-Khel All please use this issue to discuss and plan changes required to the IBM Cloud hosted machines, I've put in some initial thoughts on the status of these machines, and what we require, but we'll bottom this out first, so there's a clear set of plans :) |
Tagging in @smlambert too in case she has any input to the mix of machines from a test perspective. We don't currnetly have any RHEL9 so that should be an "obvious" one to add into the mix as it's the latest available RHEL version. We should also consider whether it is appropriate to keep the RHEL6 one around (There are other options for something equivalent, such as a CentOS6 container) |
FYI @AdamBrousseau it looks like all of our machines other than the vagrant one seem to have gone offline - first alerted by Nagios at 1616 yesterday. Are you aware of this? We probably need to start looking at bumping the priority of getting these replacements (likely with whatever restrictions IBM wants to put on us for now) |
As discussed in Slack, an ssh IP allow list has been implemented. We have added the Jenkins controller IP for now. We can add more IPs if needed. |
A couple of updates to the above:
|
Review Adoptium Machines Hosted In IBM Cloud.
Below is a list of all of the IBM Cloud hosted machines in use at Adoptium, as part of the Equinix replacement and EOL windows systems, this is a good opportunity to review the machines, and refresh them as appropriate.
IBM Cloud Machines
Infrastructure Hosts
RETAIN AS IS - vagrant-x64-1: {ip: 150.239.60.120}
Build Hosts
RETAIN AS IS - win2022-x64-1: {ip: 52.118.206.11, user: Administrator}
REMOVE - REPLACE WITH ALTERNATE LINUX 1* - win2012r2-x64-1: {ip: 169.48.4.138, user: Administrator}
REMOVE - REPLACE WITH ALTERNATE LINUX 2* - win2012r2-x64-2: {ip: 169.48.4.142, user: Administrator}
Test Hosts
RETAIN AS IS - rhel6-x64-1: {ip: 169.48.4.140}
RETAIN AS IS - rhel7-x64-1: {ip: 169.48.4.136}
REMOVE (REPLACE WITH RHEL9 System) - ubuntu1604-x64-1: {ip: 169.48.4.141} -
REMOVE (REPLACE WITH WIN2022 System) - win2012r2-x64-1: {ip: 169.48.4.131, user: Administrator}
REMOVE (REPLACE WITH WIN2022 System) - win2012r2-x64-2: {ip: 169.48.4.139, user: Administrator}
See also: Equinix Replacement - #3292
See also: Windows Decommision - #3238 (comment)
N.B
We'd like to replace the 2 redundant windows 2012 build machines with 2 new linux hosts specs and O/S versions to be agreed, but potentially a new dockerhost, and the second machine commissioned as a potential replacement for C3AWX
The text was updated successfully, but these errors were encountered: