mirror of
https://github.com/Telmate/proxmox-api-go.git
synced 2026-04-25 23:45:55 +03:00
[GH-ISSUE #125] Feature request: HA support for LXC containers #24
Labels
No labels
good first issue
issue/confirmed
issue/critical
proposal/accepted
pull-request
type/bug
type/enhancement
type/feature
type/question
type/refactoring
type/testing
type/testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxmox-api-go#24
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yesrod on GitHub (Jun 26, 2021).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/125
First off, I apologize for the state of this issue, but my Go knowledge is limited. If anything I say is completely incorrect, please let me know.
Looking at the existing state of this API, it appears that the LXC container part doesn't handle HA configuration, but the QEMU VM part does. Specifically, the LXC container part is missing the
hastateparameter.If I'm reading the code correctly, the UpdateVMHA() function at https://github.com/Telmate/proxmox-api-go/blob/master/proxmox/client.go#L1172 should support setting up the HA resource for a LXC container already. If that is correct, then the LXC container part just needs a few things to also support HA, and config_qemu.go could be used as a reference to add that support.
Unfortunately, I don't understand the code well enough yet to make an attempt on my own to add this support. I would greatly appreciate if someone more familiar with the code could add this support.
@yesrod commented on GitHub (Jul 8, 2021):
I've filed pull request #126 to resolve this issue.
I also have the necessary changes for https://github.com/Telmate/terraform-provider-proxmox but I need this PR merged first due to the way that the Terraform provider finds this module.