- Users - oVirt List Archives

routing table and wrong ip rule attribution on hosts
by Nathanaël Blanchet 30 Nov '21

30 Nov '21

Hi all, I 've finished migration from 4.4.4 to 4.4.9 and I'm facing a strange issue with routing table on my hosts: all IP addressed interfaces (and in particular gluster and migration ones that requiere an IP) are not part of the "254" or "0" usual ip rule. for instance: [root@fuego ~]# nmcli con sh gluster |grep ipv4.route-table ipv4.route-table: 202179335 [root@fuego ~]# nmcli con sh migration |grep ipv4.route-table ipv4.route-table: 316605387 but ovirtmgmt: [root@fuego ~]# nmcli con sh ovirtmgmt |grep ipv4.route-table ipv4.route-table: 254 (main) and obviously the main route table is empty: [root@ ~]# ip ro default via 10.34.100.65 dev ovirtmgmt proto dhcp metric 425 10.34.100.0/24 dev ovirtmgmt proto kernel scope link src 10.34.100.116 metric 425 None of the concerned hosts can ping each other on such interface, and live migrations systematically fail. This behaviour is new with 4.4.9 and I don't know if it is a new (and not achevied) network feature introduced with centos stream to deal network filtering packets. A simple workaround would be "nmcli connection mod migration ipv4.route-table 0 && nmcli con up migration", but I'd like to understand why such strange (and unuseful ?) rule table are now randomly attributed? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 3

possible problem with mailing list
by Staniforth, Paul 29 Nov '21

29 Nov '21

Hello, When I login to the web mailing list system https://lists.ovirt.org/archives/list/users@ovirt.org/ It doesn't seem to send new posts and the discussions you've posted in and recently active discussions sections have a constantly rotating spinner. Regards, Paul S. To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

1 0

Updating hosted-engine from 4.4.5 to latest(4.4.9) fail with "DNF name '_get_key_for_package' is not defined"
by rene.purcell＠gmail.com 29 Nov '21

29 Nov '21

Hi! I'm having issue updating my nodes, normally I just clicked on them and update each of them without problem. I haven't updated since few months, now I'm unable to. So I checked the doc and saw that I probably should update my engine first so that's what I tried. Info on my setup: 2 nodes hosted-engine is ran as a vm on the same cluster storage is hosted on a NFS share on my qnap. I'm following the doc (https://www.ovirt.org/documentation/upgrade_guide/#updates-between-minor-re…) Fast recap I've put hosted-engine in global maintenance mode, installed the latest ovirt-release44.rpm on engine, engine-upgrade-check, yum update ovirt\*setup\* and finally ran the engine-setup which did not complete successfully.. Here's the error I get: [....] [ INFO ] DNF Downloaded python3-numexpr-2.7.1-1.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded perl-encoding-2.22-3.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded libXft-2.3.3-1.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded libXi-1.7.10-1.el8.x86_64.rpm SKIPPED Already downloaded [ INFO ] DNF Downloaded mcpp-2.7.2-20.el8.x86_64.rpm SKIPPED Already downloaded [ ERROR ] DNF name '_get_key_for_package' is not defined [ ERROR ] Failed to execute stage 'Package installation': name '_get_key_for_package' is not defined [ INFO ] DNF Performing DNF transaction rollback [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20211126111800-qsadme.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20211126111839-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed I can't find more info in the log specified in the output, I understand there's something wrong with the list of packages the script try to load/update but can't find any bug reports or other people having this issue so I'm running out of idea.. Anybody have a solutions to try fixing this and complete my engine upgrade to 4.4.9? Thanks a lot, have a great day!!

3 5

hosted engine vm not present
by Nathanaël Blanchet 28 Nov '21

28 Nov '21

