Date: Sun, 30 Nov 2014 16:33:09 -0800 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Cc: Kevin Bowling <kbowling@llnw.com>, Christer Edwards <christer.edwards@gmail.com>, Sean Bruno <sbruno@llnw.com>, Jeremy Singletary <jsingletary@llnw.com>, Jason Wolfe <jason@llnw.com>, Chris Christensen <cchristensen@llnw.com> Subject: Call for Help: Setting up Saltstack for devops of jenkins.freebsd.org cluster Message-ID: <CAG=rPVeO4L9MPzN1v%2BUrhYKo4gACrfdUaLsHWJ-uEcfCAQQf6g@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, As part of setting up http://jenkins.freebsd.org, 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: https://gist.github.com/rodrigc/b5d70a26f748a2a5d33b 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@freebsd.org ( https://lists.freebsd.org/mailman/listinfo/freebsd-testing ) Thanks. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVeO4L9MPzN1v%2BUrhYKo4gACrfdUaLsHWJ-uEcfCAQQf6g>