similar to: HTTP as a source for files

I''ve been using ''define'' to make a few custom types. For example, I have a simple ''file'' like thing (s3::file) that downloads a file from S3, only if the one on the local machine doesn''t match, and it can send out notifications if the file changed. This is basically an exec command that uses some scripts I wrote in an

I am wondering how to manually (using openssl instead of puppet cert command) create CA that would be usable by Puppet? The goal would be to script creation of such CA''s to deploy them on multiple puppetmasters, instead of certificates being created on them via puppet cert command. Any ideas on how to do it? I was only able to find something like that:

Hello, i have a couple of VLAN where each has its own subnet, now I would like to use one puppetserver for all these machines. the puppetserver has a DNS entry for each subnet and its own IP-Address VLAN 1: puppet-vm1.domain1 172.1.0.1/255.255.255.0 VLAN 2: puppet-vm1.domain2 172.1.1.1/255.255.255.0 ..... the hostname of the puppetserver is puppet-vm1.domain0, puppet created a

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.

I was looking into the reporting features in puppet today and realized that though I want the reports I don''t want to bog my puppetmasters down with the task of generating the rrd and png files. Also I already have a server set up to do reporting on various other things that already has the space/CPU cycles and that''s where everyone already goes to look for information. Plus we

Is is possible to have a puppetmaster that is a client of a different puppetmaster? We manage our customers'' server via puppet, but one customer has a puppetmaster server which looks after their internal systems. We''ve tried the following in /etc/puppet/puppet.conf ("customer" and "us" replacing the domain names) on their puppetmaster: [puppetmasterd]

Hi, I was wondering what people out there are doing to monitor puppetd in large environments. I''d love to hear what the best practices are around this. We have a few hundred hosts and are currently looking at the timestamps on the yaml files in /var/lib/puppet/yaml/facts/ on puppetmasters to make sure all clients are alive. Is it true that for a given client the fact file on the

Hi, we are currently managing our puppet modules with one SVN workspace for each admin. The post commit hook script updates /etc/puppet/ directory and triggers the puppet kick of the correct server. The problem we have with this solution is that sometimes there are many small checkins to one change, because the admin forgot to change small details in the config file, e.g. forgot to change

All, I''m trying to figure out the best way to estimate the amount of memory usage that will be taken up by Mongrel and I''m hoping that you have some estimates that can help me. I''m currently estimating the following: Memory Required = Number of running puppetmasters * size of manifests * number of clients managed The mongrel model doesn''t seem to *ever*

Hello I am thinking that it is better to do a cvs export of a project once, on the puppetmaster box, rather than do the same cvs export on all puppet clients, yes? If so, how does one do this? Do you run puppetd on the same box as puppetmasterd and set up the cvs export as an exec for only the node with the same hostname as the puppetmaster? Thanks Jesse Jesse Reynolds Virtual

I had some questions come up today during the Puppet demo here: 1. Is there any way to apply different intervals to different classes? For example, we might want a security baseline manifest to run once a month, package installation files once/day, etc. Since we''re a brokerage, we also don''t want ANY system changes during trading hours. I guess we could cron killing the

hi, i''m trying to set up my puppetmaster infrastructure with multiple puppetservers behind load balancers in each of our datacenters. i''m using 0.24.6. i''ve read the howto on puppet scalability, and i think i''ve got the ssl config working correct, but i''m noticing that when puppetd is used to build a puppetmaster, some of the files in $vardir/ ssl

Howdy, our puppet master is hosting nagios at the same time. it happens that the compilation of the catalog for the master during a puppet run produces a timeout: === err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run === If the whole nagios part is commented out for the master host

Hi, I''ve created two Nginx patches (see at the end of this message) to allow a simpler Nginx configuration for your Mongrel puppetmasters. The two main issues with Nginx in front of puppet were: * no CRL support * no optional certificate verification (and thus we''re forced to have two separate configs on two different ports, and to use --ca_port). Now, it is as simple as

I am trying to setup Puppet + Mongrel on RHEL5. So far I have followed this document: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel_On_Enterprise_Linux The puppetmasters all start up and Apache starts up on 8140. However, when my client connects I get the following errors: [root@lv1764p puppet]# puppetd --server puppetdev.encana.com --no- daemonize -o -v info: Retrieving

YASP... Yet Another SSL Problem, this time on puppetrun. $ sudo puppetrun -p 10 --host anotherhost -t aze Failed to load ruby LDAP library. LDAP functionality will not be available Triggering anotherhost Host anotherhost failed: Certificates were not trusted: tlsv1 alert unknown ca anotherhost finished with exit code 2 Failed: anotherhost Running with "strace -f" shows that

I have a 3 different puppetmasters running different groups of machines (dev, testing, and production). I''d like to very simply say "Give me a brief summary of the status of the nodes you manage." I''ve been having nightmare dependency problems trying to get things like Dashboard running that seem to be able to do this (Ruby, which may be an elegant language, is very

Hi. Have anyone ever managed several geographically distributed systems with Puppet? I have several almost exactly similar deployments (except the server IP''s), which management I''m looking to convert to Puppet. I have 2 options: * Have each deployment to host it''s own PuppetMaster for providing local configurations, then synchronize somehow the PuppetMasters (maybe

Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd

I have updated the 1100 clients that prior to the update used to connect to the master just fine. Now after about 30 minutes of running, puppetmasterd starts to complain "puppetmasterd[6875]: Too many connections", and from that point forward will stop compiling catalogs. Puppetmaster is configured using the Mongrel Apache configuration as described here: