-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node #16
Comments
Also need to recommend a function that checks which node has which VM when dealing with cluster setups. HA will move a VM to the next known available node that's configured in the HA rules if that VM is part of a HA group. Perhaps this might be useful as a cron job and added to WHMCS Automation ? |
Similar to Backup Request #39 this is something that ties into the functionality we're looking to slowly add: https://www.modulesgarden.com/products/whmcs/proxmox-ve-vps#changelog |
Does it appear as 2x the guest? Just need to get an idea of what the WHMCS Module will see when it interrogates PVE. |
Apparently i tried to reply via email and it didn't show up here soo... As i recall, it only appears once. However what was screwy was when HA Moved it, it'd move it in the WHMCS module, but not always t the correct node. Example: 3 Node set up with pve1, pve2, Pve3. Creation would drop the VM in to a RANDOM node (at least it looked that way to me), and HA would move it to another node. WHMCS couldn't tell which node, so it'd just move it around. If i tried to move it in whmcs, it'd move it... However the behavior would be just a game of hot potato as to which node it actually moved it to. What honestly would solve this is a sanity check to see where the vm actually is. The bigger issue is.. you'd have to add every single node frmo the cluster into the config and that'll be a pain if you have a large cluster lol |
Need to introduce mapping between PVE Nodes and WHMCS Servers, then provision to that node/server.
The text was updated successfully, but these errors were encountered: