- Users - oVirt List Archives

Re: Power management and storage domains error when running Ansible tasks!
by Strahil 05 Jan '20

05 Jan '20

You need to speciify the method to be used for power fencing - that could be HPE's iLO, Dell's iDRAC, APC UPS or something else. Best Regards, Strahil NikolovOn Jan 5, 2020 14:13, m.skrzetuski(a)gmail.com wrote: > > I don't feel comfortable uploading the whole file with all the information inside it. > I can see the following entries around power management. > > 2020-01-05 12:58:18,031+01 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-3) [26be9219] EVENT_ID: VDS_HOST_NOT_RESPONDING(9,027), Host <myhost> is not responding. Host cannot be fenced automatically because power management for the host is disabled. > [...] > 2020-01-05 12:58:24,435+01 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-25) [cff01c0] EVENT_ID: VDS_ALERT_FENCE_IS_NOT_CONFIGURED(9,000), Failed to verify Power Management configuration for Host <myhost>. > > When (in the web UI) I try to activate power management for the host I get an error: Cannot edit Host. Power Management is enabled for Host but no Agent type selected. > > Which agent is the error talking about? Do I have to run an agent somewhere? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7A5KBUZALRXP7…

2 1

Re: Cluster CPU type update
by Eli Mesika 05 Jan '20

05 Jan '20

This is the right way to do that IMO On Sat, Jan 4, 2020 at 3:09 AM Morris, Roy <roy.morris(a)ventura.org> wrote: > Hello, > > I'm running a 4.3 cluster with 56 VMs all set to default cluster and the > cluster itself is set to Intel Westmere Family. I am getting a new server > and retiring 3 old ones which brings me to my question. > > When implementing the new host into the cluster and retiring the older > hosts. I want to change the CPU type setting in the cluster default to > Broadwell which is what my new 3 host cluster will be. To make this change, > I assume the process would be to turn off all VMs, set cluster cpu type to > broadwell, then turn on VMs to get the new CPU flags? > > Just wanted to reach out and see if someone else has had to go through > this before and has any notes/tips. > > Best regards, > > Roy > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/FKFGEOW5OI6A2… >

1 0

Re: Cluster CPU type update
by Mathieu Simon 04 Jan '20

04 Jan '20

Hi Roy > To make this change, I assume the process would be to turn off all VMs, set cluster cpu type to broadwell, then turn on VMs to get the new CPU flags? Exactly, you can only reliably change the CPU type for a cluster once the last Westmere-based host is gone. That's what I had to do when I when we upgraded CPU microcode on clusters to enable the various CPU mitigations within the guests. After changing the CPU type at the cluster level, you should see an orange triangle shown with each VM in the Web UI indicating what VM needs a restart in order to pick up the change. Because of those various updates to CPU microcodes, check your current BIOS/UEFI (though microcode is part of CentOS/RHEL) then check the CPU Type in the tab of each Broadwell-based host. As of writing, ideally set "Intel Broadwell IBRS SSBD MDS" (or the -noTSX) variant. Regards Mathieu

1 0

Cluster CPU type update
by Morris, Roy 03 Jan '20

03 Jan '20

Hello, I'm running a 4.3 cluster with 56 VMs all set to default cluster and the cluster itself is set to Intel Westmere Family. I am getting a new server and retiring 3 old ones which brings me to my question. When implementing the new host into the cluster and retiring the older hosts. I want to change the CPU type setting in the cluster default to Broadwell which is what my new 3 host cluster will be. To make this change, I assume the process would be to turn off all VMs, set cluster cpu type to broadwell, then turn on VMs to get the new CPU flags? Just wanted to reach out and see if someone else has had to go through this before and has any notes/tips. Best regards, Roy

1 0

Can't add host with "Certificate enrollment failed". Any ideas?
by m.skrzetuski＠gmail.com 03 Jan '20

03 Jan '20

