Call for Help: Setting up Saltstack for devops of jenkins.freebsd.org cluster

[Craig Rodrigues]

On Sun, Nov 30, 2014 at 9:39 PM, Jason Wolfe <jason at llnw.com> wrote:

> Craig,
>
> 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.
>
> Jason
>
>
Jason,

We don't have a host earmarked as the master.  For now can we pick "havoc"?
Is it relatively easy to change later on?

--
Craig


On Mon, Dec 1, 2014 at 10:52 AM, Johannes Meixner <xmj at freebsd.org> wrote:

>
> Do we have a description on which host functions how? I.e. which of those
> mentioned is salt-master, which are buildslaves?
>
> Are there already any salt files? Do we want to use the Jenkins formula
> https://github.com/saltstack-formulas/jenkins-formula, how much do we
> need to
> extend it, or sould we start writing our own NIH solution ? ;-)
>

Johannes,

We have a list of machines in the Jenkins cluster here:
https://wiki.freebsd.org/Jenkins/MachineList
We don't have a designated saltstack master, but for now I would say we can
use "havoc".

In terms of the saltstack Jenkins formula, I don't know if it makes since
to use it or not.

Right now, the main Jenkins host ( jenkins.freebsd.org ) has Jenkins via:
   -> pkg install jenkins
           -> some entries in rc.conf like jenkins_enable="YES"

 jenkins.freebsd.org is also running an nginx server configured with a
reverse proxy:

https://wiki.freebsd.org/Jenkins#References


Take a look at https://gist.github.com/rodrigc/b5d70a26f748a2a5d33b
carefully and look at those requirements.

--
Craig