Operations grimoire/Deploy with Salt - Revision history

Dereckson: Complector

2023-04-02T22:01:17Z

Complector

← Older revision		Revision as of 22:01, 2 April 2023
Line 1:		Line 1:
	== Where to work? ==		== Where to work? ==
	* We deploy from ~~Ysul~~ using:		* We deploy from [[Complector]] using:
	** /opt/nasqueron-operations as our local copy of rOPS, authoritative for Salt		** /opt/salt/nasqueron-operations as our local copy of rOPS, authoritative for Salt
	** /opt/staging for web application content		** /opt/salt/staging for web and application content
	* You need to belong to the <code>~~salt~~</code> group to be able to ~~control Salt~~		* You need to belong to the <code>ops</code> group to be able to have access and have write-rights on the repository
	* You need to belong to the ~~<code>deploy</code> group to be able to update /opt/staging (salt is a member of deploy)~~		* Check if the Salt primary server is alive, if not <code>service salt-master start</code>
	* You want this alias: <code>alias salt sudo -u salt salt</code> (tcsh syntax)
	* Check ~~salt-master~~ is ~~run~~, if not <code>service salt-master start</code>

	== Deployment workflow ==		== Deployment workflow ==
	=== Apply a new Salt state ===		=== Apply a new Salt state ===
	# On your ~~laptop~~, prepare and upload a change to Differential against rOPS repository		# On your computer or a devserver, prepare and upload a change to Differential against rOPS repository
	# ~~Get~~ the ~~change on Ysul: <code>arc patch D607</code>~~		# Merge it to main, we deploy from the min branch
	# Ask Salt to apply the change		# Ask Salt to apply the change
	# Log on #nasqueron-operations something like <code>[Eglide] New user account: amj (D607)</code>		# Log on #nasqueron-operations something like <code>[Eglide] New user account: amj (D607)</code>
	~~# Once working~~, you can ~~merge it~~ to ~~master~~
			If you want to test it before merging, you can push a branch to datacube remote: ssh://windriver.nasqueron.org/datacube/git/operations.git

			Note `arc` isn't available on Complector, as there are too many PHP dependencies.

	=== Deploy a web site ===		=== Deploy a web site ===
	# Commit as needed		# Commit as needed
	# Go to /opt/staging relevant subdirectory and fetch code		# Go to /opt/salt/staging relevant subdirectory and fetch code
	# Ask Salt to apply the matching state (if in doubt, a full run is <code>salt '*' state.highstate</code>)		# Ask Salt to apply the matching state (if in doubt, a full run is <code>salt '*' state.highstate test=True</code>)

	== Salt commands ==		== Salt commands ==
Line 34:		Line 36:
	When you've a new state, ensure it's called from <code>top.sls</code> file, as the repository root.		When you've a new state, ensure it's called from <code>top.sls</code> file, as the repository root.

	=== Salt ~~master~~ ===		=== Salt primary server ===

	If you wish to deploy directly to the ~~Salt master~~, ~~replace <code>salt</code> by <code>salt-call --local</code>~~:		If you wish to deploy directly to the primary server, you've two solutions:

	<code>salt-call --local state.apply test</code>		1. Run a minion there and use <code>salt complector</salt> normally
			2. Replace <code>salt</code> by <code>salt-call --local</code>: <code>sudo salt-call --local state.apply test</code>

	This should run as root, so the recommended alias is <code>alias salt sudo salt</code> (tcsh syntax)		This should run as root, so the recommended alias is <code>alias salt sudo salt</code> (tcsh syntax)

			The second method seems to be currently needed for Vault tokens.

Dereckson: /* Salt commands */

2017-04-28T16:17:16Z

Salt commands

← Older revision		Revision as of 16:17, 28 April 2017
Line 21:		Line 21:

	== Salt commands ==		== Salt commands ==
			=== Remote server ===
	To apply one state or a directory:		To apply one state or a directory:

Line 32:		Line 33:

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

			=== Salt master ===

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

	<code>salt-call --local state.apply test</code>		<code>salt-call --local state.apply test</code>

			This should run as root, so the recommended alias is <code>alias salt sudo salt</code> (tcsh syntax)

Dereckson: /* Salt commands */

2017-04-28T15:42:40Z

Salt commands

← Older revision		Revision as of 15:42, 28 April 2017
Line 31:		Line 31:
	Replace <code>eglide</code> by the server name, or <code>*</code> to target all machines.		Replace <code>eglide</code> by the server name, or <code>*</code> to target all machines.

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

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

	<code>salt-call --local state.apply test</code>		<code>salt-call --local state.apply test</code>

Dereckson: /* Salt commands */

2017-04-28T15:42:23Z

Salt commands

← Older revision		Revision as of 15:42, 28 April 2017
Line 32:		Line 32:

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

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

			<code>salt-call --local state.apply test</code>

2001:470:1F13:D91:3113:262:4553:BBAF: /* Salt commands */

2016-11-07T20:24:39Z

Salt commands

← Older revision		Revision as of 20:24, 7 November 2016
Line 29:		Line 29:
	<code>salt eglide state.highstate</code>		<code>salt eglide state.highstate</code>

	Replace <code>eglide<code> by the server name, or <code>*</code> to target all machines.		Replace <code>eglide</code> by the server name, or <code>*</code> to target all machines.

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

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Deployment workflow */

