Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#14,230 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java, kubernetes, python
Área
backend, cloud, distributed-systems, infrastructure

Línea de trabajo

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.

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

Descripción

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.
Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.4k
Merge medio
6 d 20 h
PR fusionados (30 d)
27

Guía de contribución

Abrir la guía de contribución

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.