similar to: Common routines for custom functions

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

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

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

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

Anyone think it would be useful to have files backed up to the filebucket even if they are not controlled by Puppet? 1 vote here. Derek ------------------------------------------------------------------------ For important statutory and regulatory disclosures and more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure

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

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

I recently tidied up a class/definition combo that sets /etc/issue and /etc/issue.net. This failed: define issuefile($path) { file { issue: owner => root, group => root, mode => 0644, content => template("issue_conf") } } class issue { issuefile { "issue": path => "/etc/issue" } } class

Puppeteers, For some reason I have to assign my variable before I include my class for the assignment to ''take''. I though the ordering was immaterial. Am I doing something wrong (again) or is this a funny? ----------------------- This works: <0> sa_dewha@engpsr0000.intranetdev.barcapdev.com (0 jobs)

Working more on my cluster class, I can see other things coming up. I''ve ended up creating custom functions to perform basic array-handling tasks (like ''join'' and extracting a single element). I''ve also had to create a template for /etc/hosts because I can''t use the ''host'' type and iterate over an array. I know Puppet is trying very

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:

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

I''ve been having great "fun" testing the new (Puppetised) build end-to-end for several days now. The majority of the fun has been coming from vendor packages (no names mentioned), typically with conflicting permissions on files, or perhaps different home directories, UIDs for the app users so it matters in which order you do things in. My current methodology is to go through

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

Dear R devel, I have a C++ app that calls into embedded R to perform some analytic calculations. When my app encounters a segmentation fault, R always prints the following crash prompt and asks me to enter an action: *** caught segfault *** address 0x8, cause 'memory not mapped' Possible actions: 1: abort (with core dump, if enabled) 2: normal R exit 3: exit R without saving workspace