Hello I successfully migrated from HE 4.3.10 to HE 4.4.9, but I think I commited a mistake: The HostedEngine vm was running on the host (haboob) where I deployed the upgrade path. Everything was ok except that I deployed it on the wrong host (haboob). So I live migrated the HostedEngine on the centos prexisting host (kilimanjaro) and erase haboob. Then I reinstalled a new host (fuego) to replace haboob. The HostedEngine is able to migrate between kilimajaro and fuego but now the vm seems to not be seen by any host when doing: [root@fuego ~]# hosted-engine --vm-status --== Host fuego (id: 1) status ==-- Host ID : 1 Host timestamp : 3252 Score : 3350 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : fuego Local maintenance : False stopped : False crc32 : 14527b72 conf_on_shared_storage : True local_conf_timestamp : 3257 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=3252 (Sun Nov 28 18:27:29 2021) host-id=1 score=3350 vm_conf_refresh_time=3257 (Sun Nov 28 18:27:34 2021) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host kilimanjaro.v100.abes.fr (id: 3) status ==-- Host ID : 3 Host timestamp : 65261186 Score : 0 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down_unexpected", "detail": "unknown"} Hostname : kilimanjaro.v100.abes.fr Local maintenance : True stopped : False crc32 : c381cf1e conf_on_shared_storage : True local_conf_timestamp : 65261189 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=65261186 (Sun Nov 28 19:27:23 2021) host-id=3 score=0 vm_conf_refresh_time=65261189 (Sun Nov 28 19:27:26 2021) conf_on_shared_storage=True maintenance=True state=LocalMaintenance stopped=False When doing hosted-engine --console, it returns: [root@fuego ~]# hosted-engine --console Command VM.getStats with args {'vmID': '74d2966c-2efa-41f0-a5c3-dd383f690a92'} failed: (code=1, message=Virtual machine does not exist: {'vmId': '74d2966c-2efa-41f0-a5c3-dd383f690a92'}) The engine VM is not on this host It is like the vmID was the old 4.3.10 HostedEngine that doesn't exist anymore. How can I make the new HostedEngine vmID be the good one known by HA and hosts? *I'm afraid to lose the HostedEngine vm when stopping it!* Thank you for your precious help. -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

Re: Creating VMs from templates with their own disks
by Strahil Nikolov 28 Nov '21

28 Nov '21

