vim monitor using rpc

Bug #1699399 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Won't Fix
Undecided
Unassigned

Bug Description

https://review.openstack.org/475207
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 60187643b586568e9c6f51c45d8b91ab697ed3fc
Author: jing.liuqing <jing.liuqing@99cloud.net>
Date: Mon Jun 19 11:19:00 2017 +0800

    vim monitor using rpc

    This patch sets up the rpc queue named KILL_ACTION.<vim_id>
    in mistral action class. When vim is deleted, the tacker server
    will send(cast) kill message to the mistral task, which will exit.

    To test it:
    1. python setup.py develop
    2. mistral-db-manage --config-file /etc/mistral/mistral.conf
    populate
    3. restart mistral related service and tacker service
    4. tacker vim-register to register a vim
    5. mistral workflow-list to check if the monitor workflow is
    started
    6. tacker vim-delete to check if the workflow and task is deleted

    DocImpact
    Implements: blueprint refactor-vim-monitor

    Change-Id: I078917af65e57305c06b4605835c9d0d3dc1cf68

Tags: doc tacker
Yasufumi Ogawa (yasufum)
Changed in tacker:
status: New → Won't Fix
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.