similar to: Multiple Environment Support

Hi Does anyone know if the following is supposed to work? ------------------------------------------------------ site.pp case $psi_rank { Devel: { import "Devel/psi_gfa/*" import "Devel/nodes" import "Devel/os/yum_update" } Prod: { import "Prod/psi_gfa/*" import "Prod/nodes" import

Hi all, I''m sure you''re all wondering what the heck is going on with development and why there are so many open tickets. Hopefully this email will answer those questions for you. REST Development ====================== First, I''ve found the REST work to be significantly more complicated than I''d feared. The plumbing is nearly all done and the majority

I''m about to leave town for three weeks and my home server keeps rebooting. It''s my mail server, unfortunately, so there''s a good chance you won''t get this. :/ Anyway, I''ve been meaning to do this for ages and ages, and it''s time to finally do so. I need to move all of the Puppet lists to a public, non-me provider, someone who has

So I can''t quite see how to do this in the existing syntax. Ideally there would be an onlyif parameter for packages, but that doesn''t seem to be the case. I could create a fact that returns true or false depending on whether the file exists, but that doesn''t feel like the right way to do it either. I could do something like: $file_exists =

Can anyone who''s having this problem please send details? I''m trying to reproduce it -- I''ve got 5 clients concurrently retrieving 200 10k files made of random binary, and I can''t get any corruption or memory growth at all. Is everyone experiencing the problem using Mongrel? Webrick? What versions of ruby? Are only big files affected? Small files?

Ok, given the statement on the web page about unlesssystemuser under Resources ( http://reductivelabs.com/projects/puppet/documentation/typedocs.html#resources), I assume that users can be purged. However, when I attempt to do this with resources { user: purge => true, noop => true } and what I get is: err: Found a bug: private method ''split'' called for nil:NilClass.

Hello, I want a simple operation in a puppet node like restarting the ssh service if it was stopped. My site.pp is simple as this: import "services/*" node default { include ssh } The services directory as a ssh.pp : class ssh { service { ssh: ensure => running, subscribe => File["/etc/ssh/sshd_config"] } } I''ve stopped the ssh service in the

Hi, I came across a use case where I would like to access a value of an attribute of a particular resource. I cannot find anything like this in the documentation. Essentially, I am trying to do something like this: $cacert_path = Base::X509::Cert["cacert"].path Did I miss something in the concepts? Thanks, Jan --~--~---------~--~----~------------~-------~--~----~ You received

I posted this earlier on IRC, but it didn''t seem anyone was active: <mozillaman>Hey all! <mozillaman>Quick question for you :) <mozillaman>I installed puppet according to the directions on the site and got this: sudo /usr/bin/puppetmasterd --nonodes undefined method `retrieve'' for nil:NilClass <mozillaman>Anyone have any ideas? Any help would be

So I''ve done some Mac OS X pkgs for the latest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

So I''m still working on a ''perfect'' setup so I can document it on the wiki, and will submit some puppet patches against 0.23.2 next week, but here''s what I''ve done that has made a big difference to stability here. in puppetmasterd at line 261, I''ve modified the Mongrel instantiation from: server = Mongrel::HttpServer.new(addr,

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

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 there, I''m running puppetmasterd manually while testing, and I was trying to split my manifest in several parts using import. If I do so whenever I run the puppetmasterd the manifest gets loaded and served correctly: cognos ~ # puppetmasterd -v info: Starting server for Puppet version 0.20.0 info: Parsed manifest in 0.02 seconds info: /var/lib/puppet/files: allowing *.example.org

Hi - I a ran puppetd -vt against a brand newly build host (which is what I normally do for a new host) and got the usual message: err: No certificate; running with reduced functionality. info: Creating a new certificate request for sega-dev-1. info: Requesting certificate On the puppetmaster, I then list the waiting host with: puppetca --list then sign the key. In this case, I decided that the

Hi, I''ve just changed my debian preseed configuration to install the debian unstable package of puppet v0.22.1. As part of the preseed I have a late command that clobbers the /etc/init.d/puppet file into using the puppet standalone program and not the puppetd (as this is what I''m using). Since the upgrade to 0.22.1 every boot hangs during the initd. Going into standalone mode

So I have the following: define nagios::service ( $nagios_template = ''service-template'', $host_name = $fqdn, $service_groups = '''', $contact_groups = $default_contact_group, $max_check_attempts = 3, $dependency = false, $dependent_host = $fqdn, $dependent_service = '''', $check_command = '''' ) {

I have the following in my site.pp node "pclient.example.com" inherits default {} When I try to start puppetmaster it gives me the following error Starting puppetmaster: Syntax error at ''pclient.example.com'' at /etc/puppet/manifests/site.pp:24 When I change the node declaration to this node ''pclient.example.com'' inherits default {} puppetmaster

I forgot to mention this in my announcement yesterday. Puppet facts are no longer downcased in the language, and string comparisons now default to being case-insensitive. Where your operating system might previously have been ''solaris'' or ''debian'', it is now ''Solaris'' or ''Debian''. However, you can still do comparisons