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

Synchronise hostnames across jenkins/inventory.yml/anywhere else #619

Closed
sxa opened this issue Dec 5, 2018 · 22 comments · Fixed by #1338
Closed

Synchronise hostnames across jenkins/inventory.yml/anywhere else #619

sxa opened this issue Dec 5, 2018 · 22 comments · Fixed by #1338
Assignees
Labels
Milestone

Comments

@sxa
Copy link
Member

sxa commented Dec 5, 2018

Example: test-osuosl-ppc64le-ubuntu-16-04-1 is shown as test-osuosl-ubuntu1604-ppc64le-1 in inventory.yml

There are likely more examples. Makes it awkward to run the inventories against a specific machine when someone requests it (generally with a name from Jenkins)

@HusainYusufali
Copy link
Contributor

Pull request opened to update the inventory.yml file to match the jenkins hosts. #634

@HusainYusufali
Copy link
Contributor

HusainYusufali commented Dec 17, 2018

Below is a list of changes that need to be created in order to synchronize the hosts across Jenkins and the Inventory.yml. @sxa555 can you please review this before I go ahead and make the changes

Current Name In Jenkins New Name in Jenkins
build-macstadium-macos1010-1 build-macstadium-macos1010-x64-1
build-macstadium-macos1010-2 build-macstadium-macos1010-x64-2
test-macincloud-macos1010-1 test-macincloud-macos1010-x64-1
test-macincloud-macos1010-2 test-macincloud-macos1010-x64-2
build-osuosl-ppc64-aix-71-1 build-osuosl-aix71-ppc64-1
build-osuosl-ppc64-aix-71-2 build-osuosl-aix71-ppc64-2
test-osuosl-ppc64le-ubuntu-16-04-1 test-osuosl-ubuntu1604-ppc64le-1
test-osuosl-ppc64le-ubuntu-16-04-2 test-osuosl-ubuntu1604-ppc64le-2
test-packet-armv8-ubuntu-16-04 test-packet-ubuntu1604-armv8-1
test-packet-x64-windows-2012r2-1 test-packet-win2012r2-x64-1
build-marist-s390x-zOS-1 build-marist-zos21-s390x-1
build-marist-s390x-zOS-2 build-marist-zos21-s390x-2
build-scaleway-x64-ubuntu-16-04-2 build-scaleway-ubuntu1604-x64-2
build-scaleway-armv7-ubuntu16-04-1 build-scaleway-ubuntu1604-armv7-1
build-scaleway-armv7-ubuntu16-04-2 build-scaleway-ubuntu1604-armv7-2
test-marist-sles12-s390x-1 build-marist-sles12-s390x-1
test-marist-s390x-sles-12 test-marist-sles12-s390x-1
build-marist-s390x-sles-12 test-marist-sles12-s390x-2
Jenkins machines to be added to inventory
build-plymouth-x64-solaris11-1
build-sxa-armv7-raspbian
build-marist-sles12-s390x-1 (update IP)
test-marist-sles12-s390x-1
test-marist-sles12-s390x-2
build-scaleway-armv7-ubuntu16-04-1-temp
build-scaleway-armv7-ubuntu16-04-2-temp
test-softlayer-win2012r2-x64-1

@karianna
Copy link
Contributor

I have to question the two temp machines on scale way - who set those up and for what purpose?

@karianna
Copy link
Contributor

the test-marist labels seem mixed up as well.

@HusainYusufali
Copy link
Contributor

HusainYusufali commented Dec 18, 2018

Some of the machines are named incorrectly in contrast to the labels they have. The changes that need to be made are listed below and updated in the table above in bold. In regards to the scaleway temp machines I do not have any information on that.

https://ci.adoptopenjdk.net/computer/test-marist-sles12-s390x-1/ is build machine based on its labels, requires a name change, and IP changed in the inventory file

https://ci.adoptopenjdk.net/computer/build-marist-s390x-sles-12/ is a test machine based on its labels, requires a name change, and added to the inventory file

https://ci.adoptopenjdk.net/computer/test-marist-s390x-sles-12/ is a test machine, requires a name change, and added to the inventory file

@sxa sxa modified the milestones: 2019 March, 2019 April Mar 7, 2019
@sxa sxa modified the milestones: 2019 April, 2019 May Apr 30, 2019
@sxa sxa modified the milestones: 2019 May, 2019 June May 28, 2019
@sxa sxa added this to the August 2019 milestone Jul 30, 2019
@sxa
Copy link
Member Author

sxa commented Jul 30, 2019

