mirror of
https://github.com/pelican-dev/panel.git
synced 2026-07-16 04:03:50 +03:00
Add Node CPU resource allocations #50
Reference in New Issue
Block a user
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 @iamkubi on GitHub (May 15, 2024).
Originally assigned to: @notAreYouScared on GitHub.
Nodes should be able to define CPU resource allocations that are respected by the deployment service. This would work the same as disk/memory where you can set a maximum amount of CPU that should be assignable to the node. After this automated deployments using the deployment service would consider the node to be full if adding the new server would drive its allocated CPU time above the node's defined limit.
As best I can tell no work is required on the wings side for this. Node models would need to be updated, total assigned CPU allocations per node would need to be calculated, and that allocated usage would be used by the deployment service to determine if a node can deploy a server.
@Mutex21 commented on GitHub (May 16, 2024):
Shouldn't this also be included in the simple calculation of the load of that node? The load is very important as well.
@iamkubi commented on GitHub (May 16, 2024):
I honestly have no idea what you mean. We don't have a "simple calculation of the load of that node".