similar to: Developers having access to deploy

Hello All, So I finally got around to start to cut over node definitions from standard flat files to external nodes (foreman), and getting error message: "Error 400 on SERVER: Could not find node ''nodename''; cannot compile" - So basically it can''t pick up the node from the external node config. When I test the fetching of the yaml file it seems to work

Hello, I try config puppet with foreman frontend. Into puppetmasterd I create modules "test" and create init.pp: # Create "/tmp/testfile" if it doesn''t exist. class test_class { file { "/tmp/testfile": ensure => present, mode => 644, owner => root, group => root } } Configure nodes in site.pp and import

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 everyone, I’ve been working on getting puppet set up for our systems for the past week, and all has gone well in learning about writing manifests, but now that I’m ready to set it into production, I realize that it’s still unclear to me exactly how that’s supposed to go. For instance, during testing it has always been that I manually started and stopped puppetd and puppetmasterd on their

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

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.

# cat /etc/redhat-release CentOS release 6.4 (Final) # puppet --version 3.2.3 # rpm -q puppetdb puppetdb-1.3.2-1.el6.noarch I am now receiving "Not collecting exported resources without storeconfigs" for my opsview module. It was working fine on puppet 2.7 with Activerecord/MySQL. I am still new to puppetdb so maybe I am missing something. This is from puppet.conf: storeconfigs

After an unexpected and unreasonably long hiatus, I''ve finally returned to implementing Puppet in my environment. My puppetmaster: Puppet 0.25.4, Facter 1.5.7, Ruby 1.8.7, and FreeBSD 8.0. I''ve got five clients using the puppetmaster so far. After about 24 hours, I''ve got three puppetmaster processes running. This number continues to grow over time. If stored configs

Hello Everybody, We need to open some ports on the target machine, let''s say 694:udp and 3306:tcp I couldn''t find any documentation how can I do this with Puppet. What the best way of doing this? Thank you Dmytro -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

Hello, I would like to ask your advice for the simplest method to do deployment on a debian server. From my perspective the system should look something like this : # web server node node "prod.domain.com" inherits webserver { webapp::project{app1: domain => "app1.com", package => "app1", version => ''1.1.2''

Hello a newbie here. The situation is that: 2 machine one master one client Puppet 0.24.5 This my configuration: Client: /etc/puppet/puppetd.conf [puppetd] server = Asus-Vista-Box logdir = /var/log/puppet vardir = /var/lib/puppet rundir = /var/run master /etc/puppet/manifests/classes/sudo.pp class sudo { file { "/etc/sudoers": owner => "root",

I''m playing around with foreman for the moment. I can''t seem to figure out how to make the dashboard look like in this screenshot http://theforeman.org/wiki/foreman/Screenshots#Dashboard In order for those statistics to work what should be done? I have activated the rrdgraph reports in puppetd, uncommented the line ":rrd_report_url: report/" in config/settings.yaml

on my puppet master server (v 2.7.17 , both server and client version) , the puppet agent can''t connect to itself. other clients connected to this puppet server are working fine. the hostname is puppet.domain.com [root@puppet /]# cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hello all. I have a problem with custom types that I create: I have changed the apt package provider such that it it uses fink on darwin operating systems to install packages. I copied the apt.rb to fink.rb and customized it accordingly. Now when I follow the documentation: http://reductivelabs.com/trac/puppet/wiki/CreatingCustomTypes I should deploy it in lib/puppet/type. This does not

HI. Firstly, I''m bound to be doing something utterly basically wrong here, so if I am I apologise. Right now I have a fairly simple setup where the JAR files for a Weblogic-based application server are stored in the file server on my Puppet Master. I run scripts on the client that downloads the files from the file server, puts them in the right place etc etc. All very simple. I am

Hi, I''ve got some problems with setting up environments. On the master: [main] [...] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [...] environments = production,staging [production] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [staging] manifestdir = /opt/puppet-staging/manifests modulepath = /opt/puppet-staging/modules [puppetmasterd]

Greetings: Sorry for cross-posting this question, but I haven''t gotten any love over on the Google Forum for Foreman users<https://groups.google.com/forum/#!forum/foreman-users> (their forum isn''t as active as this one). I only recently learned about The Foreman and I''d like to deploy it on a 64-bit Ubuntu 12.04 LTS workstation to provision/manage a bunch of