introduce tacker conductor

Bug #1697341 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Undecided
Unassigned

Bug Description

https://review.openstack.org/472149
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/tacker" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit e58b01a545eb232fc1094fe1ace0b52cfda6cdcb
Author: jing.liuqing <jing.liuqing@99cloud.net>
Date: Thu Jun 8 16:20:19 2017 +0800

    introduce tacker conductor

    This patch enables the message rpc framework which tacker conductor
    will use. After started via tacker_conductor script, it will listen
    on tacker_conductor, tacker_conductor.<host> and one fanout queues.

    These three queues are intialized in oslo service module. And topic
    queue tacker_conductor will be used by mistral actions.

    How to test it:
      document will be written after the whole vim monitor is ready.
    To test this patch, after 'python setup.py develop', run
    'tacker-conductor --config-file /etc/tacker/tacker.conf', and then
    use 'rabbitmqctl list_queues' which will list three queues starting
    with 'tacker_conductor'.

    DocImpact
    Implements: blueprint refactor-vim-monitor

    Change-Id: Ide80674099d384aed1a98b22928e9fc6bcfa3ff9

Tags: doc tacker
Yasufumi Ogawa (yasufum)
Changed in tacker:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.