action #132146
Updated by okurz over 1 year ago
## Motivation The openQA webUI VM for osd will move to PRG2, same as for o3. This will be conducted by Eng-Infra. We must support them. ## Acceptance criteria * **AC1:** osd is reachable from the new location for SUSE employees * **AC2:** osd multi-machine jobs run successfully on osd after the migration * **AC3:** We can still login into the machine over ssh * **AC4:** https://monitor.qa.suse.de can still reach and monitor OSD * **AC5:** No job results are present in the file system for jobs that are no longer in the database (also taking the archive directory into account) ## Suggestions * *DONE* Inform affected users about planned migration on date 2023-08-29 * *DONE* Track https://jira.suse.com/browse/ENGINFRA-1742 "Build OpenQA Environment" for story of the openQA VMs being migrated * *DONE* Ensure that we can still login into the machine over ssh * *DONE* Ensure that *both* https://openqa.suse.de as well as https://openqa.nue.suse.com work * *DONE* (supposedly nothing to be changed) Update https://wiki.suse.net/index.php/OpenQA where necessary * *DONE* Enable salt-minion and salt-master on new-osd again * *DONE* Ensure that events to rabbit.suse.de can be published (look for errors in the openqa-webui.service journal) * *DONE* During migration work closely with Eng-Infra members conducting the actual VM migration * *DONE* Ensure openqa.nue.suse.com DNS record points to the new IP and is included in the certificate generation at https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/certificates/hosts.sls#L8 again (was removed temporary as workaround by @nicksinger) * Learn from #132143 what to look out for regarding OSD migration * Ensure that osd is reachable again after migration from the new location * for SUSE employees * for osd workers from all locations, e.g. PRG2, NUE1-SRV1, NUE1-SRV2, FC Basement * Ensure that https://monitor.qa.suse.de can still reach and monitor OSD * *DONE* Inform users as soon as migration is complete * Enable https://gitlab.suse.de/openqa/osd-deployment/-/pipeline_schedules/36/edit again and ensure it's working on new-osd * For AC5, create a script to do this kind of cleanup and run it once (before running it for real, make sure it would do the right thing by doing a dry-run first) * Ensure openqa.nue.suse.com DNS record points to the new IP and is included in the certificate generation at https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/certificates/hosts.sls#L8 again (was removed temporary as workaround by @nicksinger)