Creating VMs from templates with their own disks
Hi All Im very stumped on how to create VMs from templates I've made, but having them installed with their own disks. Please can some one guide me on how to do this? I have Ovirt running, with local storage hypervisors. Anytime I try to use a template, the vm is created and booted with the template's disk. I would especially appreciate how to do this with ansible. Im trying to automate CentOS and Ubuntu VMs.
On 2021-11-17 12:02, notify.sina@gmail.com wrote:
Hi All
Im very stumped on how to create VMs from templates I've made, but having them installed with their own disks. Please can some one guide me on how to do this? I have Ovirt running, with local storage hypervisors.
Anytime I try to use a template, the vm is created and booted with the template's disk. I would especially appreciate how to do this with ansible. Im trying to automate CentOS and Ubuntu VMs. _______________________________________________ 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/OX5MWWMYAW4OTY...
When you make a VM from a template there are two possibilities. If the VM type is set to desktop, a qcow overlay is created against the template's disk images. Any changes made in the VM are stored in the overlay.. If the VM type is set to server the template's disks are copied to a new disk, it will have the same name as the template disk, but it is in fact a new disk with the template data copied over.
Ok thanks Sounds odd but no problem How do I make the new VM use its own disk, named after itself? On Wed, 17 Nov 2021 at 19:45, Alex McWhirter <alex@triadic.us> wrote:
On 2021-11-17 12:02, notify.sina@gmail.com wrote:
Hi All
Im very stumped on how to create VMs from templates I've made, but having them installed with their own disks. Please can some one guide me on how to do this? I have Ovirt running, with local storage hypervisors.
Anytime I try to use a template, the vm is created and booted with the template's disk. I would especially appreciate how to do this with ansible. Im trying to automate CentOS and Ubuntu VMs. _______________________________________________ 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/OX5MWWMYAW4OTY...
When you make a VM from a template there are two possibilities.
If the VM type is set to desktop, a qcow overlay is created against the template's disk images. Any changes made in the VM are stored in the overlay..
If the VM type is set to server the template's disks are copied to a new disk, it will have the same name as the template disk, but it is in fact a new disk with the template data copied over.
-- Sent from MetroMail
On 2021-11-17 13:50, Sina Owolabi wrote:
Ok thanks Sounds odd but no problem
How do I make the new VM use its own disk, named after itself?
On Wed, 17 Nov 2021 at 19:45, Alex McWhirter <alex@triadic.us> wrote:
On 2021-11-17 12:02, notify.sina@gmail.com wrote:
Hi All
Im very stumped on how to create VMs from templates I've made, but having them installed with their own disks. Please can some one guide me on how to do this? I have Ovirt running, with local storage hypervisors.
Anytime I try to use a template, the vm is created and booted with the template's disk. I would especially appreciate how to do this with ansible. Im trying to automate CentOS and Ubuntu VMs. _______________________________________________ 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/OX5MWWMYAW4OTY...
When you make a VM from a template there are two possibilities.
If the VM type is set to desktop, a qcow overlay is created against the template's disk images. Any changes made in the VM are stored in the overlay..
If the VM type is set to server the template's disks are copied to a new disk, it will have the same name as the template disk, but it is in fact a new disk with the template data copied over. -- Sent from MetroMail
You can create a template with no disk, then VM's created from that template will also have no disk. Then add a new disk to the VM after you create it. This is how the default blank template works. You can also create a template with an empty disk, then every VM created will also get an empty disk by default. You can always rename disks as well.
Im sorry, I am trying to wrap my head around this but it is difficult. I just want to be able to stand up new vms, with their own storage, similar to how I can with plain vanilla KVM, with a template or without, maybe even with a kickstart, and hopefully with ansible. Right now anytime I try to create a VM, using the template, (with ansible), it gets the template disk attached, and from the console I see the new vm is named as the vm I created the template with. Cloud init script that is meant to rename the vm, and join it to IPA, is ignored. If I create storage for the vm, before creating it, both the template storage and the new storage are attached to the vm, which is also confusing. Cloud init is also ignored. I didn't think something this straightforward would end up needing a shift in thinking about how vms are created, especially with a product that's more than likely using kvm under the hood. I would appreciate some straightforward guiding steps, if I can get them. Really. It's been a frustrating week.
On 2021-11-17 13:50, Sina Owolabi wrote:
You can create a template with no disk, then VM's created from that template will also have no disk. Then add a new disk to the VM after you create it. This is how the default blank template works. You can also create a template with an empty disk, then every VM created will also get an empty disk by default. You can always rename disks as well.
Hello, The VMs can get created from a template otherwise the blank template is used if a particular template is used it can be thin dependent VM the VMs disks is linked to the Templates disk and it just carries the changes made in the VMs disk (this is quicker and uses less space if you a lot of disks). The other option is to create a cloned VM and this will copy the Templates disk to the VM so it's no longer dependent. In the ansible documentation look for the clone option. https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_mod... https://www.ovirt.org/documentation/virtual_machine_management_guide/index.h... Virtual Machine Management Guide<https://www.ovirt.org/documentation/virtual_machine_management_guide/index.html> oVirt is a free open-source virtualization solution for your entire enterprise www.ovirt.org For the cloud-init does the cloud-init package need to be installed on the template image? Regards, Paul S. ________________________________ From: notify.sina@gmail.com <notify.sina@gmail.com> Sent: 18 November 2021 07:34 To: users@ovirt.org <users@ovirt.org> Subject: [ovirt-users] Re: Creating VMs from templates with their own disks Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Im sorry, I am trying to wrap my head around this but it is difficult. I just want to be able to stand up new vms, with their own storage, similar to how I can with plain vanilla KVM, with a template or without, maybe even with a kickstart, and hopefully with ansible. Right now anytime I try to create a VM, using the template, (with ansible), it gets the template disk attached, and from the console I see the new vm is named as the vm I created the template with. Cloud init script that is meant to rename the vm, and join it to IPA, is ignored. If I create storage for the vm, before creating it, both the template storage and the new storage are attached to the vm, which is also confusing. Cloud init is also ignored. I didn't think something this straightforward would end up needing a shift in thinking about how vms are created, especially with a product that's more than likely using kvm under the hood. I would appreciate some straightforward guiding steps, if I can get them. Really. It's been a frustrating week.
On 2021-11-17 13:50, Sina Owolabi wrote:
You can create a template with no disk, then VM's created from that template will also have no disk. Then add a new disk to the VM after you create it. This is how the default blank template works. You can also create a template with an empty disk, then every VM created will also get an empty disk by default. You can always rename disks as well.
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovir... To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email
participants (4)
-
Alex McWhirter -
notify.sina＠gmail.com -
Sina Owolabi
-
Staniforth, Paul