github-actions[bot] commented on issue #14230: URL: https://github.com/apache/cloudstack/issues/14230#issuecomment-5798922331
## ๐ฏ Triage report This is a feature request/design proposal for a decentralized HA/fencing mechanism that would allow surviving KVM hosts to restart VMs from a failed host even when the management server and/or database is unreachable (e.g., during a network partition or when the management server itself runs as a guest on the failed host). The author proposes options such as Corosync/Pacemaker/STONITH or a LINSTOR+drbd-reactor based approach, and references related PR #13589 and issue #14206. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:new-feature | Proposes new distributed HA/fencing capability not currently part of CloudStack's architecture. | | **Component** | component:kvm | Proposal is specifically about KVM hosts/agents and libvirt domain reconstruction. | | **Severity** | n/a | Feature request, not a bug. | | **Labels** | type:new-feature, component:kvm | See reasoning above. | | **Coding agent** | Not suitable | This is a large architectural/design proposal (distributed quorum, fencing, agent-to-agent communication) requiring maintainer discussion and design decisions before any implementation could begin. | ### ๐ Similar issues - https://github.com/apache/cloudstack/pull/13589 (related) โ referenced by the author as a possibly related or overlapping effort. - https://github.com/apache/cloudstack/issues/14206 (related) โ referenced by the author as a possibly related HA issue. - https://github.com/apache/cloudstack/issues/13376 (related) โ "Redfish: Host-HA fails to mark a powered-off KVM host as Down", adjacent HA/fencing reliability issue. <details><summary>๐ก Notes and suggestions</summary> - This proposal touches on core HA/fencing architecture and would benefit from discussion on the dev mailing list or a design document (per CloudStack's contribution process) before any code is written. - Maintainers should confirm whether this overlaps with existing/planned work in PR #13589 and issue #14206 to avoid duplicated design effort. - Key open questions for the author/maintainers: how would quorum/fencing decisions avoid split-brain with the existing HA subsystem that assumes a central management server; how would agent-to-agent proxying interact with existing security models (mutual auth between agents); what happens to VM state reconciliation once the management server reconnects. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/35867756133) ยท sonnet50 140.8K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 35867756133, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/35867756133 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
