similar to: Puppet starting before network is up

My first public-facing deployment of Puppet is likely to be on some parallel computing nodes we have here. One of our fluid dynamics packages expects to be able to rsh from one master node to other slave nodes in the same batch queue. I think I''ve made some good class definitions up to this last point, where code duplication rears its head. Example of the problem: class ch405-host

I''ve been working up my first puppet module, one that will make Amanda configurations consistently. In general, I''d like the following to happen: - Each Amanda server should make sure all its holding disks are configured properly; this should only happen once per server, per puppetd run. Definitely not on a per-configuration basis. - Each Amanda server should keep its

I''m trying to get a new file server managed by puppet from day 1, at least as much as possible. At the moment, though, there''s two issues I''m running into: 1. fstab should have entries for my comically-large RAID, but doesn''t. 2. each puppet run appears to remount the RAID, even when no rules in the manifest change. I suspect the issue may be in parsing

This appears to be working for me, but suggestions on improvements are welcome: master/manifests/definitions/stowedpackage.pp: > define stowedpackage ( $basepackage, $version, > $rsyncserver=''gold.cae.tntech.edu'', > $rsyncmodule=''metastow'', > $stowdestdir=''/usr/local/stow'' ) { > > file { stow_initiator:

I won''t claim it''s all done to the best style, but it does appear to work. Can someone take a look at http://blogs.cae.tntech.edu/mwr/2007/08/02/the-new-file-server-puppet-and-modules/ and give suggestions? It''s a bit more extensive than the example on the wiki at ModuleOrganization, and might make a decent jumping-off point for others. -- Mike Renfro / R&D

"The important thing to understand about how schedules are currently implemented in Puppet is that they can only be used to stop an element from being applied, they never guarantee that it is applied." A schedule does not say this will happen this often, it says this can not happen more than this often. Thus with the default half hour updates the proposed schedule would not have any

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

Hello, I''m trying to add an environment variable as fact like this : #export $FACTER_test="infof" #facter | grep test test => infof But my fact don''t synchronize with puppet master. I don''t see it in / var/puppet/yaml/clientfile.yaml If I want this works, I''ve need to start puppet like this : #puppetd -vt --factsync but factsync''s

Hi all, I''m a new puppet user and I''m running into some weirdness around creating users on solaris. (puppet version 0.23.2) The virt_all_users way of managing users seems pretty reasonable, but I don''t see how to deal with user specific groups with that. I have: class virt_all_users { @user { "seph": ensure => "present",

Hi, I have a template file which I would like to append to an existing file (in this case I wish to add a few lines to /etc/motd). Unless I''ve missed it, it does not appear that file has an append option. Is there an easy way copy to the end of a file Thanks Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google

I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and

Hi, When starting puppet on a new machine, (or when the $vardir/lib is empty) puppet will not run the facts, it will only copy them. on the second time puppet runs, it works quiet well: on the client its defined: [main] pluginsync = true pluginsource = puppet://$server/plugins plugindest = $vardir/lib/puppet factpath = $vardir/lib/puppet/facter [puppetd] factsync = true I also tried with

Part of my authentication setup is to keep clients'' secrets.tdb for Samba/Winbind on the puppetmaster. Since secrets.tdb contains the username/password for an Active Directory machine account, it will get changed by Winbind periodically, and I don''t want it those changes to get reverted by puppet. So I''ve got active-directory-member.pp, last modified August 19, with

I''ve got one node that doesn''t seem to want to load my custom fact. I''ve got ''factsync = true'' in my puppet.conf, and I know I can manually go onto the node and issue a ''puppetd -vt --factsync'' to get it to sync up, but I''d like to know why its not picking this fact up, because this could become problematic. Any tips on

Hi, I think the answer is no but is it possible to have a facter output from within puppet ? If i type facter on the command line i miss all the fact that puppet download with the factsync feature. How to see the output of facter including those of the factsync file ? -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list

So I have two classes for openvz setup. The first is openvz::setup and it sets up the box for OpenVZ.. then another class (in same .pp file) called openvz::master sets up the config for the main system (as opposed to a VE). The error I see is that the openvz::master class is executed (and fails) becuase it doesn''t seem to load up the setup class? debug: Calling puppetmaster.getconfig

Um, I don't remember the exact checkout command line I used, but it was probably something like the instructions on the web page: cvs -d :pserver:cvs@pserver.samba.org:/cvsroot rsync anyway, how do I update? I tried: [chris@lt2 rsync]$ cvs update -d -P cvs [update aborted]: connect to pserver.samba.org(66.70.73.150):2401 failed: Connection refused and login gives the same: [chris@lt2

Hello, I''m new to puppet and facter. Initially we are planning on using facter/puppet to inventory machines (Mac, Ubuntu, and RHEL). We plan on writing a number of custom facts. Obviouly some of the facts will only be specific to some OSs. I know there is a "confine" method, but it confuses me. It seems the confine statement in some of the recipes and in the Turnbull book is

I use the cvs version: cvs -d :pserver:anonymous@cvs.icecast.org:/cvsroot login cvs -d :pserver:anonymous@cvs.icecast.org:/cvsroot checkout ice2 cd ice2 cvs -d :pserver:anonymous@cvs.icecast.org:/cvsroot checkout avl cvs -d :pserver:anonymous@cvs.icecast.org:/cvsroot checkout log cvs -d :pserver:anonymous@cvs.icecast.org:/cvsroot checkout httpp cvs -d :pserver:anonymous@cvs.icecast.org:/cvsroot

Ooff! I am using ices2. Well that explains it then! I am new to linux and I thank you very much for your help and patience. Please just some clarification. To get cvs version of ices for mp3 streaming compatibilty with Icecast2: cvs -d :pserver:anoncvs@cvs.xiph.org:/cvs/ice login pw:anoncvs cvs -d :pserver:anoncvs@cvs.xiph.org:/cvs/ice -z 9 co ices or cvs -d