action #136133
Updated by okurz 8 months ago
## Motivation
Extracted from #134864
## Acceptance criteria
* **AC1:** aarch64.openqanet.opensuse.org up and running in FC Basement again
* **AC2:** Inventory management systems, i.e. racktables and netbox, reflect the plan and current situation at all times
* **AC3:** On top of AC1 machine is successfully working on o3 jobs
## Suggestions
* Read what had been done in #134864 (the machine is physically already in FC Basement, see https://racktables.nue.suse.com/index.php?page=object&tab=default&object_id=2034, it's connected to power, ipmi and system ethernet, ipmi should be reachable)
* *DONE* Wait for https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4043
* Ensure you can reach the machine over IPMI
* Update https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls as necessary
* Lookup what we did for the "rsync over external ssh" forwarding on o3 workers and apply the same here so that the machine can get tests from o3 over public network
* Trigger some test-tests and if all good use production worker classes
* As necessary extend progress.opensuse.org/projects/openqav3/wiki/ for the machine which is likely not directly reachable by community members as it resides within SUSE internal network
* Ensure inventory management system(s), at least racktables, is up-to-date
* Ensure machines are usable again from new location, e.g. passing openQA tests accordingly
## Rollback actions
* Re-enable https://gitlab.suse.de/openqa/monitor-o3/-/pipeline_schedules after aarch64.o3 is up again, see #135467
Back