Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
#14,230 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java, kubernetes, python
Bereich
backend, cloud, distributed-systems, infrastructure

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Java
Sterne
3.1k
Forks
1.4k
Ø Merge
6 T. 20 Std.
Gemergte PRs (30 T.)
27

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/cloudstack

Alle Issues in apache/cloudstack

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.