Skip to content
Playground to work in the snapper module before it gets upstreamed
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
srv/salt Some refactor. Pylint fixes and unit tests Jul 25, 2016
tests/unit/modules Some refactor. Pylint fixes and unit tests Jul 25, 2016
vagrant/salt mounting /srv/salt conflicts with the package, better configure it Feb 23, 2016
.gitignore ignoring vim .swp files Jun 8, 2016
README.md
Vagrantfile

README.md

(openSUSE) Vagrant Salt Playground

This Vagrantfile starts 1 master and three minions.

  • The master/minions are deployed with salt (meta-salt?) using the /vagrant/salt recipes

  • Everything in /vagrant/salt (/vagrant/vagrant/salt inside the VMs) is used only for the initial deployment.

  • Everything in /srv/salt (/vagrant/srv/salt, symlinked to /srv/salt) can be used to play with modules and states.

Usage

vagrant up

This will start one master and 3 minions. The base image is opensuse/openSUSE-42.1-x86_64. The salt packages are not the ones in Leap but the ones the SUSE maintains in systemsmanagement:salstack which may be a bit newer than Leap.

Once the base box is booted, the salt recipes in vagrant/salt will bootstrap the master, expose its IP via SLP, and configure the minions to point to this IP. The states in vagrant/salt are only using for the initial bootstrapping.

The master will be configured with file_root point to /vagrant/srv/salt which is the folder srv/salt outside of the VM. That is the folder where you can put states for the minions.

Author

You can’t perform that action at this time.