Most of the issues with the marist sles 12 machine(s) was resolved under #765.
@Willsparker This could do with being revisited. inventory.yml is the master list of all our machines and is processed by ansible tower when deciding which machines to configure. This issue is mostly surrounding the fact that not all of the names on there match the ones used in https://ci.adoptopenjdk.net/computer/

@Willsparker
Copy link
Contributor

All of the hostnames I've found that were out of sync between ci.adoptopenjdk.net and inventory.yml

Jenkins Inventory.yml
build-macstadium-macos1010-1 build-macstadium-macos1010-x64-1
build-macstadium-macos1010-2 build-macstadium-macos1010-x64-2
build-macstadium-macos1012-1 build-macstadium-macos1012-x64-1
build-macstadium-macos1012-2 build-macstadium-macos1012-x64-2
build-marist-s390x-zOS-1 build-marist-zos21-s390x-1
build-marist-s390x-zOS-2 build-marist-zos21-s390x-2
build-osuosl-ppc64-aix-71-1 build-osuosl-aix71-ppc64-1
build-osuosl-ppc64-aix-71-2 build-osuosl-aix71-ppc64-2
build-packet-ubuntu1604-armv7l-1 Missing from Inventory.yml
build-packet-ubuntu1604-armv8l-1 Missing from Inventory.yml
build-scaleway-x64-ubuntu-16-04-2 build-scaleway-Ubuntu1604-x64-2
build-scaleway-armv7-ubuntu16-04-2 build-scaleway-ubuntu1604-armv7-1
build-scaleway-armv7-ubuntu16-04-1 build-scaleway-ubuntu1604-armv7-2
test-godaddy-win3 test-godaddy-win2016-x64-3
test-osuosl-ppc64-aix-71-1 test-osuosl-aix71-ppc64-1
Missing from Jenkins test-osuosl-aix71-ppc64-2
test-packet-armv8-ubuntu-16-04 test-packet-ubuntu1604-armv8-1
test-packet-x64-windows-2012r2-1 test-packet-win2012r2-x64-1
test-marist-ubuntu1604-s390x-2-XJ Missing from Inventory.yml
Missing from Jenkins test-softlayer-win2012r2-x64-1

@sxa
Copy link
Member Author

sxa commented Aug 13, 2019

Notes:

@karianna
Copy link
Contributor

All of the hostnames I've found that were out of sync between ci.adoptopenjdk.net and inventory.yml

Jenkins Inventory.yml
build-macstadium-macos1010-1 build-macstadium-macos1010-x64-1
build-macstadium-macos1010-2 build-macstadium-macos1010-x64-2
build-macstadium-macos1012-1 build-macstadium-macos1012-x64-1
build-macstadium-macos1012-2 build-macstadium-macos1012-x64-2
build-marist-s390x-zOS-1 build-marist-zos21-s390x-1
build-marist-s390x-zOS-2 build-marist-zos21-s390x-2
build-osuosl-ppc64-aix-71-1 build-osuosl-aix71-ppc64-1
build-osuosl-ppc64-aix-71-2 build-osuosl-aix71-ppc64-2
build-packet-ubuntu1604-armv7l-1 Missing from Inventory.yml
build-packet-ubuntu1604-armv8l-1 Missing from Inventory.yml
build-scaleway-x64-ubuntu-16-04-2 build-scaleway-Ubuntu1604-x64-2
build-scaleway-armv7-ubuntu16-04-2 build-scaleway-ubuntu1604-armv7-1
build-scaleway-armv7-ubuntu16-04-1 build-scaleway-ubuntu1604-armv7-2
test-godaddy-win3 test-godaddy-win2016-x64-3
test-osuosl-ppc64-aix-71-1 test-osuosl-aix71-ppc64-1
Missing from Jenkins test-osuosl-aix71-ppc64-2
test-packet-armv8-ubuntu-16-04 test-packet-ubuntu1604-armv8-1
test-packet-x64-windows-2012r2-1 test-packet-win2012r2-x64-1
test-marist-ubuntu1604-s390x-2-XJ Missing from Inventory.yml
Missing from Jenkins test-softlayer-win2012r2-x64-1

Can we automate that?

@sxa
Copy link
Member Author

sxa commented Aug 13, 2019

Can we automate that?

Should be able to put together a job that does a check and passes/fails based on whether they're in sync without too much difficulty. Can do that after we do the one-off cleanup ...

@sxa
Copy link
Member Author

sxa commented Aug 13, 2019

Also https://ci.adoptopenjdk.net/view/work%20in%20progress/job/SXA-processCheck should have pretty much the same list of machines

@karianna karianna modified the milestones: August 2019, September 2019 Sep 2, 2019
@karianna karianna modified the milestones: September 2019, October 2019 Oct 4, 2019
@sxa sxa modified the milestones: October 2019, November 2019 Nov 1, 2019
@karianna
Copy link
Contributor

karianna commented Nov 6, 2019

@karianna @sxa555 Is a one-off cleanup still required, and if so where should I take the hostnames from?

I'll defer to @sxa on this one

@sxa sxa modified the milestones: November 2019, December 2019 Nov 29, 2019
@sxa sxa modified the milestones: December 2019, January 2020 Dec 31, 2019
@karianna karianna modified the milestones: January 2020, February 2020 Feb 3, 2020
@sxa sxa modified the milestones: February 2020, March 2020 Feb 25, 2020
@sxa sxa modified the milestones: March 2020, April 2020 Mar 31, 2020
@sxa sxa modified the milestones: April 2020, May 2020 May 4, 2020
@sxa
Copy link
Member Author

sxa commented May 18, 2020

Let's make them consistent, so <use>-<provider>-<os>-<arch>-<count> as far as practical.

@Willsparker
Copy link
Contributor

Willsparker commented May 18, 2020

I've changed the following at ci.adoptopenjdk.net, FYI:

test-packet-x64-windows-2012r2-1 	---> 	test-packet-win2012r2-x64-1
test-packet-armv8-ubuntu-16-04		--->	test-packet-ubuntu1604-armv8-1
test-ibm-ppc64-aix-71-2 		--->	test-ibm-aix71-ppc64-2
test-ibm-ppc64-aix-71-1 		---> 	test-ibm-aix71-ppc64-1
test-ibm-cabbage			---> 	test-ibm-aix71-ppc64-3
test-godaddy-win3			---> 	test-godaddy-win2016-x64-3
perf-macstadium-macos1015-2		--->	perf-macstadium-macos1015-x64-2
perf-macstadium-macos1015-1		--->	perf-macstadium-macos1015-x64-1
infra-vagrant-1				--->	infra-softlayer-ubuntu1804-x64-1
build-scaleway-x64-ubuntu-16-04-2 	--->	build-scaleway-ubuntu1604-x64-1
build-scaleway-armv7-ubuntu16-04-2	--->	build-scaleway-ubuntu1604-armv7-2
build-scaleway-armv7-ubuntu16-04-1	--->	build-scaleway-ubuntu1604-armv7-1
build-osuosl-ppc64-aix-71-2		--->	build-osuosl-aix71-ppc64-2
build-osuosl-ppc64-aix-71-1		--->	build-osuosl-aix71-ppc64-1
build-marist-s390x-zOS-2		--->	build-marist-zOS-s390x-2
build-marist-s390x-zOS-1		--->	build-marist-zOS-s390x-1
build-macstadium-macos1014-2		--->	build-macstadium-macos1014-x64-2
build-macstadium-macos1014-1		--->	build-macstadium-macos1014-x64-1
build-macstadium-macos1012-1		--->	build-macstadium-macos1012-x64-1
build-macstadium-macos1010-1		--->	build-macstadium-macos1010-x64-1

@Willsparker
Copy link
Contributor

Of all the hosts that are currently offline at ci.adoptopenjdk.net, the follow are 'unpingable'

build-godaddy-rhel7-x64-1
build-linaro-centos74-armv8-1 	( build-linaro-centos74-armv8-2 had same IP )
build-linaro-centos76-armv8-2
build-marist-ubuntu1604-s390x-2
build-marist-ubuntu1604-s390x-3
docker-aws-ubuntu1604-x64-0
infra-aws-ubuntu1804-x64-1
test-macincloud-macos1014-x64-3
test-osuosl-centos74-ppc64le-3

@sxa
Copy link
Member Author

sxa commented May 18, 2020

test-godaddy-win3 to test-godaddy-win2016-x64-3 may be problematic

@Willsparker
Copy link
Contributor

Can we confirm that's still an issue? It's been quite awhile

@sxa
Copy link
Member Author

sxa commented May 20, 2020

Feel free to verify

@Willsparker
Copy link
Contributor

I would love to, but none of them are connected to Jenkins, nor do I have credentials for them. They're also not displaying clock time or response difference which I think is a show that they're turned off at the minute?

@Willsparker
Copy link
Contributor

I think with the above PR, this issue can be closed. Any objections anyone?

@sxa
Copy link
Member Author

sxa commented May 27, 2020

Fine with me as long as we don't see lots of things queued up overnight because of it ;-)

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

Successfully merging a pull request may close this issue.

4 participants