Nasqueron Agora - User contributions [en]

Operations grimoire/Deploy with Salt

2016-09-12T05:03:05Z

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

== 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 <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)
* Check salt-master is run, if not <code>service salt-master start</code>

== Deployment workflow ==
=== Apply a new Salt state ===
# 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
=== 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 ==
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

2016-09-12T05:00:27Z

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

== 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 <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)
* 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

2016-09-12T05:00:09Z

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

== 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 <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)
* 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

2016-09-12T04:59:29Z

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

== Where to work? ==
* 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 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/Sites on Ysul

2016-09-12T04:57:51Z

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: Created page with "Sites on Ysul are deployed to /var/wwwroot. Four processes are known: * through custom deployment script (e.g. Zed, Nasqueron Tools) * through Git (e.g. www.espace-win.org ar..."

Sites on Ysul are deployed to /var/wwwroot.

Four processes are known:
* through custom deployment script (e.g. Zed, Nasqueron Tools)
* through Git (e.g. www.espace-win.org archive)
* through Jenkins task (e.g. dæghrefn.nasqueron.org)
* without any deployment workflow

To deploy a Jenkins-powered site, just commit to master and the deploy job will run automatically.

For other sites, reach Dereckson for guidance and support.

Operations grimoire/Sites on Eglide

2016-09-12T04:53:43Z

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: Created page with "Sites on Eglide are fully managed through Salt configuration. == www.eglide.org == # On the Salt master, go to /opt/staging/wwwroot/eglide.org # Pull new code through <code>g..."

Sites on Eglide are fully managed through Salt configuration.

== www.eglide.org ==
# On the Salt master, go to /opt/staging/wwwroot/eglide.org
# Pull new code through <code>git fetch && git log HEAD..origin/master</code> and if changes are as expected <code>git rebase master</code>.
# Run <code>salt eglide state.apply roles/shellserver/eglide-website</code>

Operations grimoire

2016-09-12T04:51:07Z

2001:470:1F13:D91:E8A0:AB13:681B:5C9F: /* Services configuration */

Welcome to the Nasqueron operations grimoire (NOG).

== Infrastructure ==
* [[/Docker engine]]

== Services ==
=== Identity management ===
* [[/Login]] (Auth Grove)

=== Collaborative tools ===
* [[/Dæghrefn]] (eggdrop)
* [[/DevCentral]] (Phabricator)
* [[/Etherpad]]

=== CI/CD ===
* [[/Broker]]
* [[/Jenkins]]
* [[/Notifications center]]
* [[/Vault]]

== Other web sites ==
* [[/Sites on Eglide]]
* [[/Sites on Ysul]]
== Services configuration ==
''This section contains general information not related to a specific service.''
* [[/SSL certificates]] (Let's encrypt / letsencrypt)

== Checklists ==
=== Docker ===
* [[/Restart a Docker engine]]
* [[/Dwellers to DevCentral]]
* [[/Git operations in production containers]]

=== Salt ===
* [[/Deploy with Salt]]
* [[/Create and revoke user accounts on Salt servers]]

== Appendices ==
* [[/Policies]]
* [[/Contacts]]

[[Category:Reference]]