Added multiple target nodes instead of a single node. #766
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, I'm currently working to fix it in the right ways proxmox side https://lists.proxmox.com/pipermail/pve-devel/2023-May/057007.html I'm trying to push for proxmox8 you can follow it here: |
|
It's been a long time since the last update in the feed. Anything happened in the past? |
spettinichi
pushed a commit
to spettinichi/terraform-provider-proxmox
that referenced
this pull request
Jan 26, 2024
* added data_ha_group.go to fetch HA Groups * renamed variable in data ha group file * added the possibility to add a node with a set of possible nodes (high availability) * minor code fixes --------- Co-authored-by: Pascal Kutscha <pascal.kutscha@myloc.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Imagine you have a cluster in which you migrate using High Availability Server. this is exactly the case I had. I have created a HA Group in Proxmox within which servers are automatically migrated in case of a failure or similar.
With this code change it doesn't matter now. You can specify an array of possible nodes where the QEMU can be located.
I also implemented my own change to your golang implementation (Telmate/proxmox-api-go#262) to manage this with HA Groups.