Robert <robertsch...@gmail.com> writes:
> On May 6, 9:56 am, Peter Meier <peter.me...@immerda.ch> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> > I suspect we will turn 'node default' into 'class default', then include
>> > that rather than inheriting that, since that does fix the scope issue.
>> this is imho the way to go if you don't want to switch over to an external
>> node tool.
>> For each node I set some variables and then include exactly one class, which
>> might a class similar to your default or a subclass of that one. And then
>> we do all the overriding and setting default variables (if not set in the
>> node) stuff within these (sub-)classes.
>> This works pretty well and doesn't give you overloaded node statements.
>
> That is one possible solution to the problem Daniel describes. I'm having
> similar problems finding a good (and good-looking) solution to group nodes
> and use node inheritance.
[...]
> One solution is indeed to, as you say, put everything a single class or
> subclass, to not use inheritance. I don't like that solution very much,
> because that removes the complete configuration for any node from sight, while
> I've gone through great lengths to make the node-configuration as explicit as
> possible: node default for example, lists each class included class
> seperately.
I elected to use a define, not a class, because that way I can have mandatory
configuration as well as optional configuration, for each node, FWIW.
> In a working environment with 20+ people managing 400+ hosts, you have to be
> as explicit as possible. But without repeating.
*nod* My conclusion, on thinking about the same issue, was that it really
didn't change much when I moved from 'inherits blah' to 'blah { $fqdn: ... }'
in that I was still writing that basic stuff in one place — it just had a
different syntax from inheritance.
(You could even write it exactly where 'node default' was defined if you
want. :)
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
