[GH-ISSUE #110] Multi-Node usage for Convoy Extension on Paymenter #76

Closed
opened 2026-02-26 17:31:16 +03:00 by kerem · 4 comments
Owner

Originally created by @julianfegert on GitHub (Aug 10, 2024).
Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/110

Is there an existing feature request for this?

  • I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

When you create a product in Paymenter, you can only select one host in the Convoy extension for paymenter. If this host is fully booked, an error appears: exceeds the nodes limit.

The Convoy extension for paymenter should use the next free host if several hosts are stored in Convoy.

Describe the solution you'd like.

For example, 2 hosts are stored in Convoy, e.g. pve06 and pve08. The convoy extension for paymenter is set to pve06. pve06 is fully utilized, then the extension should not issue an error but create the vm on pve08. an error message should only be issued if there is no free capacity on any existing node.

Additional context to this request.

No response

Originally created by @julianfegert on GitHub (Aug 10, 2024). Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/110 ### Is there an existing feature request for this? - [X] I have searched the existing issues before opening this feature request. ### Describe the feature you would like to see. When you create a product in Paymenter, you can only select one host in the Convoy extension for paymenter. If this host is fully booked, an error appears: exceeds the nodes limit. The Convoy extension for paymenter should use the next free host if several hosts are stored in Convoy. ### Describe the solution you'd like. For example, 2 hosts are stored in Convoy, e.g. pve06 and pve08. The convoy extension for paymenter is set to pve06. pve06 is fully utilized, then the extension should not issue an error but create the vm on pve08. an error message should only be issued if there is no free capacity on any existing node. ### Additional context to this request. _No response_
kerem 2026-02-26 17:31:16 +03:00
Author
Owner

@TeYroXOfficial commented on GitHub (Aug 10, 2024):

You should open an issue in Convoy extension for Paymenter repo, instead of here.
Eric didn't wrote extension for it.

<!-- gh-comment-id:2282301686 --> @TeYroXOfficial commented on GitHub (Aug 10, 2024): You should open an issue in Convoy extension for Paymenter repo, instead of here. Eric didn't wrote extension for it.
Author
Owner

@julianfegert commented on GitHub (Aug 10, 2024):

I already have. But I thought it might be necessary to make adjustments to convoy as well.
or can such a feature conpletely realized via adaptations to the extension without edits on convoy?

<!-- gh-comment-id:2282303101 --> @julianfegert commented on GitHub (Aug 10, 2024): I already have. But I thought it might be necessary to make adjustments to convoy as well. or can such a feature conpletely realized via adaptations to the extension without edits on convoy?
Author
Owner

@Adekabang commented on GitHub (Aug 11, 2024):

For now you can copy the extension and rename it. So, you have 2 or more extension, and choose the node. Then create a new product. This is the temporary solution. and also don't forget to set the stock.

<!-- gh-comment-id:2282346315 --> @Adekabang commented on GitHub (Aug 11, 2024): For now you can copy the extension and rename it. So, you have 2 or more extension, and choose the node. Then create a new product. This is the temporary solution. and also don't forget to set the stock.
Author
Owner

@ericwang401 commented on GitHub (Aug 11, 2024):

Modifying Convoy to support Paymenter's inability to load balance between many nodes would break other extensions that have implemented this ability.

<!-- gh-comment-id:2282598779 --> @ericwang401 commented on GitHub (Aug 11, 2024): Modifying Convoy to support Paymenter's inability to load balance between many nodes would break other extensions that have implemented this ability.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/panel#76
No description provided.