Hello everyone, I am trying to add a new host with the "ovirt.infra" role and use the following Ansible snippet for it. hosts: - name: delirium address: delirium.home cluster: Matrix public_key: true power_management_enabled: true I am getting the following error. msg: 'Error message: [''Host delirium installation failed. Certificate enrollment failed.'', ''An error has occurred during installation of Host delirium: Certificate enrollment failed.'']' Any ideas? The error does not say what exactly is wrong. The following are my SSL certs. [skrzetuski@delirium ~]$ sudo ls -lR /etc/pki/ovirt-engine/ /etc/pki/ovirt-engine/: total 68 lrwxrwxrwx. 1 root root 28 Jan 2 23:51 apache-ca.pem -> /etc/pki/ovirt-engine/ca.pem -rw-r--r--. 1 root root 384 Jan 2 23:51 cacert.conf -rw-r--r--. 1 root root 384 Jan 2 23:51 cacert.template -rw-r--r--. 1 root root 384 Nov 12 14:16 cacert.template.in -rw-r--r--. 1 root root 1647 Jan 3 01:12 ca.pem -rw-r--r--. 1 root root 1444 Jan 2 23:51 cert.conf drwxr-xr-x. 2 ovirt ovirt 4096 Jan 2 23:52 certs -rw-r--r--. 1 root root 1444 Jan 2 23:51 cert.template -rw-r--r--. 1 root root 1156 Nov 12 14:16 cert.template.in -rw-r--r--. 1 ovirt ovirt 800 Jan 2 23:52 database.txt -rw-r--r--. 1 ovirt ovirt 20 Jan 2 23:52 database.txt.attr -rw-r--r--. 1 ovirt ovirt 20 Jan 2 23:52 database.txt.attr.old -rw-r--r--. 1 ovirt ovirt 733 Jan 2 23:52 database.txt.old drwxr-xr-x. 2 root root 4096 Jan 2 23:52 keys -rw-r--r--. 1 root root 550 Nov 12 14:16 openssl.conf drwxr-x---. 2 ovirt ovirt 20 Jan 2 23:51 private drwxr-xr-x. 2 ovirt ovirt 4096 Jan 3 12:22 requests -rw-r--r--. 1 ovirt ovirt 5 Jan 2 23:52 serial.txt -rw-r--r--. 1 ovirt ovirt 5 Jan 2 23:52 serial.txt.old /etc/pki/ovirt-engine/certs: total 244 -rw-r--r--. 1 root root 1310 Jan 2 23:51 1000.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1001.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1002.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1003.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1004.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1005.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1006.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1007.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1008.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1009.pem -rw-r--r--. 1 root root 4925 Jan 2 23:52 100A.pem -rw-r--r--. 1 root root 5011 Jan 2 23:52 100B.pem -rw-r--r--. 1 root root 5011 Jan 2 23:52 100C.pem -rw-r--r--. 1 root root 1968 Jan 3 01:12 apache.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 apache.cer.20200102235148 -rw-r--r--. 1 root root 1310 Jan 2 23:51 ca.der -rw-r--r--. 1 root root 5109 Jan 2 23:51 engine.cer -rw-r--r--. 1 root root 1727 Jan 2 23:51 imageio-proxy.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 imageio-proxy.cer.20200102235148 -rw-r--r--. 1 root root 5109 Jan 2 23:51 jboss.cer -rw-r--r--. 1 root root 1727 Jan 2 23:51 ovirt-provider-ovn.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 ovirt-provider-ovn.cer.20200102235149 -rw-r--r--. 1 root root 1727 Jan 2 23:51 ovn-ndb.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 ovn-ndb.cer.20200102235148 -rw-r--r--. 1 root root 1727 Jan 2 23:51 ovn-sdb.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 ovn-sdb.cer.20200102235149 -rw-r--r--. 1 root root 1727 Jan 2 23:51 reports.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 reports.cer.20200102235148 -rw-r--r--. 1 root root 4925 Jan 2 23:52 vmconsole-proxy-helper.cer -rw-r--r--. 1 root root 5011 Jan 2 23:52 vmconsole-proxy-host.cer -rw-r--r--. 1 root root 1391 Jan 2 23:52 vmconsole-proxy-host-cert.pub -rw-r--r--. 1 root root 381 Jan 2 23:52 vmconsole-proxy-host.pub -rw-r--r--. 1 root root 5011 Jan 2 23:52 vmconsole-proxy-user.cer -rw-r--r--. 1 root root 1423 Jan 2 23:52 vmconsole-proxy-user-cert.pub -rw-r--r--. 1 root root 381 Jan 2 23:52 vmconsole-proxy-user.pub -rw-r--r--. 1 root root 1727 Jan 2 23:51 websocket-proxy.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 websocket-proxy.cer.20200102235148 /etc/pki/ovirt-engine/keys: total 84 -rw-r-----. 1 root ovirt 1675 Jan 3 01:12 apache.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 apache.p12 -rw-------. 1 ovirt ovirt 1828 Jan 2 23:51 engine_id_rsa -rw-------. 1 ovirt root 2709 Jan 2 23:51 engine.p12 -rw-------. 1 root root 1828 Jan 2 23:51 imageio-proxy.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 imageio-proxy.p12 -rw-------. 1 ovirt root 2709 Jan 2 23:51 jboss.p12 -rw-------. 1 root root 1828 Jan 2 23:51 ovirt-provider-ovn.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 ovirt-provider-ovn.p12 -rw-------. 1 root root 1828 Jan 2 23:51 ovn-ndb.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 ovn-ndb.p12 -rw-------. 1 root root 1832 Jan 2 23:51 ovn-sdb.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 ovn-sdb.p12 -rw-------. 1 root root 1828 Jan 2 23:51 reports.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 reports.p12 -rw-------. 1 ovirt-vmconsole ovirt-vmconsole 1832 Jan 2 23:52 vmconsole-proxy-helper.key.nopass -rw-------. 1 root root 2677 Jan 2 23:52 vmconsole-proxy-helper.p12 -rw-------. 1 root root 2693 Jan 2 23:52 vmconsole-proxy-host.p12 -rw-------. 1 root root 2693 Jan 2 23:52 vmconsole-proxy-user.p12 -rw-------. 1 ovirt ovirt 1828 Jan 2 23:51 websocket-proxy.key.nopass -rw-------. 1 ovirt root 2709 Jan 2 23:51 websocket-proxy.p12 /etc/pki/ovirt-engine/private: total 4 -rw-r-----. 1 ovirt ovirt 1675 Jan 2 23:51 ca.pem /etc/pki/ovirt-engine/requests: total 64 -rw-r--r--. 1 ovirt ovirt 862 Jan 3 12:04 192.168.1.5.req -rw-r--r--. 1 root root 863 Jan 2 23:51 apache.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ca.csr -rw-r--r--. 1 root root 863 Jan 2 23:51 engine.req -rw-r--r--. 1 root root 863 Jan 2 23:51 imageio-proxy.req -rw-r--r--. 1 root root 863 Jan 2 23:51 jboss.req -rw-r--r--. 1 ovirt ovirt 862 Jan 3 12:11 delirium.home.req -rw-r--r--. 1 ovirt ovirt 862 Jan 3 12:22 delirium.mysecretdomain.ch.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ovirt-provider-ovn.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ovn-ndb.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ovn-sdb.req -rw-r--r--. 1 root root 863 Jan 2 23:51 reports.req -rw-r--r--. 1 root root 863 Jan 2 23:52 vmconsole-proxy-helper.req -rw-r--r--. 1 root root 863 Jan 2 23:52 vmconsole-proxy-host.req -rw-r--r--. 1 root root 863 Jan 2 23:52 vmconsole-proxy-user.req -rw-r--r--. 1 root root 863 Jan 2 23:51 websocket-proxy.req Kind regards skrzetuski

