similar to: Installing YUM with Puppet

Hi, I can''t find an option of the puppetd client that can just print what the puppetd client will do on my system (updateing files, installing softwares, etc), but without doing all the things (like a "diff" between the current state of my system and the state defined on the puppet server). Is such option exists ? Regards

Hi, I''m running Puppet 0.23.0 on my servers, and i got something like this: In a classa.pp file (included in site.pp): class A { file { "test1": ... } } In a classb.pp file (included in site.pp): class B { file { "test2": ... } if defined(File["test1"]) { ... do things ... } if

Hello folks, Im trying to migrate from static nodes-definition to external nodes definition. My script looks like this stolen from http://reductivelabs.com/trac/puppet/wiki/ExternalNodes: {{{ #!/usr/bin/perl -w use warnings; use YAML qw( Dump ); use Switch; #initialize vars our @classes; our %parameters; Function to fill @classes and %parameters with correct values .... print Dump( {

Hi, I''ve got a problem when using templates in Puppet. In my node declarations, i set (or not) some special variables to activate (or not) some part of my configuration. When i don''t need the configuration part, i don''t declare the variable. I then use something like this in my templates: ... <% if defined? myvar %> ... myvalue = <%= myvar %> ... <%

Hi, I can''t find a way to add a page on the wiki (i''m logged in but there is no edit button on the facter recipes page), so here is a recipe for DRBD. It has been tested on version 0.8.4. Can someone publish it on the web site? if FileTest.exists?("/proc/drbd") result = {} Thread::exclusive do File.readlines("/proc/drbd").each do |l| if l =~

Hi all, I''ve now finished all of the functionality I plan to add in the next release, so all that remains is closing as many open bugs as possible. I''ve gone through and marked all of the bugs I specifically plan on fixing with the ''minor'' milestone. If you have a bug in the db[1] that you think needs to be fixed in the next release but is not

Hello, i use a file type to manage sysctl.conf. For some work i override this file by doign File[''/etc/sysctl.conf''] and i have an exec refresh only to run sysctl -p so it reread the sysctl.conf file if changed. My issue is that at each run i got, i start in state when i see the overriden one on the server: 1st run, i have the basic sysctl.conf not the ovveriden one

Just poking around on the Docs site and went to the facter recipe for VMware. (http://reductivelabs.com/trac/puppet/wiki/IsVmwareGuestRecipe) If you look at the bottom, the author states that they were unable to get case statements to match as a regex. case $macaddress { "00:0C:29:*":{ file{ "/etc/running_inside_vmware": ensure => present } } }

Hi all, I just stumbled over a huge rails.log in /var/log/puppet on the puppetmaster. It is full of DB statments which seems to point to the fact that puppetmaster''s rails environment is set to development. No problem, I thought, set the system''s RAILS_ENV to production make it available to the master daemon and restart it. Unfortunately, this does not work. I searched

Hi, when using puppet to install extra rpm packages on centos: how can I make a package depend on 2 or more other packages. e.g. this works: class centos4_extra_packages { package { "test1" : ensure => installed, require => package["prereq"] } } but I can''t figure out how to make test1 require

Hi As I''m more familiar with cfengine and it''s way to split updates (in update.conf) from the actual grunt work (in cfagent.conf), I''m wondering how to best manage puppet and my manifests with puppet...? Should I define a puppet class that copy the puppet package (in .tgz format) and all the manifests to the client, and then have all my other classes depend on

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

Do any of you good people have a moment to help me out with my basic Puppet language skills, I''m a little new around here and getting an error I don''t yet understand. I have an RHEL4 Puppetmaster happily controlling the permissions of /etc/sudoers on an RHEL5 and SolarisX86 client. My actual environment consists of several systems in several locations. All systems need the

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 am working on some initial testing of puppet and noticed that when using the package type, I see this in my client logs (from different runs): warning: Found multiple default providers for package: up2date, yum; using up2date warning: Found multiple default providers for package: yum, up2date; using yum This is on a CentOS 4.4 client with puppet-0.22.0-1.el4 (from dlutter repo). After

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

I''ve started working on a new tool that should help with modifying the configuration of a system under the control of puppet. The tool is called cft (pronounced ''sift'') and is inspired by Gnome''s Sabayon[1] in taht it watches how an admin changes a system and spits out a puppet manifest based on its observations. Cft''s website is

Hello, I use puppet with RHEL and there are some packages that aren''t in up2date/yum repositories. I need a way to get these specific RPMs installed. There''s a blog posting that describes an almost-perfect way to do it: http://www.raskas.be/blog/2007/09/10/managing-user-passwords-with-puppet-on-centos/ The only problem with his example is that the RPM will always in the /tmp

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,

Out of curiosity, is anybody using puppet on RHEL3 (or Centos 3) ? If so, how did you get it to work ? Did you build a ruby-1.8.x or does puppet work on the 1.6.x ruby that ships with RHEL3 ? thanks for any pointers, David