Tacker conductor

Tacker conductor is a component which is used to communicate with other components via message RPC. In the conductor, the RPC server sides can access the tacker base on behalf of them.

To start

Tacker conductor can be started via python console entry script ‘tacker-conductor’:

tacker-conductor --config-file /etc/tacker/tacker.conf

we can easily start many tacker-conductor instances with different ‘host’ value in the configuration file:

test@ubuntu64:~/devstack$ grep 'host = secondinstance' /etc/tacker/tacker2.conf
host = secondinstance

and then start the second instance:

tacker-conductor --config-file /etc/tacker/tacker2.conf

Rabbitmq queues

Tacker conductor is listening on three queues:

test@ubuntu64:~/tacker$ sudo rabbitmqctl list_queues | grep CONDUCTOR
TACKER_CONDUCTOR    0
TACKER_CONDUCTOR.ubuntu64   0
TACKER_CONDUCTOR_fanout_0ea005c0b666488485a7b3689eb70168    0

But only TACKER_CONDUCTOR queue without host suffix is used.