868854c2e7
Commit 2b51a6f0c39b4df56823afe9d114dab886e3359e introduced options for gitfs_remotes in a pillar by using a jinja test to see if a parameter is a mapping (dict etc.). This feature however is only available in jinja 2.6 or newer (see http://jinja.pocoo.org/docs/dev/templates/#mapping). Although this version of Jinja is available on Ubuntu, other OS / package managers do provide older versions (2.2.1 in RedHat 6). This change makes use of the "iterable" test which should do the exact same thing.
salt
Yes, Salt can Salt itself!
Note
See the full Salt Formulas installation and usage instructions.
Available states
salt.minion
Install a minion
salt.master
Install a master.
salt.syndic
Install a syndic.
salt.cloud
Install salt cloud.
salt.ssh
Install salt-ssh with roster file. Configure pillar data under salt:ssh_roster to feed the template.
Configuration
Every option available in the templates can be set in pillar.
Settings under 'salt' will be overridden by more specific settings under
salt['master'], salt['minion'] or
salt['cloud']
salt:
ret_port: 4506
master:
user: saltuser
...
minion:
user: saltuser
...
cloud:
providers: ec2
...Extending
Additional templates can be added by the user under salt/files/minion.d and master.d. This might be useful if, for example, a recently-added configuration option is not yet provided by the default template.
Vagrant
Executing the provided Vagrantfile will create a Ubuntu 14.04 VM, add the default Saltstack Repository and install the current stable version.
The folders inside the VM will be set up in a way that enables you to simply execute 'sudo salt "*" state.highstate' to apply the salt formula to the VM, using the pillar.example config. You can check /etc/salt/ for results.
Remember, you will have to run state.highstate or
state.sls salt.(master|minion|cloud) manually.