Re: [Puppet Users] Did PE 3.7 kills r10k?

2014-12-27 Thread chris mague
Vadym, I ran into the same problem and was able to work around as follows with the caveat that it's unsupported: sudo su - pe-postgres psql \connect pe-classifier select * from groups; # write everything down update groups set environment_name='agent-specified' where environment_name='productio

Re: [Puppet Users] HA puppetmaster in AWS

2014-07-18 Thread chris mague
I used this approach detailed below in production for a large-ish environment. When used in conjunction with Nginx load balancing in AWS (http://blog.mague.com/?p=286) it worked very well. 1) Route all certificate requests (explained above) to a pair of boxes that have the sync setup listed bel

[Puppet Users] PuppetDB certificate signature failure for /CN=puppetdb

2013-01-16 Thread chris mague
I regenerated the puppetdb certs according to the instructions here: Step 3, Option B https://docs.puppetlabs.com/puppetdb/0.9/install_from_source.html#step-3-option-b-manually-create-a-keystore-and-truststore And can verify the cert manually using openssl client #echo "QUIT" | openssl s_client

[Puppet Users] Re: Variable scope changes in 2.6.4

2011-03-16 Thread chris mague
On Mar 16, 9:03 am, Felix Frank wrote: > On 03/16/2011 04:37 PM, chris mague wrote: > > > > > > > > > > > How do I define and use variables in 2.6.4? > > Setting global variables worked in previous versions and I understand > > this has chang

[Puppet Users] Variable scope changes in 2.6.4

2011-03-16 Thread chris mague
How do I define and use variables in 2.6.4? Setting global variables worked in previous versions and I understand this has changed, but am unsure how to make the following work. site.pp = import "dev_nodes.pp" node default { include tmpfiles } dev_nodes.pp ==

[Puppet Users] 2.6.2 defunct processes

2011-02-09 Thread chris mague
I'm running 2.6.2 both client and server and am having a problem with defunct processes for sh and gem on the clients. Right now I see 715 of them. Restarting the puppet daemon nightly helps, but I would prefer to fix this. root 21667 1 0 11:11 ?00:01:20 /usr/bin/ruby1.8 /usr/ s

[Puppet Users] Re: 2.6.2 excluding an exported resource

2011-02-04 Thread chris mague
possible in 2.6.4 by doing Host <<| tag == "stagehosts" and title != $fqdn |>> but I'm on 2.6.2 -c On Feb 4, 7:22 am, jcbollinger wrote: > On Feb 3, 3:24 pm, chris mague wrote: > > > > > I have the class below to export host entries. > > H

[Puppet Users] 2.6.2 excluding an exported resource

2011-02-03 Thread chris mague
I have the class below to export host entries. However I wish to override the entry for my host to 127.0.0.1 So for all of the hosts other than foo.bar.com I would like them to have the real IP address but for foo.bar.com I would like to just have the loopback host entry. 2.6.2 doesn't allow mult

[Puppet Users] Re: Using puppet to redeploy staging app

2011-01-14 Thread chris mague
On Jan 14, 2:27 pm, Romain Pelisse wrote: > > It depends on how you deploy your applications. > > > In the case of packaged applications I do the following after tests > > pass in Hudson: > > > 1) using extconf to specify versions and overwrite the package version > > of the file with a script >

[Puppet Users] Re: Using puppet to redeploy staging app

2011-01-14 Thread chris mague
On Jan 14, 1:41 pm, Romain Pelisse wrote: > Hi, > > I'm building a staging environement and I would like it to be able to > redeploy automatically, after each commit - or every hour, some > applications. Those applications are right now deployed and set up by > puppet. I wonder if I should use pup

[Puppet Users] Re: Large hierarchy of files?

2010-11-12 Thread chris mague
On Nov 10, 2:09 pm, ericlee748 wrote: > Hey guys, > > I have a large hierarchy of files that are set up to recursively copy > from my puppet master. It takes a long while to copy these files over > to the clients - roughly 1 hour. Only 1 or 2 files in the hierarchy > will ever change. Is there a b

[Puppet Users] stages and modules

2010-11-08 Thread chris mague
I am trying to implement stages in 2.6.2 (both client and server) stage { [baseos, pre, post, brsoft]: } class runstages { Stage[baseos] -> Stage[pre] -> Stage[main] -> Stage[post] -> Stage[brsoft] } node default { include runstages include debian::base_packages