- Users - oVirt List Archives

Global Maintenance
by Anton Louw 09 Jun '20

09 Jun '20

Hi Everybody, Just a bit of background. A couple of weeks back I moved my self-hosted engine to a standalone manager. Everything went smooth, my environment is up and running without any issues. Just one thing, when I want to reconfigure settings on my self-hosted engine, it says: "It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode" When trying to enable global maintenance from my node, I also get the below: "Cannot connect to the HA daemon, please check the logs" Is there something I missed when I moved my self-hosted engine to a standalone manager? Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

1 0

Upgrade from 4.3.7 to 4.4 report (through scratch reinstall)
by Gianluca Cecchi 09 Jun '20

09 Jun '20

Just to give a report of final success updating from 4.3.7 to 4.4 one of my home labs, composed by a single host. hw: Intel NUC6i5SY with 32G of ram and 2 SSD disks (250Gb and 500Gb) source sw: oVirt 4.3.7 single host with CentOS 7 OS and storage provided through the host itself via NFS (not officially supported, but working, apart when shutdown needed) Two main VMs to migrate to the new environment: Fedora 30 and Slackware Current (just to not forget the first love... ;-) Exported the VMs to an export storage domain offered through an external USB disk dest sw: oVirt node ng 4.4 configured with HCI single host wizard. Installed on the 250Gb disk. I pre-clean the disks (dd of the first 100Mb of the disks) before install, because during the beta/rc phase I noticed the installer was not so smart to cleanup pre-existing configurations. I had problems in the first run, but with engine cleanup and redeploying it went ok. See here for more details: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/6QODLB6J5Z74YC… I configured the gluster domains in the wizard on the whole second disk. I then imported the 2 VMs without problems. Before starting them up I changed their inherited "BIOS Type" from Legacy to "Default Cluster" and they both started without any problem. While in 4.4 I was able to update Fedora VM from 30 to 31 and then 32 and also refresh the slackware-current one that was about a month behind from latest current. With "Default Cluster" BIOS type the VMs start with the following options: " -machine pc-q35-rhel8.1.0,accel=kvm,usb=off,dump-guest-core=off -cpu Broadwell-noTSX" I was then able to download a CentOS 8 cloud image from the predefined ovirt-image-repository storage domain and convert it to template. Created a VM from this template and cloud-init was able to inject the ssh public key and set timezone. Changed cluster type of ths VM to Default as above with a warning from oVirt but without any problem inside the VM and also changed the disk type from virtio to virtio-scsi without problems. Now I enabled incremental backup at engine level and also at disk level of this CentOS 8 VM so that I can make some tests in this regard. Also, I was able to successfully test the ovirt-ansible-shutdown-env ansible role to make a clean overall shutdown of the environment, one of the things that in my previous unsupported setup was a little cumbersome. Right after install I noticed that in CentOS 8 ovirt-node-ng setup, intel_pstate was the default scaling driver setup, but my cpu was almost always crying with core at 2.6Ghz (and temp around 90 degrees) even if attempted to setup conservative profiles and without nothing running, apart engine VM. The NUC is under my working day table and I don't need always performance from it... So I modified (notice also the rhgb and quite omissions...) these files and reboot: - /etc/default/grub GRUB_CMDLINE_LINUX='crashkernel=auto resume=/dev/mapper/onn-swap rd.lvm.lv=onn/ovirt-node-ng-4.4.0-0.20200521.0+1 rd.lvm.lv=onn/swap intel_pstate=disable' - /boot/grub2/grub.cfg set default_kernelopts="root=UUID=85212719-8feb-43aa-9819-2820d4672795 ro crashkernel=auto ipv6.disable=1 intel_pstate=disable " - /boot/loader/entries/ovirt-node-ng-4.4.0-0.20200521.0+1-4.18.0-147.8.1.el8_1.x86_64.conf options intel_pstate=disable boot=UUID=b717ab4f-ca71-469a-8836-ff92cebc7650 crashkernel=auto rd.lvm.lv=onn/swap root=/dev/onn/ovirt-node-ng-4.4.0-0.20200521.0+1 resume=/dev/mapper/onn-swap rootflags=discard rd.lvm.lv=onn/ovirt-node-ng-4.4.0-0.20200521.0+1 img.bootid=ovirt-node-ng-4.4.0-0.20200521.0+1 null - /boot/efi/EFI/centos/grub.cfg set default_kernelopts="root=/dev/mapper/onn-root ro crashkernel=auto resume=/dev/mapper/onn-swap rd.lvm.lv=onn/root rd.lvm.lv=onn/swap intel_pstate=disable " And now with the default/old scaling driver all is quite silent and still working ok for my needs, with web admin quite usable. I updated my two VMs as described above after cpompleting these changes. Right now for example I have hosted engine running + slackware one + CentOS 8 one with [root@ovirt01 ~]# cat /proc/cpuinfo | grep Hz model name : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz cpu MHz : 648.431 model name : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz cpu MHz : 628.307 model name : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz cpu MHz : 648.859 model name : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz cpu MHz : 663.792 [root@ovirt01 ~]# and [root@ovirt01 ~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor powersave powersave powersave powersave [root@ovirt01 g.cecchi]# Thanks to all that helped throughout ... Cheers, Gianluca

