Call for Help: Setting up Saltstack for devops of cluster

Jason Wolfe jason at
Mon Dec 1 05:48:05 UTC 2014


Did we have one of havoc/wreck/chaos earmarked to function as the 
master, or did we want an isolated instance running the orchestrating? 
The load for a handful of machines should be next to nothing, so 
dedicated hardware is not required, but an isolated environment would 
likely be best for various reasons including security.

Getting the framework set up should be a day or so of work, but dialing 
in all of the logic to replicate the current state of things and the 
requests in the gist will be a bit longer.  With Salt Helium having just 
gone gold, I think we have a solid release to get things moving.


On 11/30/2014 5:33 PM, Craig Rodrigues wrote:
> Hi,
> As part of setting up, I have set up several VM's
> across different machines.  I am quickly finding that it
> is a lot of work to do config management of the cluster by hand with ad
> hoc scripts.
> I would like to use a more modern and off-the-shelf devops framework to
> do this.  I've written down my rough requirements here:
> I'm leaning towards using Saltstack (vs. Chef, Puppet, Ansible,
> CFEngine, whatever) because:
>      -> Saltstack seems to have an active community with many companies
>           using it
>      -> Saltstack is implemented in Python, and I have a slight bias
>            towards Python things :)
>      -> Kevin Bowling at Limelight Networks told me he had good
>          experiences with at, and the Limelight guys are generally cool :)
> Is there anyone with Saltstack experience who can help
> set this up in the Jenkins cluster, based on the requirements that I
> have written above?  I want to lay the groundwork
> for being able to grow the Jenkins cluster to tens or even
> hundreds of VM's or bare metal nodes if that makes sense to do so in
> the future.
> Please send followup responses to freebsd-testing at
> <mailto:freebsd-testing at> (
> )
> Thanks.
> --
> Craig

The information in this message may be confidential.  It is intended solely 
the addressee(s).  If you are not the intended recipient, any disclosure,
copying or distribution of the message, or any action or omission taken by 
in reliance on it, is prohibited and may be unlawful.  Please immediately
contact the sender if you have received this message in error.

More information about the freebsd-testing mailing list