refactor vim monitor
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:
-
pike-3
- Started by
- yong sheng gong
- Completed by
- yong sheng gong
Related branches
Related bugs
Sprints
Whiteboard
spec is reviewed at https:/
Gerrit topic: https:/
Addressed by: https:/
introduce tacker conductor
Addressed by: https:/
vim monitor using rpc
Addressed by: https:/
Implement vim status update in conductor
Addressed by: https:/
Add release notes for tacker conductor and mistral vim monitoring
Addressed by: https:/
Add devref for tacker conductor and vim monitoring
Addressed by: https:/
Run conductor before tacker server
Addressed by: https:/
Disable debug log of ping command in vim ping action
