Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Restarting a KVM VMs after its host fails when the management server is also unreachable

Aberta
#14,230 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, kubernetes, python
Domínio
backend, cloud, distributed-systems, infrastructure

Direção de pesquisa

The issue describes a distributed systems problem requiring a new cluster mechanism for VM HA. Start by reviewing the existing KVM agent code and the linked PR #13589 and issue #14206. Understand how CloudStack currently handles host failures and VM restarts via the management server. Research Corosync/Pacemaker and LINSTOR/drbd-reactor integration possibilities. The goal is to design a system where agents can autonomously restart VMs during a management server outage.

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

Descrição

component:kvm type:new-feature
The required feature described as a wish

Today if a KVM host fails and the management server and/or database is unreachable at the same moment (a remote site outage, a network partition, or the management server itself running as a guest on the failing host) CloudStack cannot restart the affected VMs. Every HA and DRS decision path runs inside the management server process and depends on the database.

I propose to add a small, storage-aware cluster mechanism that can restart a VM on a surviving host using its own quorum and fencing, and hands control back cleanly once the management server returns. This might require the Agents to actually keep shadow copy of each of the VMs configuration (of just enough per-VM data to rebuild the libvirt domain: disk identifiers, NIC MACs, CPU/memory, bridge/VLAN mapping). Possibly the agents can exchange information with each other and in case one Agent looses connectivity to management server act as a proxy towards the management server?

This might be an addition/similar or even fix to the https://github.com/apache/cloudstack/pull/13589 , https://github.com/apache/cloudstack/issues/14206 , or rely on some other mechanisms as surviving hosts must agree "host A (and possibly the management server) is gone" without a central arbiter and must not false-positive on an ordinary network hiccup,

Options I see as viable:

  • Generic - Corosync for membership, Pacemaker for orchestration, IPMI/BMC STONITH for fencing.
  • Storage specific - LINSTOR + drbd-reactor, CloudStack already ships a maintained LINSTOR primary storage plugin whose KVM-side driver talks straight to the LINSTOR controller, bypassing the management server for volume attach, and drbd quorum enforces split-brain protection, so it might be a nice addition.
Linguagem predominante
Java
Estrelas
3.1k
Forks
1.4k
Merge médio
6d 20h
PRs com merge (30d)
27

Guia de contribuição

Abrir o guia de contribuição

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.