similar to: n00b questions - verbosity of config????

I just started messing with puppet, and i love it! I have used cfengine in the past, and were in process of planing to replace cfengine now. One thing thats stumped me this weekend and i know i read your working on virtal defines so i can''t do that, but how can i get arond this issue with the curretn setup. I think i am missing something fundamentally simple here. i have this

I''m trying to use environments and seem to be failing. Right now I have 4 defined environments: production, cat, development, beta They are defined as follows on my puppetmaster: cat /etc/puppet/puppet.conf [main] pluginsync = true vardir = /var/lib/puppet manifest = /etc/puppet/environments/production/site.pp modulepath = /etc/puppet/environments/production/modules [master] reports =

Hello, I am running puppet server version 0.25.4-2, and since Debian squeeze is the new stable release I would like to adapt some of my modules. I have a syslog-ng module, I would like to specify another template for my squeeze server. I changed my init.pp as follow : if ($operatingsystemrelease <= 5.0.8) { $syslog_template = "syslog/syslog-ng.conf.erb" } else {

Howdy: I need some help please to get hiera configuration data derived from YAML, thru puppet. I have studied Internet search results and puppet documentation on create_resources and custom defines but need a little help along. I can print out the YAML from variables, arrays, and, finally, hashes too from a puppet manifest. One thing that is stumping me is how to access from the custom define

Hi, I''m trying to make all my servers send their logs to a central server. Which seems quite simple, at first. My problem is that my servers are on different versions of different operating systems. And each of them has a different syslog default provider (syslog, rsyslog, syslog-ng...). Which of course might have been replaced by an admin who prefered another... Even funnier, SLES10

Yesterday, I switched our node structure from using node basenode, node nodetype inherits basenode, to using node classes per the changes discussed recently on this list and as defined in the wiki:GlossaryOfTerms. In the manifest, we have a syslog module which sets up all the components of syslog-ng we''re using. The ''syslog'' class is used by default on clients and then

So, I''ve been doing something like this for applications that have a client and server component... node base_node { include syslog_ng::client }} node app_node inherits base_node { } node syslog_server inherits base_node { include syslog_ng::server } ... because I want the client portion, syslog-ng in this case to be installed on everything. However, the server node also has a

Hey All, I can see in the type reference under service it has restart, stop, start etc. But is there a way to issue a /etc/init.d/daemon reload ? but still have the restart available if needed Cheers Brendan Brendan Beveridge Managed Services Consultant Direct | 02 8235 9593 Mobile | 0434 077 934 Email | Brendan.Beveridge@brennanit.com.au "Brennan IT lands major IT&T

Most of my machines are pretty cookie-cutter, so I have one class and config file setup for different services. For example, pretty much have one hosts.allow that goes out everywhere. However, there are always exceptions. So I have 3 hosts that have similar configs but have more things open, so what''s the ''best practice'' way to centralize those? Do I really need to

Hi, I am using puppet (version 0.25.5-1.e15 for redhat) for password management for non-system users. This morning, users on some of my puppet clients had their encrypted password strings in /etc/shadow replaced with the following string: YAML::syck::BadAlias That has effectively broken the users'' ability to login to those servers. Puppet will not overwrite that string with the

Ok, the file definition was missing. Now i''ve put that: ## services/ssh.pp class ssh { file { sshd_config: name => "/etc/ssh/sshd_config" } service { ssh: name => $operatingsystem ? { Debian => ssh, default => sshd }, ensure =>

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Greetings list-members! I''m a puppet newb and I''m trying to write a recipe that replaces the standard Redhat sysklogd with syslog-ng. I do this to separate shorewall-generated iptables log messages from / var/log/messages into a separate log. I have something that works now but it spews warnings every time puppetd runs on the client. The outline of what I wanted was to

There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?

Hi, I''m exploring Puppet and have hit a rather weird problem. The puppetmaster server is running CentOS4, fully updated, with puppet installed from the dlutter RPM repo, version 0.20.0-1.el4. I tried adding the remotefile function definition from http://reductivelabs.com/projects/puppet/documentation/installation.html in /etc/puppet/manifests/utils/remotefile.pp but when I start

Hi all I''m on my first attempt to set up puppet and so far all is well but for one issue that I just don''t understand. I''ve set up a class for ntp configuration. This includes a subscribe line which for some reason won''t work when I try to subscribe to the package ntp! Here''s the class entry: class ntp_service { $ntp_servers = $subnet ? {

"Service and class definitions are scoped just as variable assignments are." But what about types? Here''s an example: class solserver inherits server { remotefile { "/etc/shadow": mode => 400, group => staff, source => "solall/etc/shadow.server" } Is it possible to just override the "/etc/shadow" definition for

Hello, As I''ve been building up my puppet infrastructure, I''ve started using puppet certs for all of my services that require ssl. Usually this is in the form of links: file { "/opt/syslog-ng/etc/ca.d/b2457b50.0": require => Package["syslog-ng"], ensure => link, target =>

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hello List, We are using puppet to manage a growing number of Debian Etch based servers (currently 70). Since upgrading to 0.22.4 we encountered a problem when services do not restarted on puppets request. For example the Nagios remote plugin executor daemon (nrpe). It''s running daemonized and its confiugration is located in /etc/nagios/nrpe.cfg. This file is managed through puppet