On Mon, Oct 22, 2012 at 01:54:11PM +0200, Gary Kotton wrote: > Can you please explain the problems that you had with qpid?
OpenStack components were periodically losing touch with each other. Requests to boot/delete an instance, for example, would never make it as far the compute hosts. They would get stuck scheduling. Initially we thought this was exclusively a problem with the network firewall infrastructure (there was a default 1 hour idle connection timeout), but reconfiguring our OpenStack environment to remove the firewalls from the picture did not resolve this problem. Since replacing qpid with rabbitmq, we have not had a single recurrence of this behavior. -- Lars Kellogg-Stedman <[email protected]> | Senior Technologist | http://ac.seas.harvard.edu/ Academic Computing | http://code.seas.harvard.edu/ Harvard School of Engineering | and Applied Sciences | _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
