Re: [Puppet Users] Over riding global settings/class/variables at node level

2012-10-30 Thread chandan kumar
Thanks for the response. I am able to fix the problem class syslog_ng::service inherits standard-services { Service['rsyslog'] { enable => false, ensure => stopped, } service { 'syslog-ng': ensure => running, enable => true, require => Class['syslog_ng::install'] }

Re: [Puppet Users] Over riding global settings/class/variables at node level

2012-10-27 Thread Ramin K
On 10/26/2012 7:21 PM, chandan kumar wrote: Hello, I am new to puppet programming. I have encountered a problem where the a global setting, application to all servers, nodes across the board to enable a particular service such as rsyslog. And I want to have a server that should not run rsyslog r

Re: [Puppet Users] Over riding global settings/class/variables at node level

2012-10-27 Thread Aaron Stone
Rules are not run in order, so there's nothing to indicate to Puppet which of those contradictory rules should win. Puppet also enforces a uniqueness on the pair (type, name) -- ('service', 'rsyslog') is unique and you cannot have another one. What you'll need to do is make sure that only one of t

[Puppet Users] Over riding global settings/class/variables at node level

2012-10-27 Thread chandan kumar
Hello, I am new to puppet programming. I have encountered a problem where the a global setting, application to all servers, nodes across the board to enable a particular service such as rsyslog. And I want to have a server that should not run rsyslog rather it should run syslog-ng. So basical