action #107731
Updated by mkittler 12 months ago
## Motivation
See #107173#note-6 . I also chatted with nsinger about this: "s.qa is now salted, should we add it as salt node to OSD for auto-update+monitoring? What other machines should we add? Where does it end? If we include backup.qa, s.qa, storage.qa, why not also include qamaster, qanet? Or all QA machines? Nick Singer: Indeed I plan to eventually add all QA machines into a single salt for at least stuff like passwords and ssh keys"
## Acceptance criteria
* **AC1:** All common production QA machines are controlled by salt (not workstations or bare-metal test machines)
## Suggestions
* Review all common production QA machines in racktables and VMs and ensure they are controlled at least by *some* remote management framework repository, at best salt-states-openqa which also ensures automatic updates and monitoring
* If you don't know if a machine is production or not ask okurz
* For machines that involve another repository ensure that they are still included in automatic updates and monitoring
* For any machines that are not straight-forward make sure that a specific open ticket exists covering that machine
* Use Racktables to find out what common production QA machines are