1 1

2 node redundant cluster without hyperconverged
by gokerdalar＠gmail.com 03 Jan '20

03 Jan '20

Hello, I want to get an idea in this topic. I have two servers with the same capabilities and 8 same physical disc per node. I want to setup a cluster using a redundant disc.I dont have another server for gluster hyperconverged . How i should build for this structure ? Thanks in advance, Göker

1 0

Re: Confusion about storage domain ISO. How do I provision VMs?
by Strahil 02 Jan '20

02 Jan '20

On Jan 2, 2020 23:34, m.skrzetuski(a)gmail.com wrote: > > Hello there, > > I'm a bit confused about provisioning VMs (with Ansible). > > At first I wanted to setup a VM manually over the web UI, just to see how it works. > I was not able to upload ISO files with cloud images to a data domain but I was able to upload to ISO domain. However I read that ISO domains are deprecated (see https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht…) You should be able to import any ISO to data domains... What is the error you get ? > So what is the workflow/process of provisioning VMs from cloud images with cloud init? Where do I store my ISOs? In Storage -> Storage Domains -> Ovirt-Image-repository there are a lot of cloud images that can be imported and later used (I have neverr done that so far). So far, I'm using the ISO domain as it was in active isse when I setup my lab. > Kind regards > skrzetuski Best Regards, Strahil Nikolov

1 0

Re: 4.2.8 to 4.3.7 > Management slow
by Strahil 02 Jan '20

02 Jan '20