2 2

oVirt 4.3 and cinderlib integration (for ceph) on CentOS 7 - centos-release-openstack-pike
by Mathias Schwenke 08 Jun '20

08 Jun '20

At https://www.ovirt.org/develop/release-management/features/storage/cinderlib… ist described the cinderlib integration into oVirt: Installation: - install centos-release-openstack-pike on engine and all hosts - install openstack-cinder and python-pip on engine - pip install cinderlib on engine - install python2-os-brick on all hosts - install ceph-common on engine and on all hosts Which software versions do you use on CentOS 7 whith oVirt 4.3.10? The package centos-release-openstack-pike, as described at the above-mentioned Managed Block Storage feature page, doesn't exist anymore in the CentOS repositories, so I have to switch to centos-release-openstack-queens or newer (rocky, stein, train). So I get (for using with ceph luminous 12): - openstack-cinder 12.0.10 - cinderlib 1.0.1 - ceph-common 12.2.11 - python2-os-brick 2.3.9

2 5

migration
by eevans＠digitaldatatechs.com 08 Jun '20

08 Jun '20

I am running Ovirt 4.310. When I update the engine server it updates the user extensions to ovirt-engine-ui-extensions.noarch 0:1.0.13-1.20200303git3b594b8.el7 and migration fails. I have to downgrade to ovirt-engine-ui-extensions-1.0.10-1.el7.noarch.rpm inorder to get migration to work again. This needs to be passed on to the developers to correct the updated version. Also, I had to download ovirt-engine-ui-extensions-1.0.10-1.el7.noarch.rpm and run yum downgrade ovirt-engine-ui-extensions-1.0.10-1.el7.noarch.rpm for the downgrade to complete successfully. After the downgrade, migration works.

3 2

Ovirt 4.4, Gluster with multiple disks
by Mustapha Aissat 08 Jun '20

08 Jun '20

Hi all, I have a small question. How to configure gluster to use multiple disks for a volume? [image: image.png] Do I need to configure a RAID or LVM that group all disks or I can specify the disks to use in the GUI? Thank you in advance. Best regards, Mustapha AISSAT.

1 0

clean of .shard files if changing volume settings
by Gianluca Cecchi 08 Jun '20

08 Jun '20

Hello, I have a single host in 4.4 with HCI and Gluster. I have only one brick for the volume and I disabled sharding: [root@ovirt01 /root]# gluster volume set data features.shard off volume set: success [root@ovirt01 /root]# In events of web admin I see it registered and updating db: Detected change in value of option features.shard from on to off on volume data of cluster Default, and updated it to engine DB. 6/3/206:46:52 PM Then I delete a VM with a 65Gb disk, that I created while sharding was enabled (I enabled the check box to remove disks) but it seems that files under .shard are not removed. [root@ovirt01 ~]# du -sh /rhev/data-center/mnt/glusterSD/ovirt01st.lutwyn.storage\:_data/.shard/ 62G /rhev/data-center/mnt/glusterSD/ovirt01st.lutwyn.storage:_data/.shard/ [root@ovirt01 ~]# Is there any special command I have to run? Or can I simply remove the .shard directory now? I only had that VM in that storage domain before disabling sharding. The files are all of type: -rw-rw----. 1 root root 67100672 Jun 3 18:18 23f0c94c-cf2a-42c1-8e2e-a21c4e542774.1 -rw-rw----. 1 root root 67108864 Jun 3 18:18 23f0c94c-cf2a-42c1-8e2e-a21c4e542774.2 ... -rw-rw----. 1 root root 67108864 Jun 3 18:44 23f0c94c-cf2a-42c1-8e2e-a21c4e542774.1008 -rw-rw----. 1 root root 39845888 Jun 3 18:44 23f0c94c-cf2a-42c1-8e2e-a21c4e542774.1009 -rw-rw----. 1 root root 56643584 Jun 3 18:44 23f0c94c-cf2a-42c1-8e2e-a21c4e542774.1031 Thanks in advance, Gianluca

2 2

Re: Slow disk upload via WebGUI
by Strahil Nikolov 06 Jun '20

06 Jun '20

