Red Hat Bugzilla – Bug 1012148
Conductor should be able to start multiple workers
Last modified: 2014-06-18 03:00:30 EDT
+++ This bug was initially created as a clone of Bug #1012143 +++
Description of problem:
Any reasonable deployment needs more than one conductor process and grizzly did not support this natively. Right now, this is only workable if someone runs a conductor on several machines or starts multiple processes manually. We should have an /etc/sysconfig/nova-conductor config point to specify how many daemons to start so that it's easy to start multiple daemons on a single system.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy conductor on one machine
2. Deploy compute on many machines
3. Notice failures and poor performance
Everything funnels through a single conductor.
Multiple conductors should be started to spread out the load.
This should be pretty easy to do in the script, starting multiple workers, with log files and pid files like /var/log/nova/conductor-$i.log, etc.