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

Can we eliminate resource-based capacity tracking? #237

Closed
ebauman opened this issue Nov 4, 2022 · 2 comments · Fixed by hobbyfarm/gargantua#130
Closed

Can we eliminate resource-based capacity tracking? #237

ebauman opened this issue Nov 4, 2022 · 2 comments · Fixed by hobbyfarm/gargantua#130

Comments

@ebauman
Copy link
Member

ebauman commented Nov 4, 2022

Currently HobbyFarm is capable of tracking utilization in an environment based not only on the count of virtual machines deployed, but also theoretically the amount of CPU, memory and disk storage being taken up by the VMs.

In practice, this has almost never been done. Most users are in cloud providers and are concerned with node counts not resource consumption. Further, the abstract nature of the vm template (where the resource amounts are specified) doesn't directly translate to what consumption would be in a particular environment. Additionally, this mechanism may not even work at ll (I did say it only theoretically works ;) )

I propose we remove the concept of tracking VMs by resource consumption and focus solely on the count of VMs in an environment. It is then left as an exercise to the user to determine what capacity their environment has for different types of virtual machines.

@jggoebel
Copy link
Member

jggoebel commented Nov 4, 2022

Supporting this too. Calculating based on capacity makes the provisioning even more complex.
Removing this should not be very hard but would require environment/v2

We could in the same step fix #234

@jggoebel
Copy link
Member

jggoebel commented Nov 4, 2022

also in the same step fix #236 so we do not need to release two versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants