similar to: Ubuntu experience

--On Monday, May 14, 2007 9:16 PM -0700 Jos Backus <jos@catnook.com> wrote: > ObPuppet: we ramping up our deployment this week to around 200 hosts. So > far everything has been going smoothly. We don''t have nearly as many and yet, we see occasional errors ("End of file reached") which seems to indicate the network cutting out. I can''t imagine what would

Is it possible to specify an arch type (e.g. i386 or x86_64, etc) when using the package resource type? -- DK

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

I know people must be doing something to manage iptables, but I haven''t been able to find anything yet. ( My google-fu must be weak today. ) What are you using to manage your iptables? -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers--

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

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

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 would like to write up brief tutorial/documentation on how to manage /etc/passwd using puppet. While this may seem pretty straight forward to some...the documentation is not. We have been able to create a manifest that defines all of our users "virtually" and are able to "realize" users and add them to the system(s) running puppetd. Is there a way to simply realize all users

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

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:

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

Anyone ever migrated the puppetca to a different host? What are the steps that are involved?

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

I''ve been thinking about how to make Puppet a killer app, and I think there is one specific thing that could be done to help make that happen: People using Puppet now to consistently state what they *really* wish Puppet could do for them -- the recent thread around Puppet on Windows is in that vein, but it''s not specific enough. For example, I''d like to know what

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

Hello, I am currently experiencing a bit of a quandry with how to specify default configuration applications to generic nodes. Here is an example setup: Classes: Class A Class B inherits Class A Class C inherits Class B Problem: I have unique hosts (nodes) X and Y and a bunch of other standard hosts. I would like X and Y to be able to override attributes in Class C (thus inherit class C) but

In the normal override method, you can change the value of a parameter, but can you unset a parameter? file { "/etc/somefile": mode => 644, owner => "dude" } File ["/etc/somefile"] { mode => unset } ??

Hello Puppet users, I had talked with Luke about this scenario and was wondering how others would/are handling something like this. Imagine a scenario where all servers will have a specific postfix configuration except for a server or two or three. So, you want to define a file "/etc/postfix/main.cf" and specify the source from your dist tree. But for those exceptional servers,