It is reasonable flow that you inherit the configuration from the template, but you can change most of the settings during the creation of the VM, I just don't understand why not to be able to change the disk size and name.
Why disk size? You can say the same thing with any other settings, so just make a template for any different setting you need for different VMs based on that same OS.
This flow of changing the disk size is supported in any other platforms take a few, OpenStack, VMWare, Xen and any other Cloud providers.
I don't see a reason why to do this in two API calls, one for VM creation and then another one for just expanding the disk size.
I do understand if you create a VM based on a thin template which is just a link that there's no other way.
Another "issue" is that it creates the new of the new disk for the VM based on the template name instead of "vmname_Disk1" etc...
I have a customer with many different disk sizes, varying from 50GB up to 200GB, If I go and create a template for an OS based on that, I will probably have 10 templates, it's not scalable if you need to just modify something in the template as well.
So the only option right now is to use OpenStack Glance for saving images or create a new feature in Foreman/Satelite for that.
On 16/06/2020, 20:53, "Nir Soffer" <nsoffer@redhat.com> wrote:
On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum <erezz@nanosek.com> wrote:
>
> Hey,
>
> I have created a template that the disk is a thick (raw) with a size of 15GB.
>
> I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template.
>
> So far the only solution I managed to find is to adjust the size after creating the VM.
This looks like reasonable flow. You create the vm from a template, so
you inherit the
disk size from the template. Then you modify the disk to the required size.
> For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk.
Why is this problematic?
> I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance?
If you always need to resize the template, why not create another
templated with the right
size based on this template?
Nir
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/46IFRJCTZNZZHRYVDIYGVJFBNSOJNPVX/