similar to: Run a custom function through the ruby debugger

I''m looking for some help in getting the proper escape sequence within the generate function. Ultimately what I''m trying to do is generate some random strings, store them as variables, and use those variables to populate configuration files stored as templates. I can get this to work when applying the template on the localhost, but it fails when applied via the puppet

Almost 4-5% of the total number of nodes are not receiving catalog from the master on an hourly run. We have about 250 nodes. The nodes that are receiving this error are rather random. The hourly cron happens almost at the same time. Is there any configuration changes for Puppet that can be done to avoid this ? Puppet (err): Could not retrieve catalog from remote server: execution expired

Hi All, I would like to pick your brains as to the best way to configure the below senario within puppet. I am currently configuring puppet for our environment and have seperated development/back office from production through configuring roles for each server to identify them as such. What i need to be able todo is have the production servers only update outside of office hours, but have the

Hi all, My current conf splits 188 clients execution in one hour, and puppet runs as a cron job. My server (2cpu 2 GB RAM) runs with mongrel (with 8 puppetmasterd) and this conf works fine. We''d like puppet to run clients all at same time (force a change, i.e.), so we''re testing several things. (Previous conf do not support massive execution). First and most important, is

I have a temporary need to be able to duplicate this function outside of Puppet. How do I strip out the important stuff and make a stand-alone ruby script out of it ? “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- You received this message because you are

Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as

We''re back with a maintenance release: 2.6.5. This release addresses a number of bugs in the 2.6.x branch and adds a handful of features and documentation updates. This release candidate contains fixes for bugs identified in the previous release candidates: - rc1 caused a warning on Ruby 1.8.6 which could cause log pollution. This release candidate no longer generates the warning. - rc1

We''re back with a maintenance release: 2.6.5. This release addresses a number of bugs in the 2.6.x branch. 2.6.5 is a maintenance release in the 2.6.x branch and it contains only bug fixes, documentation updates and a small handful of features. The first release candidate is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.5-rc1.tar.gz We''re

----- Forwarded message from Nick Lewis <nick@puppetlabs.com> ----- Date: Thu, 3 Feb 2011 21:59:10 -0800 From: Nick Lewis <nick@puppetlabs.com> To: puppet-users@googlegroups.com, puppet-dev@googlegroups.com Subject: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available! Message-ID: <AANLkTikjFwZ98P_NcxF54zHbU2mJf15XDrLg2cMp2GWT@mail.gmail.com> We''re back

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site: