On Fri, Sep 24, 2010 at 5:19 PM, Alan Conway <[email protected]> wrote: > Lots of newcomers stumble over this. I occasionally forget something myself > when setting up on a new host. Shout if you have any ideas on how the doc > could be improved so that you would have figured this out more quickly. >
This doesn't really seem like a qpid issue so much as an issue where if you don't understand what the relationship is between corosync, multicast traffic and qpid then you will more than likely miss this kind of configuration issue. Perhaps calling it out explicitly on the wiki page with some links to the related projects would be a good addition for those of us new to the whole suite of software. I was struggling to understand how everything hooked together never having used corosync or qpid. In a perfect world, there would be a way to test corosync and multicast traffic besides running something as complex as qpid. A tool that did some kind of multicast ping/heads up just to show traffic was routed correctly might be a handy tool. Then the install process would essentially consist of ensuring things were correctly configured each step of the way rather than waiting until you touched a bunch of files and installed a bunch of packages to see if it all works perfectly together. I guess what I'm saying is that solving this problem at the qpid level is fantastic for qpid, but there are lots of other things that need corosync/heartbeat configured correctly. Tools to better support and troubleshoot the underlying functionality of corosync would make setting up a vip and stonith much easier (for instance). To be fair, such tools may exist and I am simply ignorant of them. So if you know of resources, I'm happy to hear about them. Either way, thanks again for pointing me in the right direction. I have a bunch more to read up on. These tools open up a lot of possibilities for me. -- J. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
