You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: