Operations grimoire/Deploy with Salt

📕📁📜 Old technical information :: content warning

⌛ This Nasqueron Operations Grimoire page hasn't been updated for a long time.

☣ As our infrastructure evolves quickly, there is a good chance this information is outdated or now inaccurate. Be careful and consider update it.

➡️ To assert the information is still up-to-date or not, you can check the history of the relevant role in our Operations repository.

Where to work?

We deploy from Ysul using:
- /opt/nasqueron-operations as our local copy of rOPS, authoritative for Salt
- /opt/staging for web application content
You need to belong to the salt group to be able to control Salt
You need to belong to the deploy group to be able to update /opt/staging (salt is a member of deploy)
You want this alias: alias salt sudo -u salt salt (tcsh syntax)
Check salt-master is run, if not service salt-master start

On your laptop, prepare and upload a change to Differential against rOPS repository
Get the change on Ysul: arc patch D607
Ask Salt to apply the change
Log on #nasqueron-operations something like [Eglide] New user account: amj (D607)
Once working, you can merge it to master

Commit as needed
Go to /opt/staging relevant subdirectory and fetch code
Ask Salt to apply the matching state (if in doubt, a full run is salt '*' state.highstate)

To apply one state or a directory:

salt eglide state.apply roles/shellserver/users

To apply all:

salt eglide state.highstate

Replace eglide by the server name, or * to target all machines.

When you've a new state, ensure it's called from top.sls file, as the repository root.

If you wish to deploy directly to the Salt master, replace salt by salt-call --local:

salt-call --local state.apply test