similar to: Module Organization

Hi, I was talking to Luke today about managing manifests and related files, and he suggested that I post to the list.. What would be nice (and what I''ve use in in-house systems I''ve used previously) is to have a way to dynamically include manifest fragments at runtime. Lets assume that you''re setting up bugzilla using puppet. In the ''main'' manifest

Hello all. Probably this question has already been posed in the context of another software, but I am unable to find it. I would like to implement a module which should manage munin-clients as well as the munin-server. Here is what I am thinking about implementing: - There are two classes: munin::client and munin::server - munin::clients'' configuration will be managed automatically.

Hi all. I am trying to use debian package preseeding within my modules. Therefor I have created a preseed_package.pp like: define authentication::preseed_package ( $ensure ) { file { "/var/local/preseed/$name.preseed": source => "$module_path/files/$name.preseed", mode => 600, backup => false, require => File["/var/local/preseed"], } package {

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

"Service and class definitions are scoped just as variable assignments are." But what about types? Here''s an example: class solserver inherits server { remotefile { "/etc/shadow": mode => 400, group => staff, source => "solall/etc/shadow.server" } Is it possible to just override the "/etc/shadow" definition for

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

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

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:

I''ve been thinking about how to make Puppet a killer app, and I think there is one specific thing that could be done to help make that happen: People using Puppet now to consistently state what they *really* wish Puppet could do for them -- the recent thread around Puppet on Windows is in that vein, but it''s not specific enough. For example, I''d like to know what

Hi, I''ve just installed Puppet on two CentOS 5.5 servers, "S" for "A". "A" does not have the ntp package installed nor of course ntp running. The Puppet server is started on "S" with the ntp class from this tutorial: http://bitfieldconsulting.com/puppet-tutorial (included below) however when I run the agent on "A" it don''t

Hi all, I have three parameterized classes, named mq, mq_gsk and apache. The mq class always calls the mq_gsk class, but the apache class should only call the mq_gsk class when the mq class is not used in a hosts'' node definition Here is my configuration class mq ( $gsk_version = undef ) { require mq::params < ..... > class { ''mq_gsk'':

How can I express the following in puppet? $http_conf = "/etc/http/conf/httpd.conf" $vhosts_conf = "/etc/http/conf/vhosts.conf" @files = ("$httpd_conf", "$vhosts_conf") foreach f (@files) { file { "$f": owner => root, group => root, mode => 664, source => "puppet://$server/apache/$f", }

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

Hi, I''m learning puppet as that is what they use at my current work, though that could change... Question 1: Last place of work, we wrote our own perl based system which was extremely simple and concise to drive - eg to distribute a file, we would put it in: <nfsdir>/noarch/dist/etc/syslog-ng/syslog-ng.conf/ # which means create a file /etc/syslog-ng/syslog-ng.conf on the

If I use the ''file'' type to sync a file where the parent directory doesn''t exist the sync fails. According to the puppet docs "Puppet will autorequire any parent directories that are being managed". Am i missing something? Example: file { "/tmp/dhcp/dhcpd.include": source => "/tmp/dhcpd.include", } In

Hi, How would I do this: wgetfile { "$name-$file": url => $url, file => $file, target => $target, options => $options, before => Component["md5check-$name"] } wgetfile { "$name-$md5file": url => $url, file =>

I have the following define... define puppet::module_dir { if $name { include puppet file { "${puppetdir}/modules/${name}": ensure => directory, mode => 0755, purge => true, recurse => true, } } } I call it like so: puppet::module_dir { "main" } puppet::module_dir

Hi there, Just started using Puppet since yesterday, so a totally newbie question. I tried to search the answer by myself but none of the suggestions actually worked. This is how my "modules" is laid: |-- modules | |-- mySudo | | |-- files | | | `-- sudoers | | `-- manifests | | `-- init.pp The file(s), that I want to send to the client machines, is in the

Dear puppet wizards, http://docs.puppetlabs.com/puppet/3/reference/lang_defined_types.html does not suggest to me that nested parametrized defines would be forbidden, hence I expected the following code to work: add_to_ssh_authorized_keys.pp: -------- define a::ssh_keys::add_to_ssh_authorized_keys($homebasedir="/home", $targetuser="root", $keyowner, $keyownername,

Hi dear Users, I''ve been looking in internet and on the puppet wiki website but i am still confused about this. Lets say I have 2 Modules: A and B What I want to do is call a class on module A directly from module B. I know it is possible to call different classes within a module by using inheritance and using different .pp config files. But how I do not know how to do the