search for: moduleorganisation

Hey folks, I''ve just uploaded an apache2 module[1] to our Google Code repository[2]. It''s based largely on the recipe available on the Puppet trac[3], but with a fair amount of modification and generalization... Basically, it provides abstractions for config file snippets, site definitions, and apxs modules -- and then "basic" and "debian"

I tried to install the ''mongrel'' gem tonight via puppet in an attempt to migrate from webrick to mongrel as described on the puppet site[1]. I added the following to my manifest: package { "rubygems": ensure => installed; "mongrel": ensure => installed, provider => gem, require => Package["rubygems"]; }

I updated http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation to reflect how I intend to implement modules, and what that will look like from a user''s point of view. Comments/flames etc. welcome. David

Hi, I''m starting to move over to Modules, which looks pretty clean and solid. Reading http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation, one thing that confuses me is how the client resolves the implicit file server resources. I''ve got a few different puppet master servers running on different ports, and my configuration re-defines $puppet_master_host and $puppet_master_port globals depending on which master the client is...

...dule webserver needs module funky_yumrepos), though that would probably not affect puppet itself, just the tool downloading modules, like prm. * My previous writeup at [2] should probably die; I''ll delete the page in a few days David [1] http://reductivelabs.com/cgi-bin/puppet.cgi/wiki/ModuleOrganisation [2] http://reductivelabs.com/cgi-bin/puppet.cgi/wiki/ModuleOrganisation

Hi, I''m new to puppet and trying to get started using it just in local mode. My basic question is: how can i reference a static file within the module (eg in the module''s files/ subdirectory, as described in http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation). I suppose i could try using a full.absolute path to the file, but that seems to completely defeat the purpose of a module. I overcame my first hurdle - which was getting puppet to find the module at all. I created a puppet.conf containing a modulepath declaration. At this point, even without...

Ok, I''ve been reading and I have some questions about best practices: I understand that modules are to be self contained blocks that i can just drop in. Using best practices, how does this fit into the naming scheme? Classes are singletons. I think i understand this. I''ve been defining classes in /etc/puppet/classes, but then how does this relate to any modules i might want

Hi all, I''m proud to announce that I seem to have pushed a new release of Puppet out in record time. This is a minor upgrade, mostly bugfixes and small features, but there are lots of each. See the changelog[1] for an idea of what this release provides, but keep in mind that this changelog is my first real attempt at keeping an up-to-date changelog. Enjoy! 1 -

Greetings - Maybe I''m a bit slow, but I''ve been trying to understand how to use a module for the better part of a day and I''m not getting it. Here''s what I''ve done: Using puppet 0.23.2 1. Downloaded the shorewall module from David Schmitt''s git repo (Thanks David!!!!) and placed it in the directory /var/lib/puppet/modules (using the rpm

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

Hello everyone, A long time ago, I posted the Stanford Best Practices and I''ve gone through and updated it today. I''d like to have people go through it and see if we can strip out some Stanford specific stuff and tag this as an official best practice. I think an official best practice will be important as more and more people consider making shareable modules, etc (mostly

Hi, [First, a quick introduction... I''m one of the sysadmins at Koumbit.org, and we''re evaluating puppet for managing our modest server farm. I''ve already started writing recipes and manifests and intend to share those with this community. Part of my time worked on this will be directly paid by Koumbit.] So we''ve got a few half-finished puppet modules here:

Hi, I was talking to Luke today about managing manifests and related files, and he suggested that I post to the list.. What would be nice (and what I''ve use in in-house systems I''ve used previously) is to have a way to dynamically include manifest fragments at runtime. Lets assume that you''re setting up bugzilla using puppet. In the ''main'' manifest

I finally got my cfengine configs all objectified and separated into service-based configurations. But there are still many things that cfe can''t or won''t do very well, so I''m looking for a replacement. What about puppet? I am looking for something that I can use to manage services and applications, not hosts and files. It seems like puppet may have inherited some of