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

Abierto
  • ¿Algo no está bien?
#14,531 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
api, backend, devops, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.4k
Merge medio
7 d 16 h
PR fusionados (30 d)
15

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/cloudstack

Todos los issues de apache/cloudstack

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.