KVM: show live migration progress on the instance page and add transfer details to VM.MIGRATE events

未关闭
#14,531 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java

调研方向

Start by tracing the KVM agent’s libvirt migration job information, the management server’s migrate work job and updateAsyncJobStatus(), the VM response API, and the instance page and VM.MIGRATE event handling. The issue describes the expected progress fields, display, and event summaries, but names no files or tests; first map the migration flow across these components. Done means progress is polled and exposed during migration, shown in the UI, and summarized in completion and error events.

由索引模型根据 Issue 内容生成。

描述

component:api component:kvm component:UI
The required feature described as a wish
SUMMARY

During a live migration the UI only shows the instance as Migrating, so admins have to run virsh domjobinfo on the source host to see how far along it is or whether it has stalled.

This proposes showing migration progress for KVM first. The API field is hypervisor-neutral, so VMware, XenServer and others can add it later from their own task progress.

PROPOSAL
  • KVM agent: new command that returns the libvirt domain job info (disk and memory processed / remaining / total).
  • Management server: poll the source host every few seconds while the migrate work job runs, and store the result on the job with updateAsyncJobStatus().
  • API: admin-only migrationprogress on the VM response while the state is Migrating, read from the pending vm_work_job. Percent is always set and the byte/rate figures are optional, since other hypervisors only report a percentage.
  • UI: progress bar under Status on the instance page with percentage, "x of y complete", estimated time remaining and transfer rate in MB/s. When volumes migrate with the VM, disks and memory get separate bars; libvirt already splits them in the same job info (file* / mem*). Mock-up attached.
  • Events: append a summary to the VM.MIGRATE Completed event description (data transferred, duration, average rate), and on Error - a record of how far it got and a short reason (e.g. timed out and not converging, destination unreachable). Sizes, rates and reason category only. I wouldn't include host or storage names, since the event can be visible to the VM owner.

Happy to work on a PR if this approach is acceptable.

Mock-up of the UI change below:
Progress in an instance:
Image

Event - Successful:
Image

Event - Failed:
Image

主要语言
Java
星标
3.1k
派生
1.4k
平均合并
7 天 16 小时
30 天内合并 PR
15

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/cloudstack 的其他 Issue

查看 apache/cloudstack 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。