similar to: subversion verification on commit

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

Hi, I want to validate my puppet manifests before I check them into source control. I just want to make sure that the manifest syntaxes are legal, not to do any more complex testing - the checkin may be on my laptop and not on the system that the manifests may be intended to run on. Ideally I''d be able to do this from ruby code - and I did try to instantiate some classes and override

I''m trying to come up with a way to manage /etc/puppet on the Puppet server from my workstation. My idea was to place all of /etc/puppet into subversion, check it out to my workstation, commit via ssh, and then use a post-commit to update /etc/puppet. That way any time I made a change in /etc/puppet it would be immediately updated and ready for the next puppetd run. Problem is the

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

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

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

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

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,

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

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

Besides using an exec line with a case statement(to determine the specific os''s disable command), does puppet come with a buit in method to disable a user account? Thanks!. --------------------------------- Get the Yahoo! toolbar and be alerted to new email wherever you''re surfing. _______________________________________________ Puppet-users mailing list

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

I just built new puppet rpm''s for Fedora (puppet-0.22.1-2) that fix the lockdir problem that many of you have encountered. The packages should show up on a mirror near you very soon. Unfortunately, I am having trouble getting to my buildsystem that I use for the RHEL versions of the RPM; I made the source rpm available on my people page[1] If you need the RPM for RHEL, you need to

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?

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

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

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