similar to: #3933 - Option to make puppet fail as soon as a resource fails.

So I''ve done some Mac OS X pkgs for the latest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.24.8 is now available! This is a maintenance release for the 0.24.x branch but contains a small number of new features including some significant performance enhancements for large installations and stored configurations. The tarball is available at: http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz MD5 hash:

0.25.5 changed the default vardir from /var/puppet to /var/lib/puppet and it''s caused the odd issue we have to fix in the Mac pkg preflights. After re-reading ''man hier'' I''m tempted to change the default on OS X to: /var/db/puppet instead. /var/ multi-purpose log, temporary, transient, and spool files ...

Hello... I wanted to be able to startup an EC2 instance with one command and have a fully functioning server without having to shell into each new instance and configure the bits to allow puppet to finish the configuration. Here are some notes I came up with for bootstrapping an ec2 instance with puppet using Ubuntu 10.04. I left out a lot of things about creating and running custom AIM

I''d like to extend my use of puppet to manage my desktop/notebook macs. As others have noted, the hostname of the mobile machines tends to change frequently, so basing the node name (in my site.pp) and the corresponding cert and private key names seems to be an issue. I seem to recall somewhat talking about this at Puppet Camp last week….. Generally my signing strategy is always to

Hi Everyone, I am using Puppet 2.6.5 to configure fresh VMs. These VMs have their hostname set to localhost.localdomain initially at boot-time. There is this script file that runs in rc.local and this is what I do inside it 1. I change the hostname from localhost to xxx.xxxxxx using the hostname command. 2. start the puppet agent as /usr/sbin/puppetd --certname=xxx.xxxxxx

Hi, Why doesn''t puppet resource group tell me who belongs to the group? Given the group such as: mg_team:x:501:smruph, cosman, msmith, mhankey With the command: puppet resource group mg_team only returns: group { ''mg_team'': gid => ''501'', ensure => ''present'' } I was expecting: group { ''mg_team'':

Reminder for Mac Puppeteers going to WWDC How about we meet for lunch at noon on Tuesday. Let''s try to get the table closet to the Odwalla refrigerator, just for reference. We can get more specific on this list on the 8th after we verify the set up. I might even get there a little earlier and put down "reserved" tags. --- Thank you, Allan Marcus Solutions Architect Central

So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync''d to the host it seems when puppetd wakes up and starts its catalog run it doesn''t re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron?

so here are my unorganized thoughts on Passenger settings. * PassengerMaxPoolSize This depends a lot on two primary variables. a) How much RAM you have. b) How much resident memory is needed for your environments/modules. Only way to determine this is with tweaking, and you''ll need to be much more conservative than the suggested settings on the Passenger docs as your app takes up a lot

packages.debian.org is lagging in terms of what it''s showing, but.... $ rmadison -u debian {puppet,facter} | grep unstable puppet | 0.25.4-1 | unstable | source, all facter | 1.5.7-1 | unstable | source, all they''re both up there now. -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

So I can''t quite see how to do this in the existing syntax. Ideally there would be an onlyif parameter for packages, but that doesn''t seem to be the case. I could create a fact that returns true or false depending on whether the file exists, but that doesn''t feel like the right way to do it either. I could do something like: $file_exists =

My custom external nodes script sets the environment variable, but Puppet ignores it. For testing, I have a manifest that deploys this template to a file: environment = <%= environment %> The output from my external nodes script: --- classes: - devhost environment: development parameters: memcached_memory: ''32'' But running "puppetd --test" results in the

Hi I have just put puppet onto a new Ubuntu install and it ran a couple of times but now I get Execution of ''/etc/puppet/etckeeper-commit-pre'' returned 1: whenever puppetd runs. Grepping on etckeeper-commit turns up lots of posts to ubuntu and debian forums about changes made in February. Does anyone know what the story is? I''ve ended up with a screwed pam

I am trying to come up with a workable solution in managing numerous Mac workstations allowing a high degree of flexibility with regards to certs. My puppet environment is setup to application installation on machines that have been ''imaged'' with a base OS and the puppet and facter apps. So, when a Mac is ''imaged'' and subsequently re-booted, puppet is run at

I''m looking at re-working or replacing install.rb from the source distribution to allow more flexible installations, primarily to get MacPorts and Fink packages working but to also work on automatic Mac pkg creation from source. How are people currently using it? Currently the command line options are for options like --no-rdoc, --no-man, --quick, --full, but if you want to specify a

Group - I''m putting a presentation together for $work (a large .gov) and I want to make sure I get my facts (pun intended) straight ... Are the following steps for Facter-Client-Server interaction correct (I have a feeling not): 1. Client puppet run is initiated (via regular schedule, puppetrun, or puppetd) 2. The client contacts the server and downloads any custom facts it does not

Puppet 2.6.14 is a security release in the 2.6.x branch which addresses CVEs 2012-1053 and 2012-1054. All users of Puppet 2.6.x are encouraged to upgrade when possible to Puppet 2.6.14. Other information available at: http://puppetlabs.com/security or visit http://puppetlabs.com/security/cve/cve-2012-1053 and http://puppetlabs.com/security/cve/cve-2012-1053 Detailed feature release notes are

Nigel Kersten and I had previously worked on a plist provider spec for Mac OS X. Attached is a PDF of the current state. I would appreciate any input and criticisms. --~--~---------~--~----~------------~-------~--~----~ 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

Hello, I have 680 hosts reporting into a central puppet server. Yesterday I made a change to site.pp and the nodes/foo.pp and nodes/ bar.pp files to push out some new files (a script to enable LDAP) and it seems that only a handful of stores have downloaded the file and run the script. (I don''t have reporting setup yet other than on a few clients which I did manually) If I ssh into a