live migration progress report
Some busy enterprise workloads hosted on large sized VM, such as SAP ERP
Systems, VMs running memory write intensive workloads, this may lead migration
not converge.
Now nova can not report more details of migration statistics, such as how many
ram are transferred, what's the ram dirty-sync-count, or the size of
"xbzrle-cache". Sometimes the operator may not know these details, and decide
how to take the next action on the migration.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Medium
- Drafter:
- lvmxh
- Direction:
- Approved
- Assignee:
- lvmxh
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-3
- Started by
- John Garbutt
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
report live migration progress
This current spec seems to include an API design that would get my -2 vote, so we need to resolve this issue by revising the spec. --johnthetubaguy 20151207
Gerrit topic: https:/
Addressed by: https:/
Corrects the API propose for live-migration progress
Addressed by: https:/
Add API /servers/
Addressed by: https:/
Add migration progress detail in DB
Addressed by: https:/
write live migration progress detail to DB in migration monitor
Addressed by: https:/
add ref link for /os-migrations