similar to: RFC: Moving mailing lists soon

Hi, I''ve just changed my debian preseed configuration to install the debian unstable package of puppet v0.22.1. As part of the preseed I have a late command that clobbers the /etc/init.d/puppet file into using the puppet standalone program and not the puppetd (as this is what I''m using). Since the upgrade to 0.22.1 every boot hangs during the initd. Going into standalone mode

We haven''t been able to use mongrel for testing yet, but in order not to waste time, we did some performance testing with 1, 2 and 4 puppetmasterd/webrick processes. Attached is an HTML page (ripped from our wiki - not pretty, but reasonably readable) which describes the method and results. If someone feels like making some nice graphs, that would be great. If not, I''ll try to

Hi, We''re trying to follow the instructions at http://reductivelabs.com/trac/puppet/wiki/UsingMongrel (Just using a single puppetmaster/mongrel instance and plain mod_proxy for now, instead of balancer one) We got past the "Server is not a class" error by modifying mongrel.rb We also kind-of got past the: /opt/bin/puppetmasterd:293: undefined method `daemonize'' for

I turned on reporting the other day and I''m seeing alot of these when puppet runs. Especially during times when nothing is going on (middle of the night etc) Tue Dec 11 12:34:48 -0500 2007 //base/puppet/puppet::client/Service[puppet]/ensure (notice): ensure changed ''stopped'' to ''running'' It''s also quite odd that puppet when it runs it thinks

Hi all, I''m in the throes of the REST conversion and I''m wondering: How important is it to retain backward compatibility? The language will clearly be consistent between the two, but it looks like it''s going to be a heckuva lot more complicated to keep compatibility for all network services (as in, for each of them, I''ll have to write a shell that

Hi, I think this has been discussed previously on the list, so apologies if I''m covering old ground but I''ve been using puppet to manage a few Rails applications which have dependencies on quite a few gems, so it''s getting to be a bit of an onerous task to manage them. It looks like the command line interface to gems doesn''t really support automated

Since I had my type development epiphany a couple of days ago, I''ve decided to write down my understanding of developing simple types, at http://reductivelabs.com/trac/puppet/wiki/PracticalTypes. I''d appreciate comments from people who already know how to develop types as to correctness, and also comments from people who are new to type development about whether it''s a

Hello everyone, A long time ago, I posted the Stanford Best Practices and I''ve gone through and updated it today. I''d like to have people go through it and see if we can strip out some Stanford specific stuff and tag this as an official best practice. I think an official best practice will be important as more and more people consider making shareable modules, etc (mostly

Hi, https://reductivelabs.com/trac/puppet/wiki/DocumentationStart https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction https://reductivelabs.com/trac/puppet/wiki/PuppetMasters https://reductivelabs.com/trac/puppet/wiki/PuppetBestPractice - Max

Hi all, i'' m trying to configure puppet to use rails with postgresql. I'' m having troubles to make it work. Got no error when running puppetmasterd but nothing is being populated in the DB. Is anybody using puppet with postgres ? my config (in puppet.conf) [rails] dbadapter = postgresql dbname = mydb dbserver = localhost dbuser = user dbpassword = password

Anyone know if it would be straightforward to extract this information from Puppet, probably in a custom function: The classes included as a result of the client''s parsed configuration - or - Am I in class X as a result of my parsed configuration? I''m thinking it would result in a more elegant manifest if classes X and Y behaved differently if they were both included compared

Hi. I''d like to use exception handling in my custom facts. For example, in plain Ruby: begin buildno = '''' bcrelease = open("/etc/BCrelease") while (line = bcrelease.gets) line = line.chomp buildno = $1 if line =~ /^Build:\s+(\d+)/ end bcrelease.close print "#{buildno}\n" rescue print "No

I''m having problems with a definition not being found. I get the following error when running puppetd -vt: err: Could not find type "manual_apt_get_update" in file /etc/puppet/manifests/definitions/apt_misc.pp at line 22 The definition is present for sure. Can anyone spot a problem with the code below? define manual_apt_get_update { exec { "/usr/bin/apt-get

Hello All, We are investigating writing a custom puppet report that would be a web app to show a change log for each host. The issue we are running into stems from how we run puppet. We run a daily cronjob in noop and report mode and fix inconsistency''s either by hand or by puppet depending on the host. This should change some what in the future as our puppet environment matures

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

I''m thinking about how to set up the processes for Production puppet runs now. Being ultra-conservative here, we''d like to see what would happen before pressing the red button. I can run in noop mode, and everything is evaluated but nothing is done. A YAML report magically appears on the Puppetmaster which my script parses and spits out something the management can read

Hi all, I''ve got a new class in the current code, which I''ve been calling Configuration but Matt reasonably thinks is horrible. He is recommending the name Manifest, and I figured I''d see what others thought. The point of the class is to function as a resource container -- it keeps a reference to all of the resources we''re managing, and knows how to

Fedora Core 7 has just updated their Ruby package (was 1.8.6.36-3.fc7, is now 1.8.6.110-3.fc7), and the upgrade broke my Puppet installation, and there was a similar report from someone else. Communications between the puppetmasterd and the puppetd running on the same host broke down with the message: Could not retrieve configuration: Certificates were not trusted: hostname not match with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Russ, Digant, *! Several times on the IRC channel I noticed people having problems getting to grips with the interaction of scopes when using template nodes[1]. Typically this looks thus: | node genericwebserver { stuff } | | node ''web01.example.com'' inherits genericwebserver { | $influence_genericwebserver =

Hello all, I''m thinking about a configuration class that, amongst other things execs out to a ''dangerous'' configuration script. I''d like to make this a noop by default, so the operator has to try a bit harder to invoke it. So I thought about doing something like: class blah { exec { danger: noop => true, tag => hitme, command