adoptium / adoptium/infrastructure

Resolve AIX hostname resolution issues

Open
#3,344 2 comments 0 reactions 0 assignees View on GitHub
os:aix
Dominant language
Python
Stars
96
Forks
106
Avg merge
1d 16h
Merged PRs (30d)
12

Description

I suggest we adjust the AIX playbooks to set the hostname on the machine to match the inventory file. This would make it consistent with the other UNIX playbooks and ease the cross-platform system administration by providing consistent naming on the machines. The changes towards the end of last year to auto-deploy the playbooks on a regular basis have highlighted some concenrs in the issue below. In this proposal I am assuming that the use of the OSUOSL NIM server will not be affected. Let me know if I am mistaken on that.

_Originally posted by @sxa in https://github.com/adoptium/infrastructure/issues/3178#issuecomment-1891645304_

As a follow-up to [the proposals above](https://github.com/adoptium/infrastructure/issues/3178#issuecomment-1888792438), noting that for other operating systems:
- We change the hostname in the UNIX playbooks to match the name from the inventory.yml file: https://github.com/adoptium/infrastructure/blob/d2303c7fa6daf3be310fac1f36c21da4c78a0de3/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/adopt_etc/tasks/main.yml#L25
- On windows we have logic to do a hostname change, but it's only invoked if the machine name ends in a hypen character: https://github.com/adoptium/infrastructure/blob/d2303c7fa6daf3be310fac1f36c21da4c78a0de3/ansible/playbooks/AdoptOpenJDK_Windows_Playbook/roles/Common/tasks/main.yml#L41 (From https://github.com/adoptium/infrastructure/issues/2133)

On this basis it is likely that making a similar change to the UNIX playbook on the AIX machines is the preferred option here, however given the proximity to the January release cycle I suggest we pause anything more for now (although comments/discussion on the options are still welcome) We could also use `/etc/motd` to remind people on login what the `adoptXX` name is (Similar to what we do for the RISC-V machines at the PLCTlab.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the AIX playbooks with the UNIX hostname task in ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/adopt_etc/tasks/main.yml and the inventory.yml naming referenced in the issue. Check the Windows hostname task for precedent, then verify that the proposed hostname change does not affect the OSUOSL NIM server; done means AIX machines match their inventory names without disrupting deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible
Domain
devops, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.