QA (public) » openQA Project (public) » openQA Infrastructure (public)

https://progress.opensuse.org/issues/183188

OSD salt-master on separate op-prg2 VM size:S

Motivation¶

We now have more VMs on https://op-prg2.openplatform.suse.com/dashboard/ like recently backup.qe.prg2.suse.org . We can now move the salt-master from OSD to a separate VM so that we have less load on OSD, less "single point of failure" and means to recover such system ourselves.

Acceptance criteria¶

• AC1: https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/README.md references the right salt server
• AC2: https://gitlab.suse.de/openqa/salt-states-openqa/ and https://gitlab.suse.de/openqa/salt-pillars-openqa deployments work based on separate salt-master
• AC3: https://gitlab.suse.de/openqa/osd-deployment/ works based on separate salt-master
• AC4: salt-master on OSD is disabled

Suggestions¶

• Follow #181250 about a prototype VM and ruling out any problems regarding firewall so we know already that OSD machines can generally reach such VM in op-prg2 over salt
• Change https://gitlab.suse.de/openqa/salt-states-openqa/ and https://gitlab.suse.de/openqa/salt-pillars-openqa and https://gitlab.suse.de/openqa/osd-deployment/ to use the new salt-master instead of OSD
• Switch over all currently OSD connected minions (one by one or in bunches or just all at once)
• Ensure README's of above's repos are up-to-date
• Ensure salt-master on OSD is disabled and cleaned up, e.g. /srv/salt and /srv/pillar cleaned up
• DONE Update https://gitlab.suse.de/suse/wiki/-/blob/main/openqa.md and https://gitlab.suse.de/suse/wiki/-/blob/main/qe_infrastructure.md as applicable our salt master is not mentioned there at all, maybe readme of salt-states-openqa