similar to: Puppet Best Practice (moved)

Another point of disparity between how I see others write Puppet manifests and the Best Practice that I''ve adopted at my institution is the use of quoting. In Puppet, you can get away with not quoting values or references if there isn''t a special character or a keyword being used (e.g. package { openssh: ...} or User[agirl]). However, even though that is possible, to make

I''m sure everyone has read and committed the Puppet Best Practice to memory by now (I joke). One of the things I''ve written in there deals with trailing commas, which I adopted from the way I used to do multiline in Perl, but I''ve noticed that most people don''t tend to do that in Puppet. Should I revise this or should we all start using the trailing commas?

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

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 like the Stanford Best Practices guide for puppet. One thing I didn''t see it address was handling of separate environments, for example Dev, Test, Staging, Production. My thoughts on this so far, are: brainstorm #1) Handle environment differences with metadata: node devProductName01 { $env = "dev" include ProductName-webserver } node testProductName01 {

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Russ, Digant, *! Several times on the IRC channel I noticed people having problems getting to grips with the interaction of scopes when using template nodes[1]. Typically this looks thus: | node genericwebserver { stuff } | | node ''web01.example.com'' inherits genericwebserver { | $influence_genericwebserver =

Hello folks, I''ve finally figured out how to get the Wiki to notify of changes. Luke is going to work on getting a proper link in the header but for now, make sure you are logged in and then if the page you want to watch is at: <http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms> then in your browser URL, substitute "notification" for "wiki":

Hi, https://reductivelabs.com/trac/puppet/wiki/DocumentationStart https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction https://reductivelabs.com/trac/puppet/wiki/PuppetMasters https://reductivelabs.com/trac/puppet/wiki/PuppetBestPractice - Max

Hi all, In a fit of helpfulness and working on my IRC-to-Wiki-conversion, I created a place where to add tips for new users. I couldn''t find it anywhere else on the wiki, except for a primer in the documentation. Feel free to add to it (and please do!!): http://reductivelabs.com/trac/puppet/wiki/ConvertToPuppet -- Gegroet, Tim

Hi, While puppet creates its own directories for internal stuff (puppetca, state, etc.), there''s a fair bit of latitude given to where things like manifests and uploaded files live. I didn''t get much guidance from the docs when I first set things up so I mostly poked at things until the worked. Take a look at the following and let me know if this looks reasonable; if so, it

I might have the terminology wrong, but how to a give new puppet providers to the puppet clients? I''m thinking a provider is the thing the puppet client uses to implement a task that the master has given it. Am I way off here? Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

For anyone that has experienced the odd End of file or Cannot describe errors, we''ve found that switching to Mongrel has fixed this problem for us. We''re currently running 5 instance of puppetmaster under mongrel (with the apache proxy in front) and things are going great. For more information on setting up Mongrel, visit:

Hi, I''m a new puppet user (thanks !) and I''m just looking at moving my homegrown manifest structure into something resembling the best practise guide at : http://www.reductivelabs.com/trac/puppet/wiki/PuppetBestPractice. It seems as if the structure here doesn''t map to the default puppet layout (and thus doesn''t work with the standard puppet config

Hello folks, I''ve blended/updated the Glossary of Terms (<http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms>). It seems the definition of "manifests" is a bit different amongst members. Some people consider a "manifest" to be a configuration file written in puppet, e.g. any .pp file. But at my organization, we''ve considered the totality

I turned on reporting the other day and I''m seeing alot of these when puppet runs. Especially during times when nothing is going on (middle of the night etc) Tue Dec 11 12:34:48 -0500 2007 //base/puppet/puppet::client/Service[puppet]/ensure (notice): ensure changed ''stopped'' to ''running'' It''s also quite odd that puppet when it runs it thinks

I am new to Puppet and very eager to apply it to a project. But I am somewhat stymied by the learning curve. So far I''ve found many very simple examples of how to modify a file or add a user and a very complex example http://reductivelabs.com/trac/puppet/wiki/CompleteConfiguration . I have not been able to find any other examples of a total configuration tree (ie /etc/puppet/*)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi *! How do you monitor when the last puppet transaction was successful on a node? I''m searching for something easy like a timestamp, so I can put a nagios watch on this. Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb,

Is there a way to tell the puppetmaster that I want to import all modules rather than listing each one individually?

I have been all over the wiki pages for puppet and I have noticed that all the configuration examples seem vague. Does anyone know of a good solid resource for start to finish configuration of puppetmaster and puppet (server and client)? A step by step guide would be great.

Hello! In my puppet configuration I need to get some data from database. Ie.: I''ve got information about my all hosts in db - thier name, mac addresses, ip addresses, what to backup from this host etc. For now it''s just .xml file, but it could be sql db, or ldap directory. Then, using this small "database", I want to generate configuration using puppet - ie.: