Skip to content
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

Open
lsthompson opened this issue Jun 12, 2023 · 4 comments
Open
Labels
feat-major Major feature request z-module
Milestone

Comments

@lsthompson
Copy link
Member

lsthompson commented Jun 12, 2023

Need to introduce mapping between PVE Nodes and WHMCS Servers, then provision to that node/server.

@lsthompson lsthompson added the feat-major Major feature request label Jun 16, 2023
@lsthompson lsthompson added this to the v1.3.0 milestone Sep 13, 2023
@lsthompson lsthompson changed the title Client Area: Data request made to 1st node, regardless of whether VM/CT is on that node Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node (should align with SID Server) Sep 13, 2023
@jbrouhard98
Copy link

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 ?

@lsthompson
Copy link
Member Author

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

@lsthompson lsthompson changed the title Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node (should align with SID Server) Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node (should align & update) Sep 14, 2023
@lsthompson lsthompson modified the milestones: v1.3.x, v1.2.3 Sep 14, 2023
@lsthompson
Copy link
Member Author

@jbrouhard98

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.

Does it appear as 2x the guest? Just need to get an idea of what the WHMCS Module will see when it interrogates PVE.

@jbrouhard98
Copy link

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

@lsthompson lsthompson changed the title Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node (should align & update) Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node (should update) Nov 23, 2023
@lsthompson lsthompson modified the milestones: v1.2.3, v1.3.x, v1.2.4 Dec 5, 2023
@lsthompson lsthompson changed the title Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node (should update) Proxmox API Calls: Made to 1st node, not WHMCS-set/PVE-paired node Dec 6, 2023
@lsthompson lsthompson modified the milestones: v1.2.4, v1.3.x May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat-major Major feature request z-module
Projects
None yet
Development

No branches or pull requests

2 participants