similar to: Overriding types?

I tried using $name in this manner: remotefile { "/etc/auto_direct.local": mode => 644, source => "solall/$name" } (The remotefile function is handy, BTW) When I use $name here, instead of specifying the actual path to the file (solall/etc/auto_direct.local), puppetd ends up making /etc/auto_direct.local an empty directory. Shouldn''t $name

Hi, I''m exploring Puppet and have hit a rather weird problem. The puppetmaster server is running CentOS4, fully updated, with puppet installed from the dlutter RPM repo, version 0.20.0-1.el4. I tried adding the remotefile function definition from http://reductivelabs.com/projects/puppet/documentation/installation.html in /etc/puppet/manifests/utils/remotefile.pp but when I start

Hi, I just upgraded to puppet 0.20.0 today after a short time playing with 0.19.3. The docs say to use the uppercase form for types but that seems to break for me. When I updated the remotefile function to use the new way, the puppet clients complain about objects not being found. For example: ----- OLD WAY (works, just with deprecations) ----- define remotefile (...) { file { $name :

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

$ puppet --help /opt/csw/lib/ruby/gems/1.8/gems/puppet-0.20.1/bin/puppet:103: undefined method `feature'' for Puppet:Module (NoMethodError) from /opt/csw/lib/ruby/1.8/getoptlong.rb:460:in `each'' from /opt/csw/lib/ruby/1.8/getoptlong.rb:457:in `each'' from /opt/csw/lib/ruby/gems/1.8/gems/puppet-0.20.1/bin/puppet:97 from /opt/csw/bin/puppet:18

Is there a Best Practices method for doing this? :) I''m trying to configure clients by ssh''ing to them from the puppetmaster. My steps are: ssh $host ''svccfg import ...'' sleep puppetca --sign $host scp namespaceauth.conf $host ssh $host ''svcadm restart puppet'' The problem is that I''d like to stop and log an error if the cert signing

Is there a list somewhere? How do I know what $operatingsystem, for example, is going to be set to? Using ''solaris'' seems to work, but I haven''t tested ''ubuntu'' and ''redhat'' yet (haven''t gotten that far). It''d be nice to have a list of available vars, along with "how they are set." -Charlie

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hi, I had a working puppet setup using version 0.22 until the ruby security patch bit me. I tried upgrading server and clients to 0.24.1 however my old manifests don''t seem to work anymore. When I run puppetd on the client I see lots of messages like: err: //Node[waterbuck]/yumupdater/Remotefile[/etc/cron.hourly/yumupdater]/File[/etc/cron.hourly/yumupdater]/ensure: change from absent

Hello The following chunk is within a class definition. ${name} is being exchanged with an empty string: remotefile { "/${server_xml}": owner => tomcat, group => tomcat, mode => 600, source => "${ftoe_src_prefix_dev}${name}.jvm1" } However in the following chunk, lower down in the same class definition, ${name} is being exchanged

Hi, I''ve just changed my debian preseed configuration to install the debian unstable package of puppet v0.22.1. As part of the preseed I have a late command that clobbers the /etc/init.d/puppet file into using the puppet standalone program and not the puppetd (as this is what I''m using). Since the upgrade to 0.22.1 every boot hangs during the initd. Going into standalone mode

Hi, I''m trying to use several sources to pick from in a remotefile statement: remotefile { "/etc/sudoers": mode => 0440, source => [ "config/apps/sudo/sudoers.${host}", "config/apps/sudo/sudoers" ], sourceselect => first } But it doesn''t seem to work. I get an error like this: "File source

I thought the purpose of classes was that you could redefine types in the subclasses. However I get "Duplicate definition" errors whenever I attempt this. On a whim I tried the code from the documentation: http://reductivelabs.com/projects/puppet/documentation/structures.html --- Subclassing The primary benefit of using subclasses instead of just including the parent class is that

Howdy, Found out about this project while looking for via ONLamp''s FreeBSD build system article. After finding cfengine a tad arcane, this project seems like a good fit for my setup. I''m still at the tinkering phase, but I envision this thing bootstrapping and maintaining several FreeBSD installs which have different CPU''s and packages. The Good News:

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

I am trying to write a definition that downloads and extracts a tar file if the destination directory does not exist. The tar file won''t change and does not need to be download and extracted if it changes. The definition I am using now is: define remote_tar($source, $directory) { remotefile { "/tmp/$name.tgz": source => $source, } exec {

Hello List, We are using puppet to manage a growing number of Debian Etch based servers (currently 70). Since upgrading to 0.22.4 we encountered a problem when services do not restarted on puppets request. For example the Nagios remote plugin executor daemon (nrpe). It''s running daemonized and its confiugration is located in /etc/nagios/nrpe.cfg. This file is managed through puppet

There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?

Hi, I''m banging my head against the usage of variables i defines. Fx. I have this defined to easily create new systemusers: define systemuser($home = $home, $shell = "/bin/bash") { group { $name: ensure => present } user { $name: ensure => present, gid => $name, home => $home, shell =>

I am having SSL difficulties setting up a new puppet client: Client: fedora (rawhide) using 0.23.2 Server: centos 4.4 using 0.22.3 After initiating contact with puppetd --test --server=puppet.myclient.com, I see the CSR on the server. After signing it, and running puppet again, I get the signed certificate, but also see: err: Could not retrieve configuration: Certificates were not trusted: