Re: [Puppet Users] hiera and dynamic variables

2012-07-23 Thread Felix Frank
On 07/23/2012 11:59 AM, asq wrote: > i don't want to define nagiosip - it should be inherited from fact > (current set IP address on given node). ie. > project A: $nagiosip = $ipaddress_bond0_1234 > project B: $nagiosip = $ipaddress_bond0_1235 > project C: $nagiosip = $ipaddress_eth2 > project D: $

Re: [Puppet Users] hiera and dynamic variables

2012-07-23 Thread asq
W dniu poniedziałek, 23 lipca 2012 09:21:09 UTC+2 użytkownik Felix.Frank napisał: > > This end could be trivially met by putting this class declaration in a > scope that is present for all your nodes. Perhaps a "default" class or > similar. > > The class parameter should be assigned directly fr

Re: [Puppet Users] hiera and dynamic variables

2012-07-23 Thread Felix Frank
On 07/20/2012 03:55 PM, asq wrote: > > class { "nagios::host": ip => $ipaddress_bond0_1234 } > > but... we'll need to include this on every single node (now we use node > inheritance and just set $nagiosip on top node level for group of hosts > that share the same vlan). This end could be trivia

[Puppet Users] hiera and dynamic variables

2012-07-20 Thread asq
hi, we're currently evaluating hiera to get rid of hordes of global variables and prepare our manifests for next iteration of puppet. now, we have some variables, used by classes, which set properties based on facts, ie. we set approperiate interface address which should be used on monitoring