On 08/05/2011 09:33 AM, Nigel Kersten wrote:
We have a bunch of problems people regularly run into with node
inheritance, and it's something we'd like to find a better solution for.
Let me guess:
- nodes are not classes
- node scope is not global scope
Is there something else that trips people up?
Is anyone using node inheritance and happy with how it works? If so,
can you describe your setup briefly?
I just include classes in my nodes. I save the fancy stuff for classes.
I don't expect anything from nodes, so I am never disappointed.
Here's a suggestion: Get rid of nodes as something separate from classes.
Consider 'node' to be a keyword meaning 'here is a class, automatically
include it in the manifest for these hosts'. These automatically assigned
classes can inherit from other classes. Make 'node' be the name of the
scope for that automatically assigned class.
If there is no node statement, including no default node, then magically
create an empty class so that the node:: scope can be tested.
--
vagn
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@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.