There is also the API and I think there was a python script for ISO upload. You can also import from OVA. As you have multiple VMDKs, why don't you just upload in parallel (20-30 disk in batch). Best Regards, Strahil Nikolov На 6 юни 2020 г. 13:39:44 GMT+03:00, Magnus Isaksson <magnus(a)vmar.se> написа: >Hi > >From what i can tell from that link is that there is only one way for >my scenario, or have i missed something? > >"Procedure 11.8. Uploading a Disk Image to a Storage Domain" > >//Magnus >________________________________ >From: Strahil Nikolov <hunter86_bg(a)yahoo.com> >Sent: 06 June 2020 12:26 >To: users(a)ovirt.org <users(a)ovirt.org>; Magnus Isaksson <magnus(a)vmar.se> >Subject: Re: [ovirt-users] Re: Slow disk upload via WebGUI > >Hi Magnus, > > >there are several ways to upload a disk. > >For details, check >https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/ht… > >Best Regards, >Strahil Nikolov > >На 6 юни 2020 г. 12:15:36 GMT+03:00, Magnus Isaksson <magnus(a)vmar.se> >написа: >>A note to this is that we are migrating a couple of customers from a >>vmware enviroment that we have no control over, we get the vmdk files >>on a NFS share. its a bit over 130 VM:s and if every disk will go at >>100mbit/s its quite a painful process. >> >>Is there a faster way to import these disk images other then via >>WebGUI? (of course after convert) >> >>//Magnus >>________________________________ >>From: Magnus Isaksson <magnus(a)vmar.se> >>Sent: 06 June 2020 10:58 >>To: users <users(a)ovirt.org> >>Subject: [ovirt-users] Slow disk upload via WebGUI >> >>Hello >> >>I'm running Engine 4.3.9 and have fibre channel SSD storage and 4 >>nodes. >> >>When uploading disk images i get around 100mbit/s per disk, if im >>running 3 uploads at the same time i get about 300mbit/s combined. >>Everything is connected via 10G and 16G to FC storage. >> >>Why is it so slow? and what can i do to speed things up? >> >>Regards >> Magnus

1 0

Re: Slow disk upload via WebGUI
by Strahil Nikolov 06 Jun '20

06 Jun '20

Hi Magnus, there are several ways to upload a disk. For details, check https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/ht… Best Regards, Strahil Nikolov На 6 юни 2020 г. 12:15:36 GMT+03:00, Magnus Isaksson <magnus(a)vmar.se> написа: >A note to this is that we are migrating a couple of customers from a >vmware enviroment that we have no control over, we get the vmdk files >on a NFS share. its a bit over 130 VM:s and if every disk will go at >100mbit/s its quite a painful process. > >Is there a faster way to import these disk images other then via >WebGUI? (of course after convert) > >//Magnus >________________________________ >From: Magnus Isaksson <magnus(a)vmar.se> >Sent: 06 June 2020 10:58 >To: users <users(a)ovirt.org> >Subject: [ovirt-users] Slow disk upload via WebGUI > >Hello > >I'm running Engine 4.3.9 and have fibre channel SSD storage and 4 >nodes. > >When uploading disk images i get around 100mbit/s per disk, if im >running 3 uploads at the same time i get about 300mbit/s combined. >Everything is connected via 10G and 16G to FC storage. > >Why is it so slow? and what can i do to speed things up? > >Regards > Magnus

2 1

Re: Slow disk upload via WebGUI
by Magnus Isaksson 06 Jun '20

06 Jun '20

A note to this is that we are migrating a couple of customers from a vmware enviroment that we have no control over, we get the vmdk files on a NFS share. its a bit over 130 VM:s and if every disk will go at 100mbit/s its quite a painful process. Is there a faster way to import these disk images other then via WebGUI? (of course after convert) //Magnus ________________________________ From: Magnus Isaksson <magnus(a)vmar.se> Sent: 06 June 2020 10:58 To: users <users(a)ovirt.org> Subject: [ovirt-users] Slow disk upload via WebGUI Hello I'm running Engine 4.3.9 and have fibre channel SSD storage and 4 nodes. When uploading disk images i get around 100mbit/s per disk, if im running 3 uploads at the same time i get about 300mbit/s combined. Everything is connected via 10G and 16G to FC storage. Why is it so slow? and what can i do to speed things up? Regards Magnus

1 0

Slow disk upload via WebGUI
by Magnus Isaksson 06 Jun '20

06 Jun '20

Hello I'm running Engine 4.3.9 and have fibre channel SSD storage and 4 nodes. When uploading disk images i get around 100mbit/s per disk, if im running 3 uploads at the same time i get about 300mbit/s combined. Everything is connected via 10G and 16G to FC storage. Why is it so slow? and what can i do to speed things up? Regards Magnus

1 0