On Tuesday, January 28, 2014 10:11:58 PM UTC+1, jcbollinger wrote: > > > > Not any good ways. In any case, that idea doesn't look like a good fit > for the module in question. A quick examination leads me to believe that > it will set up the cluster only once (on each node that has the > pacemaker::corrosync class). The resources exported by a given node are > not available for collection until after the node has checked in at least > once, however, so even if you could collect information that they exported, > most nodes would initially get have an incomplete list of cluster members. > And that would stick. To use that module effectively, it looks like you > need to be able to enumerate the cluster members in advance. > > > What would be the correct way of doing this then?
Krist -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/9da32cdf-7ab1-4e51-b1f3-e2e3bfdb18fc%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
