search for: shahn

Hi, I''m trying to set up apache2 under puppet, as in this recipe: http://reductivelabs.com/trac/puppet/wiki/Recipes/DebianApache2Recipe I have a file "apache2.pp" as shown there, and then a webserver.pp file (see below). On running puppetd on the client, I get this message: err: Could not retrieve configuration: Could not find definition site in file

In case anyone is interested in extending the Puppetmaster by writing new functions, I''ve written up some notes on how to do it, gleaned from my own experience earlier today: http://reductivelabs.com/trac/puppet/wiki/WritingYourOwnFunctions Corrections from people who''ve done it before, or who are wanting to do it, as to correctness, clarity, or whatever, are appreciated. And

Trying to learn Puppet, given a cfengine background. Am trying to understand the Puppet way of accomplishing the following: I have a lot of servers, that are organized into clusters (we call them silos). Each silo has a specific set of parameters (like IP addresses). I''d like to organize the silo information in some way that each server is associated with that information, and can

I would like to have packages installed either in the early morning or whenever I manually choose to do so on a particular machine. I am trying to convert my existing configuration from cfengine so in that tool I had something like: packages: Hr03|ManualRun:: <package installation commands> This basically says to install packages if it''s either 3:00-3:59am or if

I attempted the following: resources { service: purge => true, noop => true } service { sshd: ensure => running; iptables ensure => running; } And got the following message: notice: Starting configuration run err: Found a bug: uninitialized constant Parse notice: Finished configuration run in 0.47 seconds When I remove the ''resources'' line, everything works

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