john
/
vagrant-saltlab
mirror of https://github.com/jbowdre/vagrant-saltlab.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
A small Vagrant lab environment for learning Salt
40 Commits 2 Branches 0 Tags 74 KiB
Vim Script 44.2%
SaltStack 35.6%
HTML 20.2%
Go to file
John Bowdre a58f8fcc1f minor reorg 
- move content to be served via gitfs to salt_content/gitfs
- create structure to hold local content at salt_content/local
- configure Vagrant to rsync salt_content/local to /srv on Salt master
 		2023-04-08 21:03:29 -05:00
salt_content minor reorg 2023-04-08 21:03:29 -05:00
.gitignore add gitignore 2023-03-14 13:57:58 -05:00
README.md start playing with top.sls 2023-03-24 17:12:03 -05:00
Vagrantfile minor reorg 2023-04-08 21:03:29 -05:00

README.md

vagrant-saltlab

Using Vagrant to run a portable Salt lab environment on my Chromebook. The included Vagrantfile spawns a environment with a single Salt Master (named salt) and four Salt Minions (named minion##) running a few different common Linux distributions for learning, testing, and development. It leverages the libvirt provider to interact with native Linux virtualization, and has a few tweaks to work around limitations imposed by running this all within ChromeOS's LXC-based Linux development environment.

To make it easier to deploy, test, break, tear down, and redeploy the environment:

  1. The Salt master blindly auto-accepts all minion keys.
  2. The minions register the roles:saltlab grain to aid in targeting.
  3. The contents of srv/ get rsynced to /srv/ when the master starts up. Note that this is a one-way rsync from host to VM (and not the other way around), so make sure to write your Salt content on the host and use vagrant rsync to push changes into the VM.

Usage

Provision the virtual environment:

vagrant up

The master and four minions will be deployed; this will take a few minutes. Once complete, you can verify status with vagrant status:

; vagrant status
Current machine states:

salt                      running (libvirt)
minion01                  running (libvirt)
minion02                  running (libvirt)
minion03                  running (libvirt)
minion04                  running (libvirt)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run `vagrant status NAME`.

Access an SSH shell on the master with vagrant ssh salt:

; vagrant ssh salt
Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-139-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage
vagrant@salt:~$

Verify that all the minion keys have been automatically accepted by the master (this is a lab environment, after all):

vagrant@salt:~$ sudo salt-key -L
Accepted Keys:
minion01
minion02
minion03
minion04
salt
Denied Keys:
Unaccepted Keys:
Rejected Keys:

Make sure all the minions are responding correctly:

vagrant@salt:~$ sudo salt '*' test.ping
salt:
    True
minion03:
    True
minion02:
    True
minion01:
    True
minion04:
    True

Happy Salting!

Cleanup

To blow it all away for a fresh start, just run vagrant destroy -f.