similar to: Puppet updating from relative directories or chroot

Hello All, I''m new to puppet, and I''d like to know: Is there a formal best practices guide for syncing { /etc/passwd, shadow, group, hosts} across clients from the master? For instance; is it a better practice to make a hard link to these files and share the link, as opposed to just sharing the files directly via a target in fileserver.conf? Inquiring minds want to know...

I have this in nodes.pp $puppetmaster_fqdn = generate("/usr/bin/facter","fqdn") and this in a template http://<%= puppetmaster_fqdn %>:8080 When puppet runs, this is the result: http://puppet.home :8080 Anybody any clue to whats causing this? I''ve tried -%> -- You received this message because you are subscribed to the Google Groups "Puppet

G''day. I am wondering what the current best practice for building a single file out of distributed fragments is with puppet. Specifically, my problem: 1. Install munin-node on arbitrary machines. 2. Install ''munin.conf'' as a single file on one machine, containing a configuration stanza for every machine that munin-node is installed on. The current best practice

Hello All, Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred directory structure for using multiple environments? Does it work much different in 2.6 than in 2.5? When I made the move I assumed (I know) that my current structure and configurations would just roll over but that isn''t the case. Thanks, Jim -- You received this message because you are subscribed to the

Hi, First of all, this is my very first message to this list, so please bear with me while I''m getting used to it. Sorry for any non-standard way to ask a question here which I can be using without prior knowledgment. I would like to be able to set up some config parameters on a given node which is going to be config-managed by Puppet and, for various reasons, I would like to be able

My manifest includes this snippet class app_client_openbsd { $app_client_pkgs_obsd = [ ''glib2-2.24.1p2'', ''gtar-1.23p1'' ] package { "${app_client_pkgs_obsd}": ensure => ''installed'', source => "http://${installserver}/openbsd/${operatingsystemrelease}/packages/${hardwaremodel}/${name}.tgz", } This

I''m running into an issue trying to do something like the following: class test { file {"test": content => template(''mytemplate1'',''mytemplate2''), } } class test::test2 inherits test { File["test"] { content +> template(''mytemplate3''), } } So, basically I want the inherited class to tack on another

Hi all, We''re writing a few scripts at the moment that could really make use of Facter, however the vast majority of them team (including my self!) are not proficient in Ruby, however they are highly proficient in other languages such as (dare I say it!) Python. Is there (or are there any plans to!) release bindings for other languages to enable facts to be used in scripts other

Hello. I use puppet 2.6.3-rc2 Now I try move my classes to modules. But I got a problem that Puppet does not sees modules. in puppet.conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl libdir = /opt/puppet-dashboard/lib/puppet modulepath=$confdir/modules In nodes : node postgres { include basesystem include postgres } In

Hi, I''m building a staging environement and I would like it to be able to redeploy automatically, after each commit - or every hour, some applications. Those applications are right now deployed and set up by puppet. I wonder if I should use puppet to redeploy those applications after each commit, and if I should how trigger, on the puppet, a full redeployement of the application ? --

G''day. We recently found some issues with the `links => follow` setting in recursive file copying; the designed behaviour is that it should allow you to determine if the master serves a symlink in a module as a symlink, or as the content of the file that the symlink points to. The full details are here: https://projects.puppetlabs.com/issues/12418 The short version is that toggling

Hi, When I start puppetd on my client machine I get this message in /var/ log/messages: Parsing /etc/puppet/puppet.conf reopening log files could not request certificate; retrieved certificate does not match private key; Please remove certificate from server and regenerate it with current key Could not retrieve catalog from remote server Using cached catalog Could not retrieve catalog

Hi, I just added an external classifier script, and things are not working as I expected to. Trying to read documentation about ext.nodes and searching the archives I couldn''t come up with any useful results. My classifier script outputs: --- YAML --- classes: - geodns::production::backend environment: production name: z01-06-02 parameters: puppet_server:

Hey all, I''ve open-sources Digg''s apache module: http://github.com/plathrop/puppet-module-apache I know this isn''t much more advanced than what I''ve seen a lot of people using. Here''s my proposition, though. Let''s get all the disparate "apache" modules out there merged together into One Awesome Module. What do you think? One module

Hello, I searched through the archive of the google group but did not found any solution or hint for my problem. I want to assign the following parameterized class to a node. class httpd($certMail, $certOU) { ... } This is the node statement to assign the class to a node. node "someserver" inherits basenode { class { httpd: certEMail =>

Hi I have a requirement to generate several very similar config files which are just a couple of tokens different and with different names. These are barnyard conf files if anyone is interested and differ only in the interface name which is also part of the file name. I can include [eth1, eth2] in the manifest and I want to get files: barnyard.conf.eth1 ..... interface eth1

So, my configuration attempts are aimed at Linodes . Ubuntu 10.10 to be exact. Linodes are libcloud enabled as well as basically provisioned. What I seek to do is add to that, not build from nothing, since libcloud et. al. give me a base to work with. What is the canonical way to manage this situation? For example: $ puppet resource package --verbose openssh-client package {

Hi, I am working on some tools that read and write pp files, and I wonder if there are some pp files available somewhere that can be used to test a parser. I am especially interested in if there are some tests written that capture invalid syntax. - henrik -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send

Hi, suppose puppet-old.domain is a CNAME pointing to puppet-new.domain, and puppet-new.domain is running Apache (for SSL) with mod_proxy_balancer to balance over some 10 puppetmaster processes. The configured SSLCertificateFile in Apache is that of puppet-new.domain How do I get a node to stop complaining when connecting to puppet-old.domain (ending up at puppet-new.domain through the CNAME)?

Hi. Lets say that for several administrative/burocratic/procedural reasons, you dont have the option of running puppet as root, in any way - not as a daemon on the managed node, nor as root on the command line with puppet apply. Say, you are the "middleware" application team and you dont have the rights to touch any part of the server that are not your apache/tomcat/whatever instances,