On Dec 13, 4:12 pm, Douglas Garstang <doug.garst...@gmail.com> wrote: > No, not really because for starters there are anywhere from 1 to 10 > instances of jboss running, but not always 10. It depends on the node. > If it was always 10, I could say something like > before=>Service["jboss-inst0"], before=>Service["jboss-inst1"] etc. > > PLUS the jboss service is controlled inside a definition, not a class. > I don't know if I can use before => in that case.
Well, "require" and "before" are the main tools you have to work with. One of these or both together must do the job for you. If you have n node-specific things dependant on m other, uncorrellated things, such that it's hard to know on either side what all the dependencies are, then you may need to perform a refactoring to get it to work. For example, figuring out how to group either the third- party stuff or the multiple Service resources or both into classes might be helpful. That's not inherently incompatible with having the resource declarations done via defined types. You may also find that you can use the scoping rules for resource defaults to set default values for Service/require or for ThirdPartyThing/before that only affect the JBoss / third party resources you're trying to manage. -- 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.
