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

Aberta
  • Algo errado?
#14,434 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
1/5
Tempo estimado
Menos de uma hora
Facilidade para iniciantes
1/100
Tipo de issue
Documentação
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
java
Domínio
content

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
Java
Estrelas
3.1k
Forks
1.4k
Merge médio
7d 16h
PRs com merge (30d)
15

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/cloudstack

Todas as issues de apache/cloudstack

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.