On Mar 21, 12:20 pm, hai wu <haiwu...@gmail.com> wrote: > I am going to use parameterized class together with extlookup, where > extlookup is used to provide different parameter value for different node > based on extlookup_precedence, the parameterized class needs to be declared > once in parent node, any issues you could forsee with this plan?
I think the problems are few for which parameterized classes are the *best* solution. Nevertheless the combination of parameterized classes with extlookup() may be the *most expedient* solution available at the moment. It will very likely solve your problem. There is some risk that you will run into trouble later as you continue to add nodes or manage more aspects of your configurations. In particular, if the number of distinct parameters you have to handle increases as you scale up, then you may reach a point when the parameters become a management problem of their own. There are other possible problems associated with parameterized classes, generally revolving around the fact that you can only include them once. Whether you are likely to run into any of them depends on how and how much you use such classes. Good Luck, 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-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.
