Hi, I need to orchestrate Salt states so that VMs are started, stopped and configured in stages. I tried using the Salt Orchestrate Runner, but it couldn't find states that I can use with 'qubesctl state.sls <state>' and 'qubesctl state.highstate'.
I have two use cases: 1. Salt should start, configure, and halt template VMs before it starts app VMs that use them. For example, the Salt GPG state requires the python-gnupg package. This package needs to be installed in the template VM so that the Salt GPG state can import keys in the app VM. The current sequence of my states appears to let template VMs halt before Salt starts app VMs. But I would like to strictly enforce this ordering between admin VM states and regular VM states. 2. Salt should ensure that service VMs are running before Salt applies states to their client VMs. For example, I have a service VM that exports gpg-agent's SSH socket through Qrexec. This VM needs to be running so that the client VM can clone git repos using keys on the serivce VM. This second case is more difficult to enforce without orchestration. I can approximate this functionality with a series of commands: qubesctl --target template-vm state.highstate qvm-shutdown template-vm qubesctl --target service-vm state.highstate qvm-start service-vm qubesctl --target client-vm state.highstate But I would like to be able to describe this orchestration in Salt. Does the Salt Orchestrate Runner work on Qubes? If not, is there a way to orchestrate Salt on Qubes? Thanks, Brian -- Brian C. Duggan he/him/his -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/53a38760-fd3e-31f8-d06b-b821a809fc23%40dugga.net. For more options, visit https://groups.google.com/d/optout.
