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

Define Ammount of RAM per node. (a cap) #302

Closed
Zendrex opened this issue Nov 28, 2014 · 1 comment
Closed

Define Ammount of RAM per node. (a cap) #302

Zendrex opened this issue Nov 28, 2014 · 1 comment

Comments

@Zendrex
Copy link

Zendrex commented Nov 28, 2014

For people who plan to use PufferPanel with WHMCS, or even just limit themselves to how many servers run on a single machine, my suggestion is to add a "cap" on how much of a given resource a server can use. In this case RAM and data storage.

For example. Say you add a new node to your panel, and it has say 32gb of ram, and a 250gb ssd. What this feature will do is allow you to state this resource information and limit you to that when you add the node to your panel. So in the case of WHMCS, when automated servers start rolling in. It will use 1 server till it caps at the 32gb of ram limit, then move to the next one or if a certain amount of resource isnt available on the current node, it will move to the next one (if possible) or just not allow it at all.

This could also be good to help limit overload of a server trying to share resources. Say I make a server and I dont remember how much of a given resource I have left. The panel will stop me for being able to say add 8gb of ram when I only have 6 left that I specified when adding the node. I say this, because I run two nodes now, and remembering the amount of each given resource becomes a tedious task and I assume it would for others too.

@DaneEveritt DaneEveritt added this to the 0.8.0 Beta milestone Nov 29, 2014
@DaneEveritt
Copy link
Contributor

I won't implement a hard cap on nodes, because some companies to run over the defined amount of RAM, either because they are trying to cram a bunch of servers on, you they actually know what they are doing and can maximize servers correctly.

I will add the ability to set the server specs though, for WHMCS and also so you can keep track of total usage. Thanks for the suggestion.

@DaneEveritt DaneEveritt modified the milestones: 0.8.0 Beta, 0.9.0 Beta, 0.8.1 Beta, 0.7.6 Beta Dec 7, 2014
DaneEveritt added a commit that referenced this issue Sep 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants