similar to: Wiki Notifications

Hello everyone, I''ve been working on an internal best practices document that also tackled giving proper terms to things that were at the time uncoined. But looks like we have a bit of a merge problem as other terms have been floating around that seem to conflict with some terms we''ve been using internally at my organization. I''m hoping we can discuss and

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

Hello community, We are running puppetmaster 0.22.3 with 45 servers attached and we are seeing a lot of messages that say: (err): Could not describe /ssh/sshd_config.RedHat: End of file reached: We were seeing a lot of this with 0.22.1 as well. Interestingly, during the stretch where we were running 0.22.2 (most of April until 2 days ago) we didn''t see this error at all or very

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:

What is everyone''s experience with Puppet on Ubuntu? Does it work as expected? Any caveats or oddities? -- DK -- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University

Anyone using the rrdgraph report on the puppetmaster on Debian stable? I''m trying to get this working and not getting far. I even took rrdtool and librrd0-dev from backports and I still get the same problem. It seems that the rrdfiles are being somewhat created, but nevertheless, the puppetmaster isn''t happy and keeps spewing: err: Report rrdgraph failed: Could not create

Hello >From my understanding, modules are not autosearched. So, if I have: include ssh ... then puppet will look for a module names ssh and class named ssh defined in /modules/ssh/init.pp Moreover, if I have: include ssh::global ... then Puppet will for class global defined in /modules/ssh/init.pp or /modules/ssh/global.ss. Is that correct? Or am I leaving out some imports

What happened with the Mongrel effort? -- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University

I just discovered something interesting: node server.example.org { class A { ... } } The above doesn''t do anything. node server.example.org { include A class A { ... } } The above works. I was under the impression that classes defined within a node were assumed to be part of that node. I learned something new today. -- Digant C Kasundra

I think some conventions are in order to help with the documentation work. (1) As suggested by someone else earlier, I think we need a clear way to mark areas needing fixes with FIXMEs. (2) Topics under discussion or drafting should indicate such, perhaps at the top of the document, with a reference to the thread. On page comments should have a clearly designated area at the bottom of the

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 recently update my remotefile definitions (others might have already done so or have been using a better one than mine). I added an ensure parameter so I could do overrides using remotefile rather than the underlying file: define remotefile($owner = root, $ignore = ".svn", $group = root, $mode = 644, $source, $backup = false, $recurse = false, $ensure = file) { $realsource =

Hi all, I''m very happy to see how quickly the Puppet community is growing and how pleasant and helpful everyone is. It seems like people are starting to handle a lot of the questions on the email lists and IRC, which is great because it means I can focus more on development and planning. There are a few areas that don''t seem to be meeting the community needs, though,

-----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 =

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 all, I''ve got a new class in the current code, which I''ve been calling Configuration but Matt reasonably thinks is horrible. He is recommending the name Manifest, and I figured I''d see what others thought. The point of the class is to function as a resource container -- it keeps a reference to all of the resources we''re managing, and knows how to

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

file { "/var/log/syslog": target => "/var/log/messages" } generates the following error: err: //henson/stanford/syslog/file=/var/log/syslog: Failed to retrieve current state: undefined method `should'' for false:FalseClass

I''ve published the tarballs and whatever bad packages my publishing system knows how to create; look for more official debs, sun packages, and rpms in the near future, hopefully. Note that this is mostly a bug-fix release, and I expect it to be a pretty painless upgrade for most everyeone (but please, test before upgrading). Here''s the changelog: Compile times now

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?