similar to: templates and require

I''d like to create a component that takes different actions based on the classes associated with the node using the component. Is this possible? Here''s what I''m thinking. node www01 { include webserver website { "site1.com": aliases => ["www.site1.com", "test.site1.com"], username => www0001 } } node www02 { include

Puppet is failing to restart lighttpd using the Debian init script. Both the default action of stop/start and using the reload action, which basically does the same thing, fail. It seems to be a filehandle problem. Changing the execute method in service.rb to redirect stdout to /dev/null allows the daemon to restart. Otherwise, I end up with a zombie process and according to strace, ruby

I just upgraded to 0.22.0 from 0.18.4 and I''m running into what I think are problems due to changes in scope rules. In my site.pp manifest, I have the following: import "classes/*" node nfsserver { include nfsserver } node webserver { include webserver } class cluster1_sites { website { "example.com": ...; "example2.com": ...; } } node

I''m trying to trigger a service to be refreshed when the target of a symlink changes. Here''s how it''s configured: file { "/etc/lighttpd/sites-enabled/$domain.conf": notify => service[lighttpd], ensure => "/nfs/www/$domain/etc/lighttpd.conf", links => follow, } This causes the service to be refreshed everytime puppet updates, even if the

I''m trying to get puppetrun to work, without luck so far. I have my puppetmaster and clients working fine with the clients polling the master. Now I want to be able to force an update. Using version 0.23.2 On the client I set listen=true and created the namespaceauth.conf file. Restarted puppetd and it appears fine. On the master I run puppetrun as root and get root@plane:/etc/puppet#

Hi - I a ran puppetd -vt against a brand newly build host (which is what I normally do for a new host) and got the usual message: err: No certificate; running with reduced functionality. info: Creating a new certificate request for sega-dev-1. info: Requesting certificate On the puppetmaster, I then list the waiting host with: puppetca --list then sign the key. In this case, I decided that the

Hi, How should I handle the combinatorics when one config file must be built for a combination of possible classes? Take for example the amd automounter''s configuration file, which on Debian is found at /etc/am-utils/amd.conf. This is an INI style file which looks like: [fsname1] param1=foo param2=bar [fsname2] param1=baz param2=quag In my case I have one class of machines

I''m in the process of documenting templates right now, and I figured I should see what happens when you use them with arrays: $ cat ~/bin/test.pp $values = [this, is, an, array, of, values] $content = template("/tmp/templates/testing.erb") file { "/tmp/temtest": content => $content } $ cat /tmp/templates/testing.erb <% values.each do |val| %> I got

Hi, I''m using the ''backup'' parameter in file resources to backup to a central filebucket on the puppetmaster. How do I restore a backup? I couldn''t find anything in the wiki, but saw some docs by running ''filebucket --help''. It says to restore a backed up file, you need to know the md5sum. Unfortunately, AFAIK the only place this

Is it possible to override the provider parameter when describing a user? My Ruby skills are quite limited, but it appears that provider is always chosen based on the operating system. I would like to build a user provider that will be almost identical to the objectadd one, but uses cpu[1] to add users and groups to an ldap directory. Since the cpu commands basically mirror the native

err: /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]: Failed to retrieve current state of resource: Could not find user puppet debug: Finishing transaction 75413780 with 2 changes since i put the last version on this test server i cannot launch puppet manualy: mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \

I know this comes up periodically, and I''ve read through the wiki (including the Best Practices page) & list archives, but still can''t quite get my head around it. I see lots of references to /modules and $MODULE_PATH, but am not sure what these refer to. Here''s a basic setup I have. Let me know if this looks correct: /etc/puppet/ |-- autosign.conf |--

Hi Puppet-Team, first thanks for this great configuration management tool ! My name is Matt and i am on creating a puppet plugin for openQRM. The basic framework is already existing and working well so far. Now, after having it working ok once i now ran into a problem that my puppet-clients do not get their configuration any more from the puppetmasterd. What i saw on the puppetmasterd logs is :

Hello there, I have come to a situation where I would like to mix 2 approaches to create the contents of a file. Here is what I have: a module ''sudo'' which manages a hosts /etc/sudoers file: init.pp: class sudo { case $operatingsystem { Debian: { package { "sudo": } } } file { "/etc/sudoers": mode => 440, content =>

Is there any security (or perhaps plans to add security) within the fileserver to verify that clients are only able to receive files specified in the manifests on the server? I''d like to distribute different Kerberos keytabs to different nodes such that nodes www01 and www02 can retrieve different files from nodes www03 and www04. Any ideas on how best to approach this problem? Thanks,

Hi all, I have a situation where I want to use the same template to create two different files in two different classes. I''ve tried to lookup some information on what is possible with templates, how advanced you can get, but haven''t found much. I guess it''s one of the areas where I should contribute to the docs - once I figured out what I can do, that is...

Folks, I''ve been looking at creating a set of man pages for puppet and I''m trying to come up with a reasonable hierarchy. I''d appreciate any suggestions. So far, here''s what I''ve come up with: - puppet(1) - puppetca(1) - puppetdoc(1) - puppetrun(1) - puppetca.conf(5) - puppetd.conf(5) - puppetmasterd.conf(5) - puppetd(8) -

hi all, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template

I have a few different groupings of hosts, and I am wondering what is the best way to organize the node configuration for them. I have a few machines that are VMware hosts, a bunch of VMware guests, and the main admin server which runs a bunch of stuff like puppetmasterd. I''ve got a bunch of classes/*.pp which define configuration for sudo, yum, java, etc. Right now I just have

Should multiple requires still work? require => Package[[lighttpd, openssl]] It fails in 0.22.0 with err: Could not apply complete configuration: Could not retrieve dependency ''Package[lighttpdopenssl]'' at /etc/puppet/manifests/classes/webserver.pp:84 Christian