refactor vim monitor

Registered by yong sheng gong on 2017-04-25

currently, a thread will be started by tacker server once a vim is registered, which is not scalable.
1. if we have a lot of vims, the tacker server will have to run a lot of threads to monitor them, which
will impact the API function of tacker server
2. if the tacker server restarts, the monitor thread will not start
3. cannot run more than one tacker server

Blueprint information

Status:
Complete
Approver:
yong sheng gong
Priority:
Essential
Drafter:
yong sheng gong
Direction:
Approved
Assignee:
yong sheng gong
Definition:
Approved
Series goal:
Accepted for pike
Implementation:
Implemented
Milestone target:
milestone icon pike-3
Started by
yong sheng gong on 2017-06-08
Completed by
yong sheng gong on 2017-07-05

Related branches

Sprints

Whiteboard

spec is reviewed at https://review.openstack.org/#/c/459520/

Gerrit topic: https://review.openstack.org/#q,topic:bp/refactor-vim-monitor,n,z

Addressed by: https://review.openstack.org/472149
    introduce tacker conductor

Addressed by: https://review.openstack.org/475207
    vim monitor using rpc

Addressed by: https://review.openstack.org/475594
    Implement vim status update in conductor

Addressed by: https://review.openstack.org/476100
    Add release notes for tacker conductor and mistral vim monitoring

Addressed by: https://review.openstack.org/476132
    Add devref for tacker conductor and vim monitoring

Addressed by: https://review.openstack.org/476730
    Run conductor before tacker server

Addressed by: https://review.openstack.org/476735
    Disable debug log of ping command in vim ping action

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.