Différences

Ci-dessous, les différences entre deux révisions de la page.

--- tuto:linux:saltstack [2018/03/04 20:34] – [Macro] root
+++ tuto:linux:saltstack [2019/07/29 17:54] (Version actuelle) – [Renderer en python] root
@@ Ligne 8: / Ligne 8: @@
   * [[https://www.youtube.com/watch?v=8yDML4CbXH0|Tuto Video 1]]
+  * [[https://github.com/saltstack/salt/wiki/Cheat-Sheet|Pense bête rapide]]
 ===== Configurer le master =====
 <code>
@@ Ligne 211: / Ligne 211: @@
 </code>
-===== structure d'un SLS =====
+===== Structure d'un SLS =====
 <code yaml>
 <Include Declaration>:
@@ Ligne 361: / Ligne 361: @@
 </code>
-===== targeting =====
+===== Targeting =====
 https://docs.saltstack.com/en/latest/ref/states/top.html#advanced-minion-targeting
   * globbing sur le nom des minions :
@@ Ligne 577: / Ligne 577: @@
 </code>
+<code>
+{% set name = {
+    'RedHat': 'httpd',
+    'Debian': 'apache2',
+}.get(grains.os_family) %}
+</code>
 ===== Executer un module =====
   * Appeler un module :
@@ Ligne 1188: / Ligne 1195: @@
 **salt-run** est toujours lancé à partir du master !
 </note>
+==== manage ====
+  * Status des minions :
+<xtermrtf>
+$ salt-run manage.status
+down:
+    - portable.localdomain
+up:
+</xtermrtf>
+  * Minions down :
+<xtermrtf>
+$ salt-run manage.down
+- portable.localdomain
+</xtermrtf>
+  * Minions up :
+<xtermrtf>
+$ salt-run manage.up
+- portable.localdomain
+</xtermrtf>
+  * Version du client salstack des minions :
+<xtermrtf>
+$ salt-run manage.versions
+Master:
+.7.3
+Up to date:
+    ----------
+    portable.localdomain:
+.7.3
+</xtermrtf>
 ==== orchestrate ====
 <code yaml>
@@ Ligne 1546: / Ligne 1585: @@
 </code>
+===== Gestion des environnements avec gitfs =====
+Editer le fichier de configuration ''/etc/salt/master.d/gitfs.conf'' :
+<code>
+top_file_merging_strategy: same
+state_top_saltenv: base
+fileserver_backend:
+  #- roots
+  - git
+gitfs_provider: pygit2
+gitfs_remotes:
+  - https://github.com/gigi206/salt-test.git
+</code>
+**roots** correspond aux **file_roots**.
+Chaque tag ou branche est accessible avec saltenv :
+<xtermrtf>
+$ salt '*' state.apply saltenv=test
+$ salt '*' state.apply saltenv=base
+</xtermrtf>
+<note>
+La branche **master** correspond au saltenv **base** !
+</note>
+===== Créer son propre module =====
+https://docs.saltstack.com/en/latest/ref/modules/index.html
+===== Créer son propre state =====
+https://docs.saltstack.com/en/latest/ref/states/writing.html
+===== Créer son propre grain =====
+https://docs.saltstack.com/en/latest/topics/grains/#writing-grains
+===== Client salt en python =====
+https://docs.saltstack.com/en/latest/ref/clients/
+===== Renderer en python =====
+https://docs.saltstack.com/en/latest/ref/renderers/all/salt.renderers.py.html
+===== Vars selon context =====
+<code>
+auth:
+    - __path__ (path to your module dir)
+modules:
+    - __pillar__
+    - __salt__
+    - __opts__
+    - __context__ ({'systemd.sd_booted': True})
+    - __grains__
+runners:
+    - __pillar__
+    - __salt__
+    - __opts__
+    - __grains__
+returners:
+    - __salt__
+    - __opts__
+    - __pillar__
+    - __grains__
+pillars:
+    - __salt__ (modules)
+    - __opts__
+    - __pillar__
+    - __grains__
+# nothing
+tops:
+    - ['__builtins__', '__file__', 'subprocess', 'yaml', '__name__', '__package__', '__doc__']
+outputters:
+    - __opts__
+    - __pillar__
+    - __grains__
+states:
+    - __pillar__
+    - __low__ (lowstate structure?)
+    - __env__
+    - __running__
+    - __lowstate__
+    - __salt__
+    - __opts__
+    - __grains__
+log_handlers:
+    - __path__
+renderers:
+    - __salt__ - Execution functions (i.e. __salt__['test.echo']('foo'))
+    - __grains__ - Grains (i.e. __grains__['os'])
+    - __pillar__ - Pillar data (i.e. __pillar__['foo'])
+    - __opts__ - Minion configuration options
+    - __env__ - The effective salt fileserver environment (i.e. base). Also referred to as a "saltenv". __env__ should not be modified in a pure python SLS file. To use a different environment, the environment should be set when executing the state. This can be done in a couple different ways:
+        Using the saltenv argument on the salt CLI (i.e. salt '*' state.sls foo.bar.baz saltenv=env_name).
+        By adding a saltenv argument to an individual state within the SLS file. In other words, adding a line like this to the state's data structure: {'saltenv': 'env_name'}
+    - __sls__ - The SLS path of the file. For example, if the root of the base environment is /srv/salt, and the SLS file is /srv/salt/foo/bar/baz.sls, then __sls__ in that file will be foo.bar.baz.
+grains:
+    - __salt__
+    - __opts__
+    - __pillar__
+    - __grains__
+</code>
 ===== Debug =====
   * Option debug (**-l debug**) :