https://github.com/srevenant/salt-master

Run Salt Master as a container
https://github.com/srevenant/salt-master

alpine centos master salt salt-master saltstack

Last synced: about 1 month ago
JSON representation

Run Salt Master as a container

• Host: GitHub
• URL: https://github.com/srevenant/salt-master
• Owner: srevenant
• Created: 2017-07-07T14:01:59.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2019-08-15T20:14:35.000Z (over 5 years ago)
• Last Synced: 2024-10-11T20:16:34.655Z (3 months ago)
• Topics: alpine, centos, master, salt, salt-master, saltstack
• Language: Shell
• Size: 1.95 KB
• Stars: 1
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# salt master

This is an example of how to leverage containers even for things such as a salt master.

This is intended as a reference, run as a swarm service, on a single node with local storage (or shared if you want to put it into a cluster).

Stackfile is: salt-master.yml

Four volumes are used to track state between restarts, in `salt-master.yml`,

which could be located anywhere outside the container, such as `/data/salt-master`:

    mkdir -p /data/salt-master/pki

    mkdir -p /data/salt-master/log

    mkdir -p /data/salt-master/cache

    mkdir -p /data/salt-master/master.d

Create the service with:

    docker swarm init

    docker stack deploy -c salt-master.yml salt

Update the service with:

    docker build -t salt-master . && \

        docker service update salt_master --image=salt-master --force

(one might suggest you have a CI system trigger this command on a merge to a git repo)

Files located in bin/ are meant to be run from the outside host, to reach inside the container.

If working in AWS, consider [Oz Boostrap](https://github.com/srevenant/oz) as a way to setup the foundations for your network,

before bringing a tool like saltstack online (a pre-provisioning bootstrap script)