Keeping compile masters consistent

31 views
Skip to first unread message

Geoff Galitz

unread,
Jun 14, 2016, 6:49:01 AM6/14/16
to puppet...@googlegroups.com

Hi folks.

I'm curious what approaches you take towards making sure the puppet tree is consistent across distributed compile masters?  In PE this would be code manager's job, I believe.  What do the FOSS folks use?

I was contemplating using zookeeper for this.

-G


--


Geoff Galitz, Systems Engineer
Shutterstock GmbH
Greifswalder Strasse 212
Aufgang F, 2 Hof
10405 Berlin

Peter M Souter

unread,
Jun 14, 2016, 7:42:25 AM6/14/16
to Puppet Users
I've seen a few ways of doing this:

- Running lsyncd to watch for changes to code on the MoM
- Rsync task on demand when the master is updated, maybe with something like incrond or just with scripting or Jenkins tasks
- The R10K mco task from acidprime/r10k https://github.com/acidprime/r10k#mcollective-support

You can probably go for something more heavyweight with glusterfs, but I like to keep it simple :)

Geoff Galitz

unread,
Jun 14, 2016, 7:50:09 AM6/14/16
to puppet...@googlegroups.com


Cool.. I'm specifically interested in knowing how people  deal with compile servers that do not update their local version of the puppet tree properly and how to prevent them serving stale or broken catalogs.

-G



--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ad4530c7-7ef8-4baa-9b12-935155eea26d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Martin Alfke

unread,
Jun 14, 2016, 7:52:29 AM6/14/16
to puppet...@googlegroups.com
Most implementations make use of config_version setting in environment.conf (or globally in puppet.conf) to identify systems with outdated puppet code
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABiayTB8GbcepTGk416RRJRCAYjogUssyszcv4ZwD3fm3sH%2BXw%40mail.gmail.com.

Matthew Nicholson

unread,
Jun 14, 2016, 8:32:12 AM6/14/16
to puppet...@googlegroups.com
We push r10k runs via consul execs from Jenkins, and after and only after a successful update, invalidate the environment cache(for the given environment), so even if a deploy fails , the master(s) will keep serving the "old" version as opposed to an incomplete deploy.
Reply all
Reply to author
Forward
0 new messages