Yep. Your code: cloud_init: custom_script: | host_name: "{{ vm_fqdn }}" user_name: myadmin user_password: <password> write_files: - path: /tmp/setup.sh permissions: '0755' content: | #!/bin/bash echo "$(hostnamectl)" >> /tmp/myhostname.txt Yet, in "custom_script" there is no "host_name" (indentation shows that host_name is part of the custom script, not to mention the "|" character). Try with: cloud_init: host_name: "{{ vm_fqdn }}" user_name: myadmin # I can't find this one in https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_mo… #user_password: <password> root_password: <vaulted_password> custom_script: | write_files: - path: /tmp/setup.sh permissions: '0755' content: | #!/bin/bash echo "$(hostnamectl)" >> /tmp/myhostname.txt Best Regards, Strahil Nikolov В петък, 26 ноември 2021 г., 19:33:16 Гринуич+2, Staniforth, Paul <p.staniforth(a)leedsbeckett.ac.uk> написа: #yiv9174097940 P {margin-top:0;margin-bottom:0;}Hi Sina, These should be part of the cloud-init dictionary and are strict about indentation. e.g. from the documentation. - name: Run VM with cloud init ovirt.ovirt.ovirt_vm: name: rhel7 template: rhel7 cluster: Default memory: 1GiB high_availability: true high_availability_priority: 50 # Available from Ansible 2.5 cloud_init: dns_servers: '8.8.8.8 8.8.4.4' nic_boot_protocol: static nic_ip_address: 10.34.60.86 nic_netmask: 255.255.252.0 nic_gateway: 10.34.63.254 nic_name: eth1 host_name: example.com custom_script: | write_files: - content: | Hello, world! path: /tmp/greeting.txt permissions: '0644' user_name: root root_password: super_passwordRegards, Paul S. From: Sina Owolabi <notify.sina(a)gmail.com> Sent: 26 November 2021 16:43 To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [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. Same thing when its written as 'hostname': atal: [ovirt.ovirt.trove.internal]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (ovirt.ovirt.ovirt_vm) module: hostname Supported parameters include: affinity_gr gs, affinity_label_mappings, allow_partial_import, auth, ballooning_enabled, bios_type, boot_devices, boot_menu, cd_iso, clone, clone_permissions, cloud_init, cloud_init_nics, cloud_i t, cluster, cluster_mappings, comment, cpu_cores, cpu_mode, cpu_pinning, cpu_shares, cpu_sockets, cpu_threads, custom_compatibility_version, custom_emulated_machine, custom_properties rotected, description, disk_format, disks, domain_mappings, exclusive, export_domain, export_ova, fetch_nested, force, force_migrate, graphical_console, high_availability, high_availa ority, host, host_devices, id, initrd_path, instance_type, io_threads, kernel_params, kernel_params_persist, kernel_path, kvm, lease, lun_mappings, memory, memory_guaranteed, memory_m e, name, nested_attributes, next_run, nics, numa_nodes, numa_tune_mode, operating_system, placement_policy, placement_policy_hosts, poll_interval, quota_id, reassign_bad_macs, rng_dev mappings, serial_console, serial_policy, serial_policy_value, smartcard_enabled, snapshot_name, snapshot_vm, soundcard_enabled, sso, state, stateless, storage_domain, sysprep, templat e_version, ticket, timeout, timezone, type, usb_support, use_latest_template_version, vmware, vnic_profile_mappings, wait, watchdog, xen"} On Fri, Nov 26, 2021 at 5:35 PM Sina Owolabi <notify.sina(a)gmail.com> wrote: > > And Paul > > when I try to add host_name, I get this error: > > TASK [Creates new virtual machine] > **************************************************************************************************************************************************** > fatal: [ovirt.ovirt.trove.internal]: FAILED! => {"changed": false, > "msg": "Unsupported parameters for (ovirt.ovirt.ovirt_vm) module: > host_name, regenerate_ssh_keys Supported parameter > affinity_group_mappings, affinity_label_mappings, > allow_partial_import, auth, ballooning_enabled, bios_type, > boot_devices, boot_menu, cd_iso, clone, clone_permissions, cloud_init, > cl > ics, cloud_init_persist, cluster, cluster_mappings, comment, > cpu_cores, cpu_mode, cpu_pinning, cpu_shares, cpu_sockets, > cpu_threads, custom_compatibility_version, custom_emulated_mach > m_properties, delete_protected, description, disk_format, disks, > domain_mappings, exclusive, export_domain, export_ova, fetch_nested, > force, force_migrate, graphical_console, high_ava > high_availability_priority, host, host_devices, id, initrd_path, > instance_type, io_threads, kernel_params, kernel_params_persist, > kernel_path, kvm, lease, lun_mappings, memory, memor > ed, memory_max, migrate, name, nested_attributes, next_run, nics, > numa_nodes, numa_tune_mode, operating_system, placement_policy, > placement_policy_hosts, poll_interval, quota_id, reas > acs, rng_device, role_mappings, serial_console, serial_policy, > serial_policy_value, smartcard_enabled, snapshot_name, snapshot_vm, > soundcard_enabled, sso, state, stateless, storage_do > rep, template, template_version, ticket, timeout, timezone, type, > usb_support, use_latest_template_version, vmware, > vnic_profile_mappings, wait, watchdog, xen"} > > On Fri, Nov 26, 2021 at 5:11 PM Staniforth, Paul > <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > > > Hi Sina, > > I get easily confused with cloud-init but shouldn't you be setting the hostname, username, etc before the custom script? > > > > Also, you could rename the disk as a separate play in your playbook. > > > > e.g. > > > > # Change Disk Name > > - ovirt.ovirt.ovirt_disk: > > id: 00000000-0000-0000-0000-000000000000 > > storage_domain: data > > name: "new_disk_name" > > vm_name: rhel7 > > > > > > Regards, > > Paul S. > > > > ________________________________ > > From: Sina Owolabi <notify.sina(a)gmail.com> > > Sent: 26 November 2021 15:00 > > To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > > Cc: users(a)ovirt.org <users(a)ovirt.org> > > Subject: Re: [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. > > > > Thanks Paul. > > > > I seem to be getting this by hand, but trying with ansible, I think my skills are a bit lacking. > > I can create with ansible, and it seems to work well, except for the fact that the new vm is > > created with the hostname of the vm from which the template was made. > > The disk is also named by the template. > > My ansiblle yaml is below and I'm pretty sure its wrong (especially where it needs to use cloud-init to inject the correct hostname, and the other prepping I would like to add). > > Please can you help correct me? > > > > --- > > - hosts: ovirt.ovirt.mydom.internal > > tasks: > > - import_tasks: ovirt_auth.yml > > > > - name: Creates new virtual machine > > ovirt.ovirt.ovirt_vm: > > auth: "{{ ovirt_auth }}" > > name: "{{ vm_fqdn }}" > > state: present > > clone: true > > cluster: lrg0-ovirt-cluster > > storage_domain: lrg0-ovirt-mydom-internal-Local > > memory: 16GiB > > cpu_cores: 8 > > cpu_sockets: 2 > > template: template-test00-centos8 > > type: server > > operating_system: other_linux > > sso: true > > disk_format: raw > > # disks: > > # - name: "{{ vm_fqdn }}-disk0" > > # bootable: true > > # nics: > > # - name: nic1 > > # boot_protocol: dhcp > > # interface: virtio > > # profile_name: "{{ net_profile_name }}" > > graphical_console: > > protocol: > > - spice > > - vnc > > cloud_init: > > custom_script: | > > host_name: "{{ vm_fqdn }}" > > user_name: myadmin > > user_password: <password> > > write_files: > > - path: /tmp/setup.sh > > permissions: '0755' > > content: | > > #!/bin/bash > > echo "$(hostnamectl)" >> /tmp/myhostname.txt > > > > ipa-client-install --hostname=`hostname -f` \ > > --mkhomedir --domain=services.mydom.internal \ > > --realm=SERVICES.MYDOM.INTERNAL --no-ntp \ > > --principal=admin --password=<password> \ > > --enable-dns-updates --unattended > > runcmd: > > - [ /tmp/setup.sh, "{{ vm_fqdn }}" ] > > > > On Wed, Nov 24, 2021 at 9:26 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > > > Hello Sina, > > > > to use the template. > > > > Create new VM and select the template. > > > > Click the advanced options. > > > > In the boot section you can set the HD to be the first boot devices and unselect any CD. > > In the Resource Allocation section, you can set the storage allocation to clone instead of thin ( this will create a copy of the template disk), you can also set the disk alias name. > > > > you can also edit the template to make sure the HD is the first boot device. > > > > I don't know what's in your ansible yaml definition. > > > > Cloning is for copying VMs or snapshots not templates. > > > > Regards, > > > > Paul S. > > ________________________________ > > From: Sina Owolabi <notify.sina(a)gmail.com> > > Sent: 24 November 2021 09:28 > > To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > > Cc: users(a)ovirt.org <users(a)ovirt.org> > > Subject: Re: [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. > > > > Hello > > > > Sorry for the late reply, work has been crazy. > > > > This doesnt seem to work as advertised, or I am still not getting it. > > Either way I would really appreciate some help and guidance. > > > > Steps I have attempted: > > 1. Create and configure VM as I want it to be (disk, partitioning, etc). > > 2. Shutdown the vm, create a template from it. > > > > Cloning manually: > > Cloning fails with this message: > > Error while executing action: > > clone00.domain.tld: > > > > Cannot add VM. One or more provided storage domains are either not in active status or of an illegal type for the requested operation. > > > > I cant modify the storage allocation, and the disk its attempting to use is the disk of the source VM. > > > > Manual template install: > > Choosing to install manually with a template requires me to add a new disk, and to boot off the CD (defined in the template) and manually set things up. This I do not wish to do, because I would rather automate. > > > > Cloning with ansible, defining the cloud-init script and using the template: > > VM is successfully created, but logging in with remote-viewer drops me into the installation process (setting up from the attached ISO). Which is also not desired. > > > > Please help me with what I am doing wrong. > > Again the goal is to have the vm setup with its own credentials. > > > > > > On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > > > 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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ansi… > > > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > Virtual Machine Management Guide > > oVirt is a free open-source virtualization solution for your entire enterprise > > https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ovirt.… > > For the cloud-init does the cloud-init package need to be installed on the template image? > > > > > > Regards, > > > > Paul S. > > ________________________________ > > From: notify.sina(a)gmail.com <notify.sina(a)gmail.com> > > Sent: 18 November 2021 07:34 > > To: users(a)ovirt.org <users(a)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(a)ovirt.org > > To unsubscribe send an email to users-leave(a)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.ovi… > > To view the terms under which this email is distributed, please go to:- > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbeck… > > > > > > > > -- > > > > cordially yours, > > > > Sina Owolabi > > > > +2348176469061 > > To view the terms under which this email is distributed, please go to:- > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbeck… > > > > > > > > -- > > > > cordially yours, > > > > Sina Owolabi > > > > +2348176469061 > > To view the terms under which this email is distributed, please go to:- > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbeck… > > > > -- > > cordially yours, > > Sina Owolabi > > +2348176469061 -- cordially yours, Sina Owolabi +2348176469061 To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/ZUHT7Z7QV2U5M…

