search for: simpsonjulian

Various people have said they are going to UKUUG and I wanted to remind people if they are about and want to discuss puppet, facter, etc they can come along. Entry is not restricted to UKUUG attendees, I''ll try and make myself obvious by having some puppet related paraphenalia. http://www.ukuug.org/events/spring2009/social/ Paul --~--~---------~--~----~------------~-------~--~----~

Hey all, I''ve open-sources Digg''s apache module: http://github.com/plathrop/puppet-module-apache I know this isn''t much more advanced than what I''ve seen a lot of people using. Here''s my proposition, though. Let''s get all the disparate "apache" modules out there merged together into One Awesome Module. What do you think? One module

Hi, I want to validate my puppet manifests before I check them into source control. I just want to make sure that the manifest syntaxes are legal, not to do any more complex testing - the checkin may be on my laptop and not on the system that the manifests may be intended to run on. Ideally I''d be able to do this from ruby code - and I did try to instantiate some classes and override

Hi, I''m pretty sure I once did some experiments with running puppet wihtout a puppertmasterd - but having a "normal" puppet manifests and modules structure in /etc/puppet. Sadly, I can''t find how to do that anymore. I know I can write plain puppet instructions in a file.pp and run them plainly - but I want the whole config as if it would reside on a server) When I

How come this doesnt work? I write this in a normal ruby script it works just fine. <% for cpu in (0..processorcount) %> I want to loop through the number of processor so a specific action can be taken to generate content for a file. I get an error on the master of: bad value for range at /etc/puppet" -Chris -- You received this message because you are subscribed to the Google

Hi, Luke asked me if I was willing to share what I am doing with the Puppet user community. So here goes: I am using puppet to manage one host right now. While that isn''t a good advertisement for Puppet''s scaling capabilities, I find it interesting because I built my single node (personal mail, svn, ci and web server) with puppet where I could (clearly there was some

Hello, I really didn''t expect this to be difficult, but I''ve been struggling with this all day :( I''m running CentOS 5.3, with rubygems, rack and fastthread, from EPEL. I''m running puppet-0.25.0-1 built from the spec file in the latest stable tarball. I''m using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen (kanarip), which is effectively EPEL

Just one more email and I''ll let you go for a few hours :) One of the things I like to see in apps is that they are immediately intuitive and easy to use for new users. I think Puppet is really good here, but there''s opportunity to make everything better. We want everyone to love Puppet from their first few minutes using it, all the way through to datacenter nirvana.