2016-09-12T05:03:05Z

Deployment workflow

← Older revision		Revision as of 05:03, 12 September 2016
Line 9:		Line 9:

	== Deployment workflow ==		== Deployment workflow ==
			=== Apply a new Salt state ===
	# On your laptop, prepare and upload a change to Differential against rOPS repository		# On your laptop, prepare and upload a change to Differential against rOPS repository
	# Get the change on Ysul: <code>arc patch D607</code>		# Get the change on Ysul: <code>arc patch D607</code>
Line 14:		Line 15:
	# Log on #nasqueron-operations something like <code>[Eglide] New user account: amj (D607)</code>		# Log on #nasqueron-operations something like <code>[Eglide] New user account: amj (D607)</code>
	# Once working, you can merge it to master		# Once working, you can merge it to master
			=== Deploy a web site ===
			# 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 <code>salt '*' state.highstate</code>)

	== Salt commands ==		== Salt commands ==

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Deployment workflow */

2016-09-12T05:00:27Z

Deployment workflow

← Older revision		Revision as of 05:00, 12 September 2016
Line 9:		Line 9:

	== Deployment workflow ==		== Deployment workflow ==
	# On your laptop, prepare and upload a change to Differential against rOPS repository		# On your laptop, prepare and upload a change to Differential against rOPS repository
	# Get the change on Ysul: <code>arc patch D607</code>		# Get the change on Ysul: <code>arc patch D607</code>
	# Ask Salt to apply the change		# Ask Salt to apply the change

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Where to work? */

2016-09-12T05:00:09Z

Where to work?

← Older revision		Revision as of 05:00, 12 September 2016
Line 2:		Line 2:
	* We deploy from Ysul using:		* We deploy from Ysul using:
	** /opt/nasqueron-operations as our local copy of rOPS, authoritative for Salt		** /opt/nasqueron-operations as our local copy of rOPS, authoritative for Salt
	** /opt/~~stating~~ for web application content		** /opt/staging for web application content
	* You need to belong to the <code>salt</code> group		* You need to belong to the <code>salt</code> group to be able to control Salt
			* You need to belong to the <code>deploy</code> group to be able to update /opt/staging (salt is a member of deploy)
	* You want this alias: <code>alias salt sudo -u salt salt</code> (tcsh syntax)		* You want this alias: <code>alias salt sudo -u salt salt</code> (tcsh syntax)
	* Check salt-master is run, if not <code>service salt-master start</code>		* Check salt-master is run, if not <code>service salt-master start</code>

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Where to work? */

2016-09-12T04:59:29Z

Where to work?

← Older revision		Revision as of 04:59, 12 September 2016
Line 1:		Line 1:
	== Where to work? ==		== Where to work? ==
	* We deploy from Ysul /opt/nasqueron-operations		* We deploy from Ysul using:
			** /opt/nasqueron-operations as our local copy of rOPS, authoritative for Salt
			** /opt/stating for web application content
	* You need to belong to the <code>salt</code> group		* You need to belong to the <code>salt</code> group
	* You want this alias: <code>alias salt sudo -u salt salt</code> (tcsh syntax)		* You want this alias: <code>alias salt sudo -u salt salt</code> (tcsh syntax)

Dereckson: Created page with "== Where to work? == * We deploy from Ysul /opt/nasqueron-operations * You need to belong to the `salt` group * You want this alias: `alias salt sudo -u salt s..."`


2016-08-11T12:38:42Z
Created page with "== Where to work? == * We deploy from Ysul /opt/nasqueron-operations * You need to belong to the <code>salt</code> group * You want this alias: <code>alias salt sudo -u salt s..."
New page
== Where to work? ==

* We deploy from Ysul /opt/nasqueron-operations

* You need to belong to the <code>salt</code> group

* You want this alias: <code>alias salt sudo -u salt salt</code> (tcsh syntax)

* Check salt-master is run, if not <code>service salt-master start</code>



== Deployment workflow ==

# On your laptop, prepare and upload a change to Differential against rOPS repository

# Get the change on Ysul: <code>arc patch D607</code>

# Ask Salt to apply the change

# Log on #nasqueron-operations something like <code>[Eglide] New user account: amj (D607)</code>

# Once working, you can merge it to master



== Salt commands ==

To apply one state or a directory:



<code>salt eglide state.apply roles/shellserver/users</code>



To apply all:



<code>salt eglide state.highstate</code>



Replace <code>eglide<code> by the server name, or <code>*</code> to target all machines.



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

Operations grimoire/Deploy with Salt - Revision history

Dereckson: Complector

Dereckson: /* Salt commands */

Dereckson: /* Salt commands */

Dereckson: /* Salt commands */

2001:470:1F13:D91:3113:262:4553:BBAF: /* Salt commands */

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Deployment workflow */

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Deployment workflow */

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Where to work? */

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Where to work? */

Dereckson: Created page with "== Where to work? == * We deploy from Ysul /opt/nasqueron-operations * You need to belong to the salt group * You want this alias: alias salt sudo -u salt s..."

Dereckson: Created page with "== Where to work? == * We deploy from Ysul /opt/nasqueron-operations * You need to belong to the `salt` group * You want this alias: `alias salt sudo -u salt s..."`