None is when you use multiple queues , which seems to be enabled on my HostedEngine VM by default. In both cases, we shouldn't reorder I/O requests in the VM, just to do the same on the Host. That's why I left queueing to happen only on the host. Best Regards, Strahil NikolovOn Jan 2, 2020 07:54, Guillaume Pavese <guillaume.pavese(a)interactiv-group.com> wrote: > > Hi, > > I use something similar > However, I think that the correct scheduler in case of virtio-scsi devices (sd*) should be "noop" instead of "none" > > Best, > > > Guillaume Pavese > Ingénieur Système et Réseau > Interactiv-Group > > > On Tue, Dec 31, 2019 at 9:27 PM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> You can manually change the I/O scheduler of the disks and if that works better for you, put a rule in udev. >> >> Here is mine: >> >> [root@engine rules.d]# cat /etc/udev/rules.d/90-default-io-scheduler.rules >> ACTION=="add|change", KERNEL=="sd*[!0-9]", ATTR{queue/scheduler}="none" >> ACTION=="add|change", KERNEL=="vd*[!0-9]", ATTR{queue/scheduler}="none" >> >> [root@engine rules.d]# cat /sys/block/vda/queue/scheduler >> [none] mq-deadline kyber >> >> Best Regards, >> Strahil Nikolov >> >> On Dec 31, 2019 12:30, Demeter Tibor <tdemeter(a)itsmart.hu> wrote: >>> >>> Dear Users, >>> >>> I've successfully upgraded my 4 node hyperconverged system from 4.2.8 to 4.3.7. >>> After upgrade everything seems to working fine, but the whole management system seems very slow. >>> Spends many seconds when I clicking on "virtual machines" or I want to edit a virtual machines. >>> The speed of vms and the IO is fine. >>> >>> It is running on a glusterfs (distributed replicate, on 3 node, 9 bricks). There are no errors, everything fine. but terrible slow:( >>> The engine vm has 0.2-0.3 load. >>> >>> What can I do? >>> >>> Thanks in advance and I wish Happy New Year! >>> >>> Regards, >>> Tibor >>> >>> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EYHGQ6JVLHDJI… > > > Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité

1 0

I am interested in using oVirt for my homelab but is it dead?
by m.skrzetuski＠gmail.com 02 Jan '20

02 Jan '20

Hi there, I'm a huge Ansible fan and work a lot with OpenStack and OpenShift. At home I purchased an Intel NUC to host some services for my home(-lab). I was reading about oVirt and it sounded promising, I saw all the Ansible roles. I installed ovirt on CentOS 8 (and used the Ansible roles from the Galaxy) and hit few strange walls like the standard SSL cert not being accepted by Google Chrome on Mac OSX with error "revoked". Additionally the community seems so small compared to others (like Proxmox). So I guess what I wanted to ask is: Is it dead? What's the future of oVirt? Is Redhat investing in the project? Kind regards skrzetuski

3 5

ovirt 4.3.7 + Gluster in hyperconverged (production design)
by adrianquintero＠gmail.com 02 Jan '20

02 Jan '20

Hi, After playing a bit with oVirt and Gluster in our pre-production environment for the last year, we have decided to move forward with a our production design using ovirt 4.3.7 + Gluster in a hyperconverged setup. For this we are looking get answers to a few questions that will help out with our design and eventually lead to our production deployment phase: Current HW specs (total servers = 18): 1.- Server type: DL380 GEN 9 2.- Memory: 256GB 3.-Disk QTY per hypervisor: - 2x600GB SAS (RAID 0) for the OS - 9x1.2TB SSD (RAID[0, 6..]..? ) for GLUSTER. 4.-Network: - Bond1: 2x10Gbps - Bond2: 2x10Gbps (for migration and gluster) Our plan is to build 2x9 node clusters, however the following questions come up: 1.-Should we build 2 separate environments each with its own engine? or should we do 1 engine that will manage both clusters? 2.-What would be the best gluster volume layout for #1 above with regards to RAID configuration: - JBOD or RAID6 or…?. - what is the benefit or downside of using JBOD vs RAID 6 for this particular scenario? 3.-Would you recommend Ansible-based deployment (if supported)? If yes where would I find the documentation for it? or should we just deploy using the UI?. - I have reviewed the following and in Chapter 5 it only mentions Web UI https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infras… - Also looked at https://github.com/gluster/gluster-ansible/tree/master/playbooks/hc-ansible… but could not get it to work properly. 4.-what is the recommended max server qty in a hyperconverged setup with gluster, 12, 15, 18...? Thanks, Adrian

3 2