similar to: Fileserver scalability

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

I just realized that if you don''t have redhat-lsb on your (Fedora 7) box, all those lsb* facts don''t show up. Should I make redhat-lsb a requirement for the facter rpm to guard against that ? David

Just wondering if anyone has built (or found) Puppet rpm packages for RHEL4 x86_64 version. James ********************************************************************************* Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this

Hi, My environment is composed of ~250 workstations hitting a single puppetmaster server, which has been working fairly well up until now. The most recent change has been a migration of a lot of remote file copy objects which were previously handled with cfengine. client side puppetd calls to the puppetmaster.getconfig method are taking unreasonably long, on the order of 2-3 minutes. It

Hi all, I''m looking at changing the operatingsystemrelease fact for Red Hat. Linux currently just uses the kernel release as the operating system release, but I''ve got a client who wants the release to have both the specific distro (e.g., AS or EL) and the release (e.g., 3 or 4). Will this particularly annoy anyone? Anyone want to help make the release string work on

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 am sure this subject has come up before. I did not find anything on Google that comes close to what I am trying to do. I would like to manage different groups on multiple nodes using puppet and do not know of a good way to do it. Does anyone have an idea of how I can accomplish this? Any help will be appreciated. Thanks, Mouncef _______________________________________________

I have a machine with two swap partitions (sda2 and sda8). Both will have none as mount point. When I try to use puppet (using mount type) for managing fstab I get problems because "name" in both instances (i.e. mount path) will be "none". How should I fix this within puppet? Regards Halvard Moe

Why doesn''t the yum provider support version, I tried added ensure -> ''ver'' and it barfs up (on clients) with: <snip> err: //stan.gbuild.org/any-host/java/Package[j2sdk]/ensure: change from 1.4.2_12-fcs to 1.4.2_13-fcs failed: Package provider yum does not support specifying versions at /etc/puppet/manifests/classes/ java.pp:13 </snip>

Hi, I have several Debian servers with puppet 0.23.2. Part of my manifest looks like this: class virt_all_users { @group { "andy": ensure => "present", gid => "1000" } @user { "andy": ensure => "present", uid => "1000",

Hello, I have two Vmware images, with 256MB of RAM memory each one, running puppetmasterd for the server and puppetd for the client. It''s normal that my puppetmasterd and puppetd occupies almost 10% of RAM memory each one? They aren''t doing anything especial, just listening on the ports. Thanks.

On Aug 27, 2006, at 8:56 AM, Thorsten Sandfuchs wrote: > hio, > I''m trying to build a "master"-directory (general) with some base- > files to > spread, and a host/class-based directory-structure to override the > defaults, > if necessary. If a file only is present in the general-section, it > shouldn''t > harm the setup, if it''s only

Hi, in an attempt to simplify my configuration, and from a suggestion on IRC, I was thinking of using multiple values for file { source => [] }. Was just currious if anyone had any comments on this. Basically, I setup my file-server to use: <snip> [private] path /var/lib/puppet/files/private/%H allow * [shared] path /var/lib/puppet/files/shared allow *

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,

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:

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

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

Ok, so I''m obviously doing something wrong here. This is running puppet 0.22.2 on a centos 4 update 4 box. When I try running this test - mount { bigdisk: ensure => mounted, device => ''bigserver:/bigdisk'', fstype => nfs, name => ''/bigdisk'', dump => "0", pass => "0", options =>

I thought I''d put this out there for anyone to save anyone who''s running 0.22.4 on AMD64 hosts a whole world of hurt. Basically, the libshadow-ruby1.8 package that Puppet (as of 0.22.4) relies on is broken for AMD64 in both Debian (Sarge+) and Ubuntu (all releases). The problem is basically just some non-portable code. I''ve reported the bug into Debian with a patch, so

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