search for: mceniri

I know someone completed this but I''m not sure the hows and whats of it. Can someone put up a doc or email about this?

Ok, so I''m obviously doing something wrong here. This is running puppet 0.22.2 on a centos 4 update 4 box. When I try running this test - mount { bigdisk: ensure => mounted, device => ''bigserver:/bigdisk'', fstype => nfs, name => ''/bigdisk'', dump => "0", pass => "0", options =>

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

I''m trying to come up with a way to manage /etc/puppet on the Puppet server from my workstation. My idea was to place all of /etc/puppet into subversion, check it out to my workstation, commit via ssh, and then use a post-commit to update /etc/puppet. That way any time I made a change in /etc/puppet it would be immediately updated and ready for the next puppetd run. Problem is the

Is there a way of specifying the server on a different port? I want to be able to change between two different puppetmasterd''s on the same box, and I want to pick between them by using selecting the port. There seems to be lots of :port* symbols floating around, and a --port in puppetd, but it''s not looking consistent. Is this something on the TODO path, or is there a

Hi all, Turns out there''s a small backward compatibility problem in 0.22.2. If you''ve got clients in older versions sending reports to a daemon running the newer version, you''ll run into a problem because I renamed the Puppet::Metric class to Puppet::Util::Metric. I''ve committed a fix to svn, but it''s not a big enough problem to require a new

Just poking around on the Docs site and went to the facter recipe for VMware. (http://reductivelabs.com/trac/puppet/wiki/IsVmwareGuestRecipe) If you look at the bottom, the author states that they were unable to get case statements to match as a regex. case $macaddress { "00:0C:29:*":{ file{ "/etc/running_inside_vmware": ensure => present } } }

hi I''ve read about PuppetReporting at the Trac website. Apparently you are working on integrating the benchmark tests for every type in ruby. Do you have any idea when this will all get implemented? This is a crucial part (and actually a necessary feature) in the configuration management system we have set up using Puppet. grtz Koen Vereeken

Hi all, Today I came across something that I consider a bug. Would like to hear your opinions. Facts: - Using 0.22.1 from Debian Unstable on a Debian Testing machine - Recipes work on other machines The recipe in question is: # Keep home-dirs in sync file { "/home/tim": recurse => true, source =>

Hi, My environment is composed of ~250 workstations hitting a single puppetmaster server, which has been working fairly well up until now. The most recent change has been a migration of a lot of remote file copy objects which were previously handled with cfengine. client side puppetd calls to the puppetmaster.getconfig method are taking unreasonably long, on the order of 2-3 minutes. It