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. On Tue, Jun 14, 2016 at 7:52 AM Martin Alfke <tux...@gmail.com> wrote:
> Most implementations make use of config_version setting in > environment.conf (or globally in puppet.conf) to identify systems with > outdated puppet code > > On 14 Jun 2016, at 13:50, Geoff Galitz <ggal...@shutterstock.com> wrote: > > > > > > > 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 > > > > > > > > On Tue, Jun 14, 2016 at 1:42 PM, Peter M Souter <p.mor...@gmail.com> > wrote: > > 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 :) > > > > > > On Tuesday, 14 June 2016 11:49:01 UTC+1, Geoff Galitz wrote: > > > > 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 > > > > > > -- > > 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+unsubscr...@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. > > > > > > > > -- > > > > > > Geoff Galitz, Systems Engineer > > Shutterstock GmbH > > Greifswalder Strasse 212 > > Aufgang F, 2 Hof > > 10405 Berlin > > > > > > -- > > 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+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CABiayTB8GbcepTGk416RRJRCAYjogUssyszcv4ZwD3fm3sH%2BXw%40mail.gmail.com > . > > For more options, visit https://groups.google.com/d/optout. > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/3C0552E2-E0CB-4745-8D8D-86F6ECE08F27%40gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2BnEbkY%2BCTG4wKVMyHT214Q%3Dz1Xd1YQh4HB3ZALZhvA-1%2Bying%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
