search for: bajandud

As I sit here staring at my manifests (and pondering a module to control Glassfish), I''m pondering the best way to do a first-run of puppet to get the initial repositories and puppet configuration downloaded. My theory is that I''ll modify rc.local (or replace firstboot-tui, we don''t use it with automated builds) to run puppetd twice - once to request the certificate,

On Thu, 2008-03-13 at 04:26 -0700, bajandude@googlemail.com wrote: > Has anyone modified yum.rb to provide groupinstall abilities? To the best of my knowledge, nobody''s working on that. The main difficulty in enabling that is making sure that puppet doesn''t run ''yum groupinstall'' (or ''yum grou...

I''ve just filed http://reductivelabs.com/trac/puppet/ticket/1182 with the aim of making it easier to add fact pickup from dmidecode in manufacturer.rb. As the ticket says, I think that the fact sections, keys and values shouldn''t be hardcoded in manufacturer.rb, but should be stored in a configuration file somewhere. This means that a given stable installation of Puppet can be

For whatever reason, the RPMForge package ruby-rrdtool doesn''t play nice on my CentOS 5.1 box with puppetmaster. It installs site_ruby/1.8/i386-linux/RRD.so, which puppetmaster is unable to find (and the suggested test of ruby -rRRDtool -e ''puts :yep'' fails). Using ln to link RRD.so to RRDtool.so works for the command line test, but still fails for puppetmaster. This

Hello folks, I''m sitting here converting my static, simple classes/snmp.pp into a full module, and I''ve run into a bit of a brick wall. net-snmp is one of those wonderful programs that will only read two configuration files (it reads a few more, but only 2 are in /etc) - /etc/snmpd.conf and /etc/snmpd.local.conf. This means that my SNMP module is somehow going to have to

After encountering a few syntax errors today, I decided I should document what they were so I could stop remembering the fixes :) http://reductivelabs.com/trac/puppet/wiki/SyntaxErrors --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hello folks. I''ve got a problem that I can''t work out the solution to. My base workstation node definition says essentially: node base-workstation { file { etc-sudoers: name => "/etc/sudoers", ... } } This works fine, all of our workstations get a standardised sudoers file. However, I have one user on a workstation who needs a specialised sudoers file.

Hello folks, As we rebuild all of our servers from a variety of distributions to one standardised distribution, we''re running into the fact that several servers have conflicting ideas of who UID 501 is. Since we''re rebuilding, that''s not really an issue - I''ve started at 500 in a virtual_users.pp file, and I''m realizing users in the per-node

I''m trying to work with Users and the realize function, and it''s driving me batty. Puppet is 0.23.2. My definition looks something like: class virtual_users { @user { fred : uid => 500 ... } @user { derf : uid => 501 ... } } node base-node { include virtual_users } node "testnode.domain.local" inherits base-node { realize User[fred] } puppetd

Me again! I have a recipe that looks like: class postgresql { file { pg_hba_conf: name => "/var/lib/pgsql/data/pg_hba.conf", source => "puppet://puppetmaster/files/workstations/common/var/lib/pgsql/data/pg_hba.conf", owner => postgres, group => postgres, mode => 600, subscribe => [ Package[postgresql] ],

Out of curiosity, I pulled 1188 records out of /var/log/messages, and extracted the number of seconds required to compile the manifest. Ran the output through perl and Excel to get a graph of count vs time to see what the puppetmaster box performance looks like. This excludes data out to the 2200 second mark, where the virtual machine got its knickers in a twist. Puppetmaster runs in a VMware