[repo-status] [Weekly Status] CloudStack activity for 2026-10-11 to 2026-10-18

Abierto
  • ¿Algo no está bien?
#14,434 0 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
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
1/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java
Área
content

Línea de trabajo

This is an automated weekly status report, with no files or tests identified and no requested code or documentation change. Read the report and its linked pull requests to understand the summarized work; the issue gives no specific completion criteria for a contribution.

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

Descripción

report weekly-status

Weekly status: 2026-10-11 to 2026-10-18 🌟

CloudStack had a focused and productive week, with meaningful progress in VM migration capabilities and build visibility.

Highlights
  • VMware-to-KVM migration restored: PR #14256 restores cold VDDK import and warm CBT migration into Ceph/RBD and LINSTOR, plus adoption of existing RBD/LINSTOR volumes through importVm/importVolume. It also includes CBT cutover and cleanup handling, source-VM firmware/guest defaults, and LINSTOR validation improvements.
  • Migration quality improvements: The change addresses per-disk CBT checkpointing, final-cycle failure paths, imported-VM target-disk retention, template handling, and controller-metadata inspection. The PR reports 157 Trillian smoke tests passing with 0 errors.
  • Build observability: PR #14394 adds Develocity integration, updates the Maven extensions, and scopes the access-key secret to Maven workflows.
  • Release posture: No release was published during this reporting window. The latest listed regular release is 4.23.0.0, published September 2, 2026.
Progress and goals

The project is advancing two important goals: broadening migration paths for operators moving away from VMware, and improving CI/build feedback for maintainers. The migration work is especially valuable because it covers both cold and warm workflows and multiple storage backends.

Recommendations and next steps
  1. Prioritize end-to-end validation of warm CBT cutover, cancellation, cleanup, and import behavior across Ceph/RBD and LINSTOR, including upgrade-path database changes.
  2. Use the new Develocity data to identify slow or flaky Maven stages and turn the findings into targeted CI improvements.
  3. Keep release readiness visible: confirm documentation, API/UI coverage, upgrade notes, and operator guidance for the migration feature before the next release milestone.
  4. Continue security and maintenance review of the release branches while feature work lands on main.

Thanks to everyone contributing reviews, testing, and implementation work this week! 🚀

Generated by Weekly Repo Status · gpt56 155.2K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-status.md@main
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.