On Dec 20, 11:00 am, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:
> On 12/20/2010 05:55 PM, rjl wrote:
> Well, I'm stumped. Maybe variable substition is just not meant to work
> for node declarations.
I could easily believe that. It doesn't make much sense to me to use
variable substitution in that context.
> I still don't see what you need it for. Your earlier post is a very good
> depiction of how to choose a node's role based on a fact: Do it by
> selecting the class(es) to include based on the fact value. Do not try
> and select a node declaration based on a fact instead.
Exactly. You hit it on the head earlier when you said "this node
definition will apply to each and every client." You can express that
in Puppet by just putting the code at top level, outside any node
definition.
If it were me, though, I'd do it slightly differently:
node default {
case $osp_type {
adm: { include adm }
...
}
}
That way you can easily sidestep the whole $osp_type selection
business if you need to do.
rjl didn't say specifically how he solved his problem, but I'm
guessing it was in one of those two ways.
John
--
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.