3 8

Attaching LVM logical volume to VM
by th3penguinwhisperer＠gmail.com 28 Nov '21

28 Nov '21

Hi, I've just migrated from Libvirt/kvm to oVirt. In libvirt I had a VM that had an LVM logical volume that was attached to a guest as a disk. However in oVirt I can't immediately find such a capability. I understand that this would "pin" my VM to this host but that's perfectly fine. Any pointers how this can be done? Thanks in advance!

3 4

Hosted Engine Deploy Failure
by Gary Pedretty 28 Nov '21

28 Nov '21

Keep getting the following error on a new clean install of the Hosted Engine on CentOS Stream. This is latest updated CentOS Stream (version 8 not 9) and latest version of ovirt https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm Attempted via the Cockpit Web Interface Deployment Wizard. Any ideas? Some really old references to this issue a few years ago, but nothing recent. Gary Deployment Log Snippet. [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user 'admin@internal': Unable to log in because the user account is disabled or locked. Contact the system administrator.. [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user 'admin@internal': Unable to log in because the user account is disabled or locked. Contact the system administrator.."}

2 2

Re: Creating VMs from templates with their own disks
by Sina Owolabi 26 Nov '21

26 Nov '21

And Paul when I try to add host_name, I get this error: TASK [Creates new virtual machine] **************************************************************************************************************************************************** fatal: [ovirt.ovirt.trove.internal]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (ovirt.ovirt.ovirt_vm) module: host_name, regenerate_ssh_keys Supported parameter affinity_group_mappings, affinity_label_mappings, allow_partial_import, auth, ballooning_enabled, bios_type, boot_devices, boot_menu, cd_iso, clone, clone_permissions, cloud_init, cl ics, cloud_init_persist, cluster, cluster_mappings, comment, cpu_cores, cpu_mode, cpu_pinning, cpu_shares, cpu_sockets, cpu_threads, custom_compatibility_version, custom_emulated_mach m_properties, delete_protected, description, disk_format, disks, domain_mappings, exclusive, export_domain, export_ova, fetch_nested, force, force_migrate, graphical_console, high_ava high_availability_priority, host, host_devices, id, initrd_path, instance_type, io_threads, kernel_params, kernel_params_persist, kernel_path, kvm, lease, lun_mappings, memory, memor ed, memory_max, migrate, name, nested_attributes, next_run, nics, numa_nodes, numa_tune_mode, operating_system, placement_policy, placement_policy_hosts, poll_interval, quota_id, reas acs, rng_device, role_mappings, serial_console, serial_policy, serial_policy_value, smartcard_enabled, snapshot_name, snapshot_vm, soundcard_enabled, sso, state, stateless, storage_do rep, template, template_version, ticket, timeout, timezone, type, usb_support, use_latest_template_version, vmware, vnic_profile_mappings, wait, watchdog, xen"} On Fri, Nov 26, 2021 at 5:11 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > Hi Sina, > I get easily confused with cloud-init but shouldn't you be setting the hostname, username, etc before the custom script? > > Also, you could rename the disk as a separate play in your playbook. > > e.g. > > # Change Disk Name > - ovirt.ovirt.ovirt_disk: > id: 00000000-0000-0000-0000-000000000000 > storage_domain: data > name: "new_disk_name" > vm_name: rhel7 > > > Regards, > Paul S. > > ________________________________ > From: Sina Owolabi <notify.sina(a)gmail.com> > Sent: 26 November 2021 15:00 > To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [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. > > Thanks Paul. > > I seem to be getting this by hand, but trying with ansible, I think my skills are a bit lacking. > I can create with ansible, and it seems to work well, except for the fact that the new vm is > created with the hostname of the vm from which the template was made. > The disk is also named by the template. > My ansiblle yaml is below and I'm pretty sure its wrong (especially where it needs to use cloud-init to inject the correct hostname, and the other prepping I would like to add). > Please can you help correct me? > > --- > - hosts: ovirt.ovirt.mydom.internal > tasks: > - import_tasks: ovirt_auth.yml > > - name: Creates new virtual machine > ovirt.ovirt.ovirt_vm: > auth: "{{ ovirt_auth }}" > name: "{{ vm_fqdn }}" > state: present > clone: true > cluster: lrg0-ovirt-cluster > storage_domain: lrg0-ovirt-mydom-internal-Local > memory: 16GiB > cpu_cores: 8 > cpu_sockets: 2 > template: template-test00-centos8 > type: server > operating_system: other_linux > sso: true > disk_format: raw > # disks: > # - name: "{{ vm_fqdn }}-disk0" > # bootable: true > # nics: > # - name: nic1 > # boot_protocol: dhcp > # interface: virtio > # profile_name: "{{ net_profile_name }}" > graphical_console: > protocol: > - spice > - vnc > cloud_init: > custom_script: | > host_name: "{{ vm_fqdn }}" > user_name: myadmin > user_password: <password> > write_files: > - path: /tmp/setup.sh > permissions: '0755' > content: | > #!/bin/bash > echo "$(hostnamectl)" >> /tmp/myhostname.txt > > ipa-client-install --hostname=`hostname -f` \ > --mkhomedir --domain=services.mydom.internal \ > --realm=SERVICES.MYDOM.INTERNAL --no-ntp \ > --principal=admin --password=<password> \ > --enable-dns-updates --unattended > runcmd: > - [ /tmp/setup.sh, "{{ vm_fqdn }}" ] > > On Wed, Nov 24, 2021 at 9:26 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > Hello Sina, > > to use the template. > > Create new VM and select the template. > > Click the advanced options. > > In the boot section you can set the HD to be the first boot devices and unselect any CD. > In the Resource Allocation section, you can set the storage allocation to clone instead of thin ( this will create a copy of the template disk), you can also set the disk alias name. > > you can also edit the template to make sure the HD is the first boot device. > > I don't know what's in your ansible yaml definition. > > Cloning is for copying VMs or snapshots not templates. > > Regards, > > Paul S. > ________________________________ > From: Sina Owolabi <notify.sina(a)gmail.com> > Sent: 24 November 2021 09:28 > To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [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. > > Hello > > Sorry for the late reply, work has been crazy. > > This doesnt seem to work as advertised, or I am still not getting it. > Either way I would really appreciate some help and guidance. > > Steps I have attempted: > 1. Create and configure VM as I want it to be (disk, partitioning, etc). > 2. Shutdown the vm, create a template from it. > > Cloning manually: > Cloning fails with this message: > Error while executing action: > clone00.domain.tld: > > Cannot add VM. One or more provided storage domains are either not in active status or of an illegal type for the requested operation. > > I cant modify the storage allocation, and the disk its attempting to use is the disk of the source VM. > > Manual template install: > Choosing to install manually with a template requires me to add a new disk, and to boot off the CD (defined in the template) and manually set things up. This I do not wish to do, because I would rather automate. > > Cloning with ansible, defining the cloud-init script and using the template: > VM is successfully created, but logging in with remote-viewer drops me into the installation process (setting up from the attached ISO). Which is also not desired. > > Please help me with what I am doing wrong. > Again the goal is to have the vm setup with its own credentials. > > > On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > 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_mo… > > https://www.ovirt.org/documentation/virtual_machine_management_guide/index.… > Virtual Machine Management Guide > 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(a)gmail.com <notify.sina(a)gmail.com> > Sent: 18 November 2021 07:34 > To: users(a)ovirt.org <users(a)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(a)ovirt.org > To unsubscribe send an email to users-leave(a)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.ovi… > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > > > > -- > > cordially yours, > > Sina Owolabi > > +2348176469061 > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > > > > -- > > cordially yours, > > Sina Owolabi > > +2348176469061 > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email -- cordially yours, Sina Owolabi +2348176469061

2 2

Re: Creating VMs from templates with their own disks
by Sina Owolabi 26 Nov '21

26 Nov '21

Thanks guys, not sure why the ansible isnt showing up, Posting again: - hosts: ovirt.ovirt.mydom.internal tasks: - import_tasks: ovirt_auth.yml - name: Creates new virtual machine ovirt.ovirt.ovirt_vm: auth: "{{ ovirt_auth }}" name: "{{ vm_fqdn }}" state: present clone: true cluster: lrg0-ovirt-cluster storage_domain: lrg0-ovirt-mydom-internal-Local memory: 16GiB cpu_cores: 8 cpu_sockets: 2 template: template-test00-centos8 type: server operating_system: other_linux sso: true disk_format: raw # disks: # - name: "{{ vm_fqdn }}-disk0" # bootable: true # nics: # - name: nic1 # boot_protocol: dhcp # interface: virtio # profile_name: "{{ net_profile_name }}" graphical_console: protocol: - spice - vnc cloud_init: custom_script: | host_name: "{{ vm_fqdn }}" user_name: myadmin user_password: <password> write_files: - path: /tmp/setup.sh permissions: '0755' content: | #!/bin/bash echo "$(hostnamectl)" >> /tmp/myhostname.txt ipa-client-install --hostname=`hostname -f` \ --mkhomedir --domain=services.mydom.internal \ --realm=SERVICES.MYDOM.INTERNAL --no-ntp \ --principal=admin --password=<password> \ --enable-dns-updates --unattended runcmd: - [ /tmp/setup.sh, "{{ vm_fqdn }}" ] On Fri, Nov 26, 2021 at 5:11 PM Staniforth, Paul < P.Staniforth(a)leedsbeckett.ac.uk> wrote: > Hi Sina, > I get easily confused with cloud-init but shouldn't you be > setting the hostname, username, etc before the custom script? > > Also, you could rename the disk as a separate play in your playbook. > > e.g. > > # Change Disk Name- ovirt.ovirt.ovirt_disk: > id: 00000000-0000-0000-0000-000000000000 > storage_domain: data > name: "new_disk_name" > vm_name: rhel7 > > > Regards, > Paul S. > > ------------------------------ > *From:* Sina Owolabi <notify.sina(a)gmail.com> > *Sent:* 26 November 2021 15:00 > *To:* Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > *Cc:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* Re: [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. > Thanks Paul. > > I seem to be getting this by hand, but trying with ansible, I think my > skills are a bit lacking. > I can create with ansible, and it seems to work well, except for the fact > that the new vm is > created with the hostname of the vm from which the template was made. > The disk is also named by the template. > My ansiblle yaml is below and I'm pretty sure its wrong (especially where > it needs to use cloud-init to inject the correct hostname, and the other > prepping I would like to add). > Please can you help correct me? > > --- > - hosts: ovirt.ovirt.mydom.internal > tasks: > - import_tasks: ovirt_auth.yml > > - name: Creates new virtual machine > ovirt.ovirt.ovirt_vm: > auth: "{{ ovirt_auth }}" > name: "{{ vm_fqdn }}" > state: present > clone: true > cluster: lrg0-ovirt-cluster > storage_domain: lrg0-ovirt-mydom-internal-Local > memory: 16GiB > cpu_cores: 8 > cpu_sockets: 2 > template: template-test00-centos8 > type: server > operating_system: other_linux > sso: true > disk_format: raw > # disks: > # - name: "{{ vm_fqdn }}-disk0" > # bootable: true > # nics: > # - name: nic1 > # boot_protocol: dhcp > # interface: virtio > # profile_name: "{{ net_profile_name }}" > graphical_console: > protocol: > - spice > - vnc > cloud_init: > custom_script: | > host_name: "{{ vm_fqdn }}" > user_name: myadmin > user_password: <password> > write_files: > - path: /tmp/setup.sh > permissions: '0755' > content: | > #!/bin/bash > echo "$(hostnamectl)" >> /tmp/myhostname.txt > > ipa-client-install --hostname=`hostname -f` \ > --mkhomedir --domain=services.mydom.internal \ > --realm=SERVICES.MYDOM.INTERNAL --no-ntp \ > --principal=admin --password=<password> \ > --enable-dns-updates --unattended > runcmd: > - [ /tmp/setup.sh, "{{ vm_fqdn }}" ] > > On Wed, Nov 24, 2021 at 9:26 PM Staniforth, Paul < > P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > Hello Sina, > > to use the template. > > Create new VM and select the template. > > Click the advanced options. > > In the boot section you can set the HD to be the first boot devices and > unselect any CD. > In the Resource Allocation section, you can set the storage allocation to > clone instead of thin ( this will create a copy of the template disk), you > can also set the disk alias name. > > you can also edit the template to make sure the HD is the first boot > device. > > I don't know what's in your ansible yaml definition. > > Cloning is for copying VMs or snapshots not templates. > > Regards, > > Paul S. > ------------------------------ > *From:* Sina Owolabi <notify.sina(a)gmail.com> > *Sent:* 24 November 2021 09:28 > *To:* Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > *Cc:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* Re: [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. > Hello > > Sorry for the late reply, work has been crazy. > > This doesnt seem to work as advertised, or I am still not getting it. > Either way I would really appreciate some help and guidance. > > Steps I have attempted: > 1. Create and configure VM as I want it to be (disk, partitioning, etc). > 2. Shutdown the vm, create a template from it. > > Cloning manually: > Cloning fails with this message: > Error while executing action: > clone00.domain.tld: > > - Cannot add VM. One or more provided storage domains are either not > in active status or of an illegal type for the requested operation. > > I cant modify the storage allocation, and the disk its attempting to use > is the disk of the source VM. > > Manual template install: > Choosing to install manually with a template requires me to add a new > disk, and to boot off the CD (defined in the template) and manually set > things up. This I do not wish to do, because I would rather automate. > > Cloning with ansible, defining the cloud-init script and using the > template: > VM is successfully created, but logging in with remote-viewer drops me > into the installation process (setting up from the attached ISO). Which is > also not desired. > > Please help me with what I am doing wrong. > Again the goal is to have the vm setup with its own credentials. > > > On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul < > P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > 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_mo… > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ansi…> > > > https://www.ovirt.org/documentation/virtual_machine_management_guide/index.… > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > Virtual Machine Management Guide > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > oVirt is a free open-source virtualization solution for your entire > enterprise > www.ovirt.org > <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ovirt.…> > For the cloud-init does the cloud-init package need to be installed on the > template image? > > > Regards, > > Paul S. > ------------------------------ > *From:* notify.sina(a)gmail.com <notify.sina(a)gmail.com> > *Sent:* 18 November 2021 07:34 > *To:* users(a)ovirt.org <users(a)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(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > <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… > <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.ovi… > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbeck…> > > > > -- > > cordially yours, > > Sina Owolabi > > +2348176469061 > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbeck…> > > > > -- > > cordially yours, > > Sina Owolabi > > +2348176469061 > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > > -- cordially yours, Sina Owolabi +2348176469061

1 0

Re: Creating VMs from templates with their own disks
by Sina Owolabi 26 Nov '21

26 Nov '21

Thanks Paul. I seem to be getting this by hand, but trying with ansible, I think my skills are a bit lacking. I can create with ansible, and it seems to work well, except for the fact that the new vm is created with the hostname of the vm from which the template was made. The disk is also named by the template. My ansiblle yaml is below and I'm pretty sure its wrong (especially where it needs to use cloud-init to inject the correct hostname, and the other prepping I would like to add). Please can you help correct me? --- - hosts: ovirt.ovirt.mydom.internal tasks: - import_tasks: ovirt_auth.yml - name: Creates new virtual machine ovirt.ovirt.ovirt_vm: auth: "{{ ovirt_auth }}" name: "{{ vm_fqdn }}" state: present clone: true cluster: lrg0-ovirt-cluster storage_domain: lrg0-ovirt-mydom-internal-Local memory: 16GiB cpu_cores: 8 cpu_sockets: 2 template: template-test00-centos8 type: server operating_system: other_linux sso: true disk_format: raw # disks: # - name: "{{ vm_fqdn }}-disk0" # bootable: true # nics: # - name: nic1 # boot_protocol: dhcp # interface: virtio # profile_name: "{{ net_profile_name }}" graphical_console: protocol: - spice - vnc cloud_init: custom_script: | host_name: "{{ vm_fqdn }}" user_name: myadmin user_password: <password> write_files: - path: /tmp/setup.sh permissions: '0755' content: | #!/bin/bash echo "$(hostnamectl)" >> /tmp/myhostname.txt ipa-client-install --hostname=`hostname -f` \ --mkhomedir --domain=services.mydom.internal \ --realm=SERVICES.MYDOM.INTERNAL --no-ntp \ --principal=admin --password=<password> \ --enable-dns-updates --unattended runcmd: - [ /tmp/setup.sh, "{{ vm_fqdn }}" ] On Wed, Nov 24, 2021 at 9:26 PM Staniforth, Paul < P.Staniforth(a)leedsbeckett.ac.uk> wrote: > Hello Sina, > > to use the template. > > Create new VM and select the template. > > Click the advanced options. > > In the boot section you can set the HD to be the first boot devices and > unselect any CD. > In the Resource Allocation section, you can set the storage allocation to > clone instead of thin ( this will create a copy of the template disk), you > can also set the disk alias name. > > you can also edit the template to make sure the HD is the first boot > device. > > I don't know what's in your ansible yaml definition. > > Cloning is for copying VMs or snapshots not templates. > > Regards, > > Paul S. > ------------------------------ > *From:* Sina Owolabi <notify.sina(a)gmail.com> > *Sent:* 24 November 2021 09:28 > *To:* Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > *Cc:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* Re: [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. > Hello > > Sorry for the late reply, work has been crazy. > > This doesnt seem to work as advertised, or I am still not getting it. > Either way I would really appreciate some help and guidance. > > Steps I have attempted: > 1. Create and configure VM as I want it to be (disk, partitioning, etc). > 2. Shutdown the vm, create a template from it. > > Cloning manually: > Cloning fails with this message: > Error while executing action: > clone00.domain.tld: > > - Cannot add VM. One or more provided storage domains are either not > in active status or of an illegal type for the requested operation. > > I cant modify the storage allocation, and the disk its attempting to use > is the disk of the source VM. > > Manual template install: > Choosing to install manually with a template requires me to add a new > disk, and to boot off the CD (defined in the template) and manually set > things up. This I do not wish to do, because I would rather automate. > > Cloning with ansible, defining the cloud-init script and using the > template: > VM is successfully created, but logging in with remote-viewer drops me > into the installation process (setting up from the attached ISO). Which is > also not desired. > > Please help me with what I am doing wrong. > Again the goal is to have the vm setup with its own credentials. > > > On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul < > P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > 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_mo… > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ansi…> > > > https://www.ovirt.org/documentation/virtual_machine_management_guide/index.… > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > Virtual Machine Management Guide > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > oVirt is a free open-source virtualization solution for your entire > enterprise > www.ovirt.org > <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ovirt.…> > For the cloud-init does the cloud-init package need to be installed on the > template image? > > > Regards, > > Paul S. > ------------------------------ > *From:* notify.sina(a)gmail.com <notify.sina(a)gmail.com> > *Sent:* 18 November 2021 07:34 > *To:* users(a)ovirt.org <users(a)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(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > <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… > <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.ovi… > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbeck…> > > > > -- > > cordially yours, > > Sina Owolabi > > +2348176469061 > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > > -- cordially yours, Sina Owolabi +2348176469061

3 2