vim monitor using rpc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
https:/
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 60187643b586568
Author: jing.liuqing <jing.liuqing@
Date: Mon Jun 19 11:19:00 2017 +0800
vim monitor using rpc
This patch sets up the rpc queue named KILL_ACTION.
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/
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-
Change-Id: I078917af65e573
Changed in tacker: | |
status: | New → Won't Fix |