GitHub user vonlo123 closed a discussion: Changing compute offering / scaling VM and root disk
We are having problems implementing our idea regarding the compute offerings. We want to use offerings with a fixed amount of CPU, RAM and local storage so that the KVM host is utilized in the best possible way. E.g. an offering 1: 1 CPU, 2 GB RAM, 20 GB local storage Offering 2: 2 CPU 4 GB RAM, 40 GB local storage etc. We want to avoid a situation where a few VMs with little CPU/RAM consume the entire storage of the host so that the storage is fully booked but the CPU and RAM are not utilized. That would be a waste of resources. Of course, we also want to offer the customer the option of changing the _compute offering_ if they need more resources for their VM. According to the [documentation](https://docs.cloudstack.apache.org/en/latest/adminguide/storage.html#root-volume-size-defined-via-service-offering) it should be possible. But after some testing, we have now come to the conclusion that changing an offering/scaling a VM is only possible if _Disk offering strictness_ is set to _false_ in the initial (and target) compute offering of the VM. But this would allow the user to freely adjust the size of the disk. Is there a solution to this? Did we miss anything? How do you ensure that all resources of a nodes are fully utilized? Version 4.18.1.0 with KVM GitHub link: https://github.com/apache/cloudstack/discussions/8578 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
