similar to: Warning for Fedora Core users

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

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

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

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

so I have this sudo module that I''ve been working on: class auth::sudo { package { sudo: ensure => installed } file { sudo_config: name => "/tmp/sudoers", owner => "root", group => "root", mode => 0440, notify => Exec["sudoers-syntax"], source => [

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

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

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

Hi, I have a number of puppets talking to 1 puppetmaster. Everything was working fine until suddenly this week the puppets are revolting. Whenever I try to run ''puppetd -v'' I see a lot of messages like: Certificates were not trusted: hostname was not match I''m sure I did not make any changes to DNS lately and I didn''t upgrade puppet on any of the machines

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

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

Dear all I''ve gotten into the habit of including SVN headers in my templates, etc so it is easy to see where the file installed into /etc/puppet/ came from. Furthermore, we use svn cp to create release branches. Therefore, you''ll see something like this: # $Id: dumpadm.conf 1239 2007-10-23 16:04:06Z sa_dewha $ # $URL:

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 want set up a puppet HA structure. but if the puppetd can set more than one server address ,the work will be simple :D if one puppetmaster have error, the client can auto try the next. I think I can use the heartbeat or dns to do this same thing,but not so good. so I want know the puppetd can direct set in the configure file ? if not,will be add this option? -- Huang

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

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

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

One more error/warning from the latest Puppet from git: In the provider I have KEYS = Facter.value(:roothome) + "/.ssh/authorized_keys" Puppet::Type.type(:authorizedkey).provide(:parsed, ... I get an error on the Puppetmaster: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/authorizedkey/parsed.rb": undefined method `+'' for nil:NilClass Could not

Hello I want to share some common subroutines between my custom functions. Given the way Puppet loads the .rb files in $plugindest/puppet/parser/functions, does anyone know how should I lay this out? I tried creating a module myutilities def self.blah() ... end end (NOT within the newfunction() call) in one of the (top-level) functions'' .rb file. However, calling