Re: [Puppet Users] Concat Module posted to Onyx Point Github.

Hi Trevor Thanks for the module. I've been testing out the concat module, thanks, but the only issue I see is files keep getting 'executed successfully' each round. Is there any way to not have it do this? I haven't really looked that your ruby logic yet. -- You received this message because

[Puppet Users] Re: Ensure a package is newer than version X

Check out yum-versionlock for RHEL/CentOS, its a yum plugin. We use it to lock down versions and then just have ensure => latest in our manifests.. Regards, Josh On May 24, 8:26 pm, Felix Frank wrote: > On 05/17/2011 09:37 PM, Doug Warner wrote: > > > On Gentoo we would handle this by putting a

[Puppet Users] Changing up some things around Puppet Labs's Open Source Software

One of the largest challenges we've continually faced at Puppet labs is trying to find a good balance in splitting the development team's time between the (currently small amount of) commercial software, and the (much larger amount of) open source software. This balancing act has, unfortunately, a

Re: [Puppet Users] enabling of 'thin_storeconfigs'

On Wed, May 25, 2011 at 11:52 AM, Patrick wrote: > > I'd avoid any version of puppet that ends in a "0" like the plague if you > want stability. The project has been steadily improving in this regard, but it's definitely been a problem. I have great hopes for 2.7.0 though, and the more people

[Puppet Users] Problem with Facter 1.5.9 on Ubuntu

It looks like there's a fairly critical bug with Facter 1.5.9, when it comes to Ubuntu[1]. Facter ends up reporting the wrong value for 'operatingsystem', which can cause problems with the manifest. If you're dependent on being able to switch in your manifests based on Ubuntu vs Debian, then you

[Puppet Users] Re: Managing netgroups in /etc/passwd with Puppet via Augeas

Hmm, I think I may have found a more tractable approach in the template() and inline_template() functions. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from th

Re: [Puppet Users] Client updates

On 05/25/2011 01:12 PM, Douglas Garstang wrote: > I probably waste quite a bit of time each week restarting the puppet client, > and logging systems, and tailing the messages file, to see if my puppet > changes worked. Is there a better way? How do people normally do this? > > Sure, I can use pupp

Re: [Puppet Users] Variable inheritance in Stages

On Tue, May 24, 2011 at 9:46 AM, Chip Schweiss wrote: > The pre classes are definately getting defined before the variable is being > declared in my node definition: > > node 'deploy.nrg.mir' { >     $deployment = true >     $deploy_environment = "development" >     $deploy_hostname = "testhost" >

Re: [Puppet Users] Variable inheritance in Stages

The pre classes are definately getting defined before the variable is being declared in my node definition: node 'deploy.nrg.mir' { $deployment = true $deploy_environment = "development" $deploy_hostname = "testhost" $deploy_fqdn = "testhost.nrg.mir" $deploy_netadapters = "2"

[Puppet Users] Managing netgroups in /etc/passwd with Puppet via Augeas

Hi all, I'm relatively new to both Puppet and Augeas. I'm currently stuck trying to figure out how to manage hosts' netgroup entries in /etc/ passwd. I've got it working to ensure a single specified netgroup is the only one in /etc/passwd: class ldap { define netgroups { augeas { "net

Re: [Puppet Users] Client updates

Douglas, I have to concur with disconnect, now that we are using Foreman, many of the things we setup in the past to catch these things are now redundant. I don't know why you "don't like" Foreman, but I have to say along with our initial decision to use puppet, and managing our configs with versi

Re: [Puppet Users] changing the default key length and hash

Just noting that we are moving forward on the original ticket. It does appear that we've drifted onto other issues, I'd like to remind people to please file bugs/feature requests on those so we don't lose track of them. On Wed, May 25, 2011 at 12:41 PM, Daniel Pittman wrote: > On Wed, May 25,

Re: [Puppet Users] changing the default key length and hash

On Wed, May 25, 2011 at 10:23, Jennings, Jared L CTR USAF AFMC 46 SK/CCI wrote: >> Ah.  I was thinking in the broader scope of getting us away from >> insecure hashes elsewhere in the product.  From a strictly certificate >> POV, indeed, it should be just fine. > > I'm trying to configure FIPS-com

Re: [Puppet Users] Output of "puppet master --compile"

I think that putting "--no-verbose" might work, but I can't test it. On May 25, 2011, at 12:18 PM, Yushu Yao wrote: > Hi Experts, > > When I use puppet master --compile, it will spit out some notice information > to the beginning of the output: > > # puppet master --manifest root/tt.pp --com

[Puppet Users] Output of "puppet master --compile"

Hi Experts, When I use puppet master --compile, it will spit out some notice information to the beginning of the output: # puppet master --manifest root/tt.pp --compile vm_0009_270e41c5-4242-416d-80ad-38dc85469076 notice: Compiled catalog for vm_0009_270e41c5-4242-416d-80ad-38dc

Re: [Puppet Users] enabling of 'thin_storeconfigs'

On May 25, 2011, at 10:23 AM, Nathan Clemons wrote: > So if Nagios configs are the only thing you use stored configs for, thin > stored configs will work just fine? > > If so, I forsee a switch in our future. :) > > Also, since you mentioned it... how difficult is it to upgrade from 0.25 to >

Re: [Puppet Users] enabling of 'thin_storeconfigs'

On 11-05-25 01:28 PM, Nigel Kersten wrote: > On Wed, May 25, 2011 at 10:23 AM, Nathan Clemons > wrote: > > So if Nagios configs are the only thing you use stored configs for, > thin stored configs will work just fine? > > If so, I forsee a switch in our f

Re: [Puppet Users] Client updates

Foreman can email error reports automatically. (Without having to use the GUI..) IIRC you can also make it email actions (changes) - if not, it shouldn't be that hard to add. We use nagios to check puppet's state file for age - if it is too old, puppet hasn't run. Between those two, afaict, we're

Re: [Puppet Users] Client updates

On Wed, May 25, 2011 at 10:40 AM, Brian Gupta wrote: > On Wed, May 25, 2011 at 1:29 PM, Douglas Garstang > wrote: > > On Wed, May 25, 2011 at 10:22 AM, Brian Gupta > > wrote: > >> > >> Basically the ways I know of: > >> > >> 1) Don't run puppet as a daemon, but run it out of cron every X mins. >

Re: [Puppet Users] Client updates

It depends on how you use it. In our environment, we don't leave the Puppet daemon running. We only do on-demand runs... that way changes only happen when we push them out. Your mileage obviously may vary, but if you're looking for tight control, that's something to consider. -- Nathan Clemons ht

Re: [Puppet Users] enabling of 'thin_storeconfigs'

On Wed, May 25, 2011 at 10:23 AM, Nathan Clemons wrote: > So if Nagios configs are the only thing you use stored configs for, thin > stored configs will work just fine? > > If so, I forsee a switch in our future. :) > > Also, since you mentioned it... how difficult is it to upgrade from 0.25 to >

Re: [Puppet Users] Client updates

On Wed, May 25, 2011 at 1:29 PM, Douglas Garstang wrote: > On Wed, May 25, 2011 at 10:22 AM, Brian Gupta > wrote: >> >> Basically the ways I know of: >> >> 1) Don't run puppet as a daemon, but run it out of cron every X mins. >> 2) Setup a cronjob that checks if puppet is running and restart it i

Re: [Puppet Users] Client updates

On Wed, May 25, 2011 at 10:35 AM, Nathan Clemons wrote: > Mcollective hides successes and only shows you failures, keeping the signal > to noise ratio very high. > > If you run puppet without daemonizing, anything that causes the config to > not be applied successfully is going to show up as an er

Re: [Puppet Users] Client updates

Mcollective hides successes and only shows you failures, keeping the signal to noise ratio very high. If you run puppet without daemonizing, anything that causes the config to not be applied successfully is going to show up as an error. -- Nathan Clemons http://www.livemocha.com The worlds larges

Re: [Puppet Users] Client updates

On Wed, May 25, 2011 at 10:26 AM, R.I.Pienaar wrote: > > > - Original Message - > > Basically the ways I know of: > > > > 1) Don't run puppet as a daemon, but run it out of cron every X mins. > > 2) Setup a cronjob that checks if puppet is running and restart it if > > not. > > 3) Setup a

RE: [Puppet Users] Client updates

>-Original Message- >From: puppet-users@googlegroups.com >[mailto:puppet-users@googlegroups.com] On Behalf Of Brian Cully >Sent: Wednesday, May 25, 2011 11:16 AM >To: puppet-users@googlegroups.com >Subject: Re: [Puppet Users] Client updates > >On May 25, 2011, at 1:12 PM, Douglas Garstang

Re: [Puppet Users] Client updates

On Wed, May 25, 2011 at 10:26 AM, Nathan Clemons wrote: > Mcollective with mc-puppet should work if you patch it to not daemonize > (you'll need to adjust the timeouts as well, of course). Errors running will > bubble up to the list of nodes that failed the run. > > Failed both for syntax erro

Re: [Puppet Users] Client updates

On Wed, May 25, 2011 at 10:22 AM, Brian Gupta wrote: > Basically the ways I know of: > > 1) Don't run puppet as a daemon, but run it out of cron every X mins. > 2) Setup a cronjob that checks if puppet is running and restart it if not. > 3) Setup a nagios job that checks to see if puppet is runnin

Re: [Puppet Users] Client updates

- Original Message - > Basically the ways I know of: > > 1) Don't run puppet as a daemon, but run it out of cron every X mins. > 2) Setup a cronjob that checks if puppet is running and restart it if > not. > 3) Setup a nagios job that checks to see if puppet is running > 4) Presuming you

Re: [Puppet Users] Client updates

Mcollective with mc-puppet should work if you patch it to not daemonize (you'll need to adjust the timeouts as well, of course). Errors running will bubble up to the list of nodes that failed the run. -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community

RE: [Puppet Users] changing the default key length and hash

> Ah. I was thinking in the broader scope of getting us away from > insecure hashes elsewhere in the product. From a strictly certificate > POV, indeed, it should be just fine. I'm trying to configure FIPS-compliant servers, and I've run into segfaults thrown by the Ruby interpreter when Puppet

Re: [Puppet Users] enabling of 'thin_storeconfigs'

So if Nagios configs are the only thing you use stored configs for, thin stored configs will work just fine? If so, I forsee a switch in our future. :) Also, since you mentioned it... how difficult is it to upgrade from 0.25 to 2.6 / 2.7? I've been curious to upgrade but for the most part everyth

Re: [Puppet Users] Client updates

Basically the ways I know of: 1) Don't run puppet as a daemon, but run it out of cron every X mins. 2) Setup a cronjob that checks if puppet is running and restart it if not. 3) Setup a nagios job that checks to see if puppet is running 4) Presuming you are managing your puppet code in some sort o

Re: [Puppet Users] Client updates

On Wed, May 25, 2011 at 10:16 AM, Brian Cully wrote: > On May 25, 2011, at 1:12 PM, Douglas Garstang wrote: > > > I probably waste quite a bit of time each week restarting the puppet > client, and logging systems, and tailing the messages file, to see if my > puppet changes worked. Is there a bet

Re: [Puppet Users] Client updates

On May 25, 2011, at 1:12 PM, Douglas Garstang wrote: > I probably waste quite a bit of time each week restarting the puppet client, > and logging systems, and tailing the messages file, to see if my puppet > changes worked. Is there a better way? How do people normally do this? I use mo

Re: [Puppet Users] enabling of 'thin_storeconfigs'

On 11-05-22 05:22 AM, Brice Figureau wrote: > On 22/05/11 01:10, Gabriel Filion wrote: >> Hello, >> >> I found out that a puppetmaster I manage is currently not using the >> thin_storeconfigs option and suggested to the other admins that we use >> this in order to reduce puppet run times a little.

[Puppet Users] Client updates

