similar to: Puppet Reports

What is the view of having / not having global variables in Puppet? Facter variables are global in the sense they are defined in every scope (whereas ''normal'' variables are only available within the scope they are defined in). I could simply add a custom fact for my DoesTheServerNeedASerialConsole flag to Facter, but I''m not 100% sure I should be having the client

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

-----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 =

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

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

Hello, I recently started deploying puppet on our server farm. It works wonderfully with RHEL4, Gentoo and Debian. I''m looking for a way to determine the state of all nodes. Say for example that I change a file on the puppetmaster which affects 200 nodes. Then I go to lunch. When I get back, I''d like to know which nodes have been updated and which have not. I asked this in

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

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

There''s definitely enough complexity in some of the modules out there to warrant solid test coverage, especially if people start extending a module to support more distributions and OSes, while trying to keep the existing support working. That''s even before you start thinking about functions, facts, and native types. They''re *really* in need of solid testing, being all

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

I''m about to leave town for three weeks and my home server keeps rebooting. It''s my mail server, unfortunately, so there''s a good chance you won''t get this. :/ Anyway, I''ve been meaning to do this for ages and ages, and it''s time to finally do so. I need to move all of the Puppet lists to a public, non-me provider, someone who has

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

Hi Luke and other people working on 0.24. I hope this is constructive. So, I have our configuration working against a checkout from git as of last night. Subject to (sorry, here''s the big but :) * external_nodes script is not being called (#951) * Custom types aren''t working unless I drop them into $rubysitedir/puppet/{type,provider}. Previously they worked in

Maybe it works, maybe it doesn''t, but I sure as hell can''t make it work. I get stuck with "Could not find object(s)" whatever I do This is my module init.pp class ztest::setup { notice "MAIN SETUP CLASS" file { directfile: path => "/etc/directfile", owner => root, group => root, mode => 0644, content

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

Hello, I''m scratching my head as to the best way to plug in a script to do some client configuration. The script is about 40 lines long (full of basic instructions to fiddle with VCS in fact). Lots of execs would seems cumbersome. My thoughts are to simply install this to the client (via the fileserver) and exec out to it. Does this seem sensible? And if so, be aware of things like

Hi All, In my companies environment, we have multiple sites in multiple geographic locations, sometimes with high latency between the sites. I''m trying to come up with a solution that could provide puppet infrastructure to all sites nodes. ----a few assumptions--- - puppet manifest / configuration is fetched from a centralized version control system. - store db is needed (ssh keys,

Hello... I need some help with tags. as an example: # pseudo code class ssh { file { "/etc/ssh/ssh_config": # normal stuff tag("dangerous") } file { "/etc/ssh/sshd_config": # normal stuff tag("dangerous") } file { "/etc/ssh/ssh_known_hosts": # normal stuff tag("safe") } } on client: puppetd --tags

Hi all I''m working on my modular recursive Makefile & svn-backed home for my Puppet manifests, custom functions, types, etc. So I''m trying to put together individual modules, test targets and so on. I have noticed that the $libdir (and probably the other configuration options too) sources from puppet.conf are not overridden by specifying --libdir=blah on the commmand line