Maybe it''s just me stumbling with object inheritance, but
here''s a
simple example of some of the issues I can''t quite get my head around
with puppet.
Lets say nodes might be either physical or virtual, and each requires
slightly different stuff to be installed. Lets also say that we have
application nodes that might either be installed in a physical or
virtual environment. How do I model the inheritance for this? If I
create two base nodes, physicalNode and virtualNode, and the
application servers also have an intermediary inheritance from a
javaServer node, then suddenly I have:
physicalServer
|--- physicalJavaServer
|--- physicalAppServer
virtualServer
|--- virtualJavaServer
|--- virtualAppServer
This seems silly to me. The further up the chain I create specific
nodes, the more unique child classes I have. All this is because I
want to do things like include ipmi tools on physical nodes, and not
virtual nodes, and maybe vmware tools on virtual nodes and not
physical nodes.
Or... is the node hierarchy the wrong place to do it? Should the
intelligence be pushed some how back into the module?
Doug.
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.