I probably waste quite a bit of time each week restarting the puppet client, and logging systems, and tailing the messages file, to see if my puppet changes worked. Is there a better way? How do people normally do this? Sure, I can use puppetrun or mcollective to cause puppet to do a config run on

Re: [Puppet Users] mode on private_keys file for nagios / func integration

On Wed, May 25, 2011 at 7:11 AM, Chris Phillips wrote: > Hi, > > I've successfully hooked up func to use the puppet certs, mostly nicely. > I'm now looking at using func to perform nagios checks (instead of > installing nrpe, which is more pants than func). Here the nagios service > runs as the n

[Puppet Users] mode on private_keys file for nagios / func integration

Hi, I've successfully hooked up func to use the puppet certs, mostly nicely. I'm now looking at using func to perform nagios checks (instead of installing nrpe, which is more pants than func). Here the nagios service runs as the nagios user, and so func also runs as that user, I thought I was sort

[Puppet Users] facter 1.5.9 does not display lsbmajdistrelease

Hi all, few time ago I already asked about lsbmajdistrelease. https://groups.google.com/group/puppet-users/browse_thread/thread/9432108a8835f09a The solution to my previous problems was installing redhat-lsb. It worked fine, but facter 1.5.9 misses lsbmajdistrelease again, even with redhat-lsb i

Re: [Puppet Users] Puppet fileserver path

thanks Peter On Wed, May 25, 2011 at 6:10 PM, Peter Bukowinski wrote: > On Wednesday, May 25, 2011 at 8:10 AM, Sumith Sudhakaran wrote: > Hi, > > > > Is it possible, to change the default puppet file server path. > > > > [files] > > path /var/lib/puppet/files > > > > > > -- > > Regards > > > >

[Puppet Users] Re: Applying Catalogs

On May 24, 5:18 pm, Yushu Yao wrote: > Thanks John, > > My case is a little bit different. Because my webserver might need the IP > address of the mysql node, and before mysql node is deployed and configured, > it's IP address is not known. As Peter wrote, you can probably use an exported resou

[Puppet Users] Re: PC EU feedback: unpack array variables in string interpolation

On May 24, 8:54 pm, vagn scott wrote: > What should this do? > >      $array = [ "one", "two" ] >      $greeting = [ "hello", "howdy" ] >      @file { "host_$array$greeting" } > > or this? > >      $array = [ "one", "two" ] >      @file { "$array_blah" } > > seems like we would need delimiters >

Re: [Puppet Users] Puppet fileserver path

On Wednesday, May 25, 2011 at 8:10 AM, Sumith Sudhakaran wrote: Hi, > > Is it possible, to change the default puppet file server path. > > [files] > path /var/lib/puppet/files > > > -- > Regards > > Sumith Yes. You can any location / multiple locations in /etc/puppet/fileserver.conf. I us

[Puppet Users] Re: problem with rack versions and puppet-dashboard

On May 24, 11:48 am, David Klann wrote: > On Tue, 24 May 2011 10:40:03 -0500, you said: > > > I get this error > > can't activate rack (~> 1.0.1), already activated rack-1.2.2 > > > It appears that puppet-dashboard uses rack 1.0.1 but passenger 3.0.7 > > needs to use rack1.2.2 > > > Is there a w

[Puppet Users] Puppet fileserver path

Hi, Is it possible, to change the default puppet file server path. *[files] path /var/lib/puppet/files* -- * Regards*** * Sumith** * -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googl

Re: [Puppet Users] Template conditionals

On Tue, May 24, 2011 at 9:06 AM, Aaron Grewell wrote: > Argh, I'll have to take that back.  The docs are right, the quotes are in > fact necessary.  Without them has_variable will always return false. My bad, responded in haste. Unquoted in ruby is actually a variable, so no that wouldn't work co

Re: [Puppet Users] Re: Cross-module dependencies

Glad to hear it worked. On May 24, 2011, at 11:40 PM, treydock wrote: > I don't have that directory. However I came across this module > https://github.com/camptocamp/puppet-sudo which among many things > enlightened me to the new feature in sudo-1.7.2+ of using includedir > and /etc/sudoers.d t