similar to: Parent directory handling of file type?

Hi, I''m testing puppet from the subversion trunk. I have a rather hacked-together system to install a CRM into one of my nodes, which worked (more or less) with version 0.19.3. When I tried to do a puppet run on a completely clean node it seemed to stall on the ''compilation'' part (I do an exec of ''perl Makefile.PL'' in the appropriate dir). When I broke

Hi all, I''ve been looking for a good example for how one would build a module, but I couldn''t really find something that I liked, so I went ahead and tried to do it myself. The result is this: a git module (see attachment). Please have a look and comment on it, before I add it to the wiki. I especially want comments on the setup of the module itself, not so much on the git

Hi folks, I''m overriding some resource attribute in a subclass. It seems that specifying a resource by its alias doesn''t work in a subclass. Looks like a bug, no ? === module-classes.pp === class module::base { file {"/tmp/test-module": alias => test-module, content => "module::base", } } class

I''m using the external_nodes functionality to read in a flat file of a node''s configuration. Currently said file is a straight yaml file (just to keep things simple). The place I''m currently stuck is in doing some more advance node configurations and placing that data in the yaml file. For example: node ''foo'' { $var1 =

Hello all. Probably this question has already been posed in the context of another software, but I am unable to find it. I would like to implement a module which should manage munin-clients as well as the munin-server. Here is what I am thinking about implementing: - There are two classes: munin::client and munin::server - munin::clients'' configuration will be managed automatically.

Hi guys, Has anyone yet tackled installing CPAN packages through puppet? I need some that aren''t available as separate debs, so if anyone has an idea how best to do this, I''d like feedback. Thanks, Thijs

Hi all, Is there a (simple) way to add conditionals to a call to a define? What I want is to run a define only if a file (that gets created somewhere along the run of the define) does not exist. In this way I can skip a whole lot of setup work in the define if I know it has already run once before. I would think adding a unless clause would be a elegant solution (and the other conditionals like

Hi guys, Unlike what it says in the documentation and the --help output, I can''t seem to get puppetd to use the --server setting. The only way I can get puppetd to work is to include a ''puppet'' alias to the ip of the machine I''m running puppetmasterd on in my hosts file. The strange thing though, is that the logs of my puppetmaster show that it *is* getting

OK, I started down this road a few months ago and got side tracked with project work. I have a class called "install" that I want to use with only machines on one protected subnet. In my site.pp file, among other node entries, I have - node default { install } The class itself - class install { case $domain { "test.example.com": { file:

I added ntp to my servers running with puppet. These are all Ubuntu machines, btw. I get the following in the verbose output: {{{ warning: Service[ntp-server](provider=debian): Could not start Service[ntp-server]: Execution of ''/etc/init.d/ntp-server start'' returned 256: * Starting NTP server... notice: /base/Service[ntp-server]/ensure: ensure changed

On 12/06/07, Luke Kanies <luke@madstop.com> wrote: > > On Jun 11, 2007, at 12:01 PM, Thijs Oppermann wrote: > > > But they don''t always work. For example, in the example (a bit > > like) above (which was what I had in my git module definition for > > clientsetup): > > > > file { "/home/${user}/.netrc.d": > > ensure

Hello, I want a simple operation in a puppet node like restarting the ssh service if it was stopped. My site.pp is simple as this: import "services/*" node default { include ssh } The services directory as a ssh.pp : class ssh { service { ssh: ensure => running, subscribe => File["/etc/ssh/sshd_config"] } } I''ve stopped the ssh service in the

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''ve been watching the thread where Luke is having to spend time defending his position about documentation. Can we get off that? From my perspective, Luke, I''m glad you have documented as much as you have. I''m one of the few who have been a little stymied by what documentation is available, but in no way do I believe berating you for your lack of documentation is a

Hi all, One of the major new features in the upcoming release is that Puppet now uses a graph library internally to handle resource relationships. The big benefit to all of you is that you can use this library to turn these graphs into images. The trick, right now, is adding --graph when you run puppetd. This creates .dot files, which can then be interpreted by the

First of all, in the thread ''Using multiple values for source, for platform/arch/host configs'' Jason said: "I would really appreciate any examples, or further advise anyone has." -> I heartily second that. A good start would be to fill in the cookbook, as Luke has been quietly whispering here and there. ;) Then my other main question at the moment is: what version

I''ve been using Puppet now for a month or so and I''ve come to a problem that may warrant an additional Puppet metaparameter. I''m advocating the addition of a metaparameter called "preaction" (or something like that), which will perform some arbitrary action before the resource is modified. There may be a way to do this within Puppet already (with some

OK, too bad. I could work around it of course by adding ''unless'' and ''creates'' clauses on all the individual parts of the define where appropriate, but I think I''ll just ignore the warnings and overhead for now. It would be cool, though, if something like the ''unless'', ''onlyif'', etc, logic was available for all

Hi, In our dev/int environemnts, our user base wants to be able to change managed files at will during the day but be notified via email of changes that happen. At night they want the files replaced to their known good state if there were changed. I tried to do this with a custom function that wraps two file types, one that just watches checksum, the other that does a reset of content with a

Hi, is there a way to make sure a file is installed only if a certain package is installed on the client? e.g. I want to distribute the client key for NX via puppet. However I only want to install these files if package ''freenx'' is installed on the client. I tried adding ''require => package["freenx"]'' but then puppetd complains it