openstack/tacker
Code Issues Proposed changes
840d754822
tacker/doc/source/contributor/tacker_conductor.rst
dharmendra 4e06cc4d1e Rearrange existing documentation to fit the new standard layout 
For more detail, see the doc migration spec.
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html

Change-Id: I85c8999eb12065662c02879beb7dd31d6178fe7e
2017-07-08 17:08:25 +00:00

1.8 KiB
Raw Blame History

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.