similar to: Modules redux

Hi, I''m starting to move over to Modules, which looks pretty clean and solid. Reading http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation, one thing that confuses me is how the client resolves the implicit file server resources. I''ve got a few different puppet master servers running on different ports, and my configuration re-defines $puppet_master_host and

This is in reference to David Schmitt''s writeup [1] I like that writeup a lot; I just had a few comments/clarifications: * Namespaces: For now, we just use a flat namespace for modules, i.e. you can''t have modules within modules, and you always know that in a fully qualified name ''foo::bar::baz'' that ''foo'' is the module name and

On the module organization wiki, we''re got the following statement: To control access to the files in modules, the fileserver configuration can contain an explicit declaration of a ``modules`` module:: ... however, I thought the fileserver couldn''t define module or any section that is in the module paths. Has anyone tried this? And if it doesn''t work, is there

Hi all, I''m proud to announce that I seem to have pushed a new release of Puppet out in record time. This is a minor upgrade, mostly bugfixes and small features, but there are lots of each. See the changelog[1] for an idea of what this release provides, but keep in mind that this changelog is my first real attempt at keeping an up-to-date changelog. Enjoy! 1 -

Hey folks, I''ve just uploaded an apache2 module[1] to our Google Code repository[2]. It''s based largely on the recipe available on the Puppet trac[3], but with a fair amount of modification and generalization... Basically, it provides abstractions for config file snippets, site definitions, and apxs modules -- and then "basic" and "debian"

I have found a few issues with puppet and the up2date provider (version 0.22.4) that I''d like to run by those who use up2date (to see if others are experiencing the same issues). 1. Puppet doesn''t seem to find the latest updates of packages that are already installed. In looking at "/usr/lib/site_ruby/1.8/puppet/provider/package/up2date.rb", I found that

At long last, 0.24.0 has been released. Look for your friendly packagers to package it up in the near future, but in the meantime you can download it: http://reductivelabs.com/downloads/puppet/puppet-0.24.0.tgz I''ll be walking the different release sites (RubyForge et al) and posting it there, too. Look for a related announcement later today on changes in development practices

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''m new to puppet and trying to get started using it just in local mode. My basic question is: how can i reference a static file within the module (eg in the module''s files/ subdirectory, as described in http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation). I suppose i could try using a full.absolute path to the file, but that seems to completely defeat the purpose

The latest release is finally out; here is the changelog: Mostly a bug-fix release, with the most important fix being the multiple-definition error. Completely rewrote the ParsedFile system; each provider is now much shorter and much more maintainable. However, fundamental problems were found with the ''port'' type, so it was disabled. Also, added

I tried to install the ''mongrel'' gem tonight via puppet in an attempt to migrate from webrick to mongrel as described on the puppet site[1]. I added the following to my manifest: package { "rubygems": ensure => installed; "mongrel": ensure => installed, provider => gem, require => Package["rubygems"]; }

Hello, I just installed the latest version of puppet and puppetmaster on an up to date RHEL4 system. If I turn on ''storeconfigs'' on the puppetmaster server I get the following error: debug: Calling puppetmaster.getconfigerr: Could not retrieve configuration: Uncaught exception No such file to load -- sqlite3 in method puppetmaster.getconfig I have gems and rails installed

I just built new puppet rpm''s for Fedora (puppet-0.22.1-2) that fix the lockdir problem that many of you have encountered. The packages should show up on a mirror near you very soon. Unfortunately, I am having trouble getting to my buildsystem that I use for the RHEL versions of the RPM; I made the source rpm available on my people page[1] If you need the RPM for RHEL, you need to

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

I just talked to Mike McGrath from Fedora Infrastructure, and he told me that they are seeing load spikes (not quite performance problems yet, but definitely a concern) in their setup. As an example, the graph [1] shows a typical client - the spikes from 16:00 to 8:00 are almost exclusively puppetd doing its thing. It seems that the most likely culprit is the fileserver - they serve 500-1500

Hello folks, At Stanford, we use modules to define every possible service, package, feature in the traditional sense (apache, ntp, iptables, etc). Then, for clients (such as other departments) and "services" (such as our mailman infrastructure, our ldap infrastructure, etc), we use manifests in /master/manifests and distributable files in /dist/ and templates in /master/templates.

Currently, facter returns the kernel version as both the kernel and operatingsystemrelease facts. I would like to change that so that on Fedora, operatingsystemrelease is the release number (5,6,7 etc.) or ''Rawhide'' ... are there any objections to making that change ? David

Is there a way to tell the puppetmaster that I want to import all modules rather than listing each one individually?

Hi, I''ve just built rpm''s for puppet-0.23.1 - since there were a few people who had trouble with the update for 0.23.0 (the change in config files requires a bit of rpm trickery), I decided to be a little more cautious in how I push the new packages. So far, new packages are (or, will be shortly) available in rawhide, Fedora 7 updates-testing, and in my yum repos for

I''m trying to scale up Puppet and am wondering if I can use Puppet in an odd way. I''m looking to use Puppet as an authoritative source for all the configuration done to a cluster. That includes fstab''s, modprobe.conf, etc. This reduces duplication. I''m using SystemImager on a cluster and would like to run Puppet during the install, so when the node reboots, it