Template

Yes, Salt can Salt itself! https://github.com/saltstack-formulas/salt-formula/

Go to file Use this template

Matthew X. Economou 827ed47a25 Filter all calls to formulas_git_opt through load_yaml Jinja macros are not actually functions. The only thing they can return is a string. In order to return structured data, the callee must serialize it, and the caller must deserialize it. This state formula uses YAML as the intermediary, hence the occurrence of both the `\|yaml` (callee) and `\|load_yaml` (caller) filters in its code. The post-render "mapping values are not allowed here" error in salt/formulas.sls or the broken rendering of salt/files/master.d/f_defaults.conf happens because invocations of the `formulas_git_opt` macro in several Jinja `set` statements do not get deserialized, resulting in the trailing newline followed by three dot characters (`...`), which YAML uses to signal the end of a document. Correcting these rendering errors requires adding the necessary deserialization code at those locations (i.e., filtering the macro call through `\|load_yaml`).		2015-09-03 14:56:45 -04:00
dev	optimized setup bootstrap	2015-04-23 11:08:39 +02:00
salt	Filter all calls to formulas_git_opt through load_yaml	2015-09-03 14:56:45 -04:00
.gitignore	Added a Vagrant setup to instantly test the formula	2014-10-16 17:30:04 +02:00
LICENSE	Update LICENSING year	2015-03-20 20:05:04 -04:00
pillar.example	Revert "Install cherrypy/tornado from pip only if use_pip is True."	2015-07-20 17:05:56 -05:00
README.rst	Revert "Advance sal/api.sls, install rest_cherrypy or rest_tornado from pip."	2015-07-20 17:05:57 -05:00
Vagrantfile	Added a Vagrant setup to instantly test the formula	2014-10-16 17:30:04 +02:00

README.rst

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.

`salt.api`

Install salt api Requisite: Configure salt-master with rest_cherrypy or rest_tornado.

`salt.standalone`

Install a minion and configure it in standalone mode.

`salt.gitfs.dulwich`

Install gitfs backend dulwich dependencies. Set salt:master:gitfs_provider: dulwich in your pillar.

salt.gitfs.gitpython ----------------------

Install gitfs backend GitPython dependenciess. Set salt:master:gitfs_provider: gitpython in your pillar.

`salt.gitfs.pygit2`

Install gitfs backend libgit2/pygit2 dependenciess. Set salt:master:gitfs_provider: pygit2 in your pillar. For EL distributions, pygit is installed from packages from EPEL.

`salt.pkgrepo`

Enable the official saltstack package repository in order to always benefit from the latest version. This state currently only works on Debian and Ubuntu, and aims to implement the installation recommendations of the official documentation.

On EL distributions, the official Salt COPR for ZeroMQ 4. Salt itself is installed via EPEL.

`salt.pkgrepo.absent`

Undo the effects of salt.pkgrepo.

`salt.formulas`

Clone selected Salt formulas Git repositories under /srv/formulas and makes them available in the relevant file_roots settings. Pillar data can be used to customize all paths, URLs, etc.

Here's a minimal pillar sample installing two formulas in the base environment.

salt_formulas:
  list:
    base:
      - salt-formula
      - openssh-formula

See pillar.example for an exhaustive list of settings available via pillar. Note that by default this state:

downloads the latest formulas from the saltstack-formulas project on GitHub.
does not update the local repositories after the initial clone. This is a safety measure since you do not control how the official repositories evolve.

If you configure the state to download the formulas from repositories that you control, then you can safely enable the salt_formulas:git_opts:default:update pillar setting to True.

`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.