- Users - oVirt List Archives

import OVA failed
by du_hongyu＠yeah.net 06 Jul '18

06 Jul '18

Hi my ovirt-engine version is 4.2.1, I import OVA by web UI, face some error, can you give me some advise? Regards Hongyu Du

2 1

ovirt, postfix and sendmail
by Fabrice Bacchella 06 Jul '18

06 Jul '18

ovirt in version 4.2 choose to incorporate postfix as a mandatory MTA: yum erase postfix ... Removing: postfix x86_64 2:2.10.1-6.el7 @base 12 M Removing for dependencies: cockpit-ovirt-dashboard noarch 0.11.28-1.el7 @ovirt-4.2 15 M ovirt-host x86_64 4.2.3-1.el7 @ovirt-4.2 11 k ovirt-hosted-engine-setup noarch 2.2.22.1-1.el7 @ovirt-4.2 2.2 M Is there a way to change that ? It's not about postfix being inferior or superior to other solutions. It's that it didn't ask any thing, didn't check if one was already installed. It's just installed. For example: rpm -q --provides postfix MTA config(postfix) = 2:2.10.1-6.el7 postfix = 2:2.10.1-6.el7 postfix(x86-64) = 2:2.10.1-6.el7 server(smtp) smtpd smtpdaemon rpm -q --provides sendmail MTA config(sendmail) = 8.14.7-5.el7 sendmail = 8.14.7-5.el7 sendmail(x86-64) = 8.14.7-5.el7 server(smtp) smtpdaemon There is a lot of other dependencies to declare other than postfix, MTA would have been better.

3 8

Ovirt Networking Setup Questions
by Dave Mintz 06 Jul '18

06 Jul '18

Hello, I am trying to understand, by reading all available docs, how to correctly set up networking. What I have: 6 nodes, 1 engine - all have 3 nics. What I want: To separate traffic into three zones - ovirtmgmt, prod (for vm and admin web interface, data (for db access). So, I have three subnets - 10.10.10.0, 10.10.20.0, and 10.10.30.0 - with matching VLANs 10, 20, 30 I am trying to understand how bonding and bridging work. Should I bond all three nics together? The instructions here: https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/ <https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/> seem to do that and then create two bridges br0 and ovirtmgmt, which they then assign ip addresses to. I can do that, but shouldn’t I be configuring all of the networking at the logical network level? So, in that case, should I just create one bond/bridge and then do all of the networking at the logical level? Sorry if this is newbie stuff. Thanks Dave

1 0

Snapshots don't seem to work with Windows VMs
by jmp242＠cornell.edu 06 Jul '18

06 Jul '18

I've been testing with Windows 10 1607 LTSB and created several snapshots. I can preview each one, but they all boot with the same configuration and software installed and files as the "active VM" - so I cannot see at all how to roll back changes. Is this a known issue? I believe I'm following the documentation properly, but I can't see that the snapshots are doing anything. I'm testing on Scientific Linux 7.4 using oVirt 4.2.2.6-1.el7.centos.

2 1

oVirt LLDP Labeler
by Ales Musil 06 Jul '18

06 Jul '18

Hello, I would like to announce that oVirt LLDP Labeler is officially available. The Labeler is service that runs along with engine and is capable of labeling host network interfaces according to their reported VLANs via LLDP. The attached labels are named "lldp_vlan_${VLAN}", where ${VLAN} is ID of the corresponding VLAN. This can make work of an administrator easier, because any network with the same label, will be automatically attached to the corresponding host interface. The Labeler is currently tested only with Juniper switches which are capable of reporting all of their VLANs that are present on the interface. We would like to extend the Labeler with auto bonding feature. Those interfaces that are detected on the same switch would be automatically bonded. The Labeler source is available here: https://github.com/almusil/ovirt-lldp-labeler And the build: https://copr.fedorainfracloud.org/coprs/amusil/ovirt-lldp-labeler/ If you have any suggestions or problems please don't hesitate to report them on the GitHub page. -- ALES MUSIL Associate software engineer - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

3 3

GlusterFS 4.1
by Chris Boot 06 Jul '18

06 Jul '18

All, Now that GlusterFS 4.1 LTS has been released, and is the "default" version of GlusterFS in CentOS (you get this from "centos-release-gluster" now), what's the status with regards to oVirt? How badly is oVirt 4.2.4 likely to break if one were to upgrade the gluster* packages to 4.1? Thanks, Chris -- Chris Boot bootc(a)boo.tc

2 1

Performing a quickstart task in the new console
by Dave Thacker 06 Jul '18

06 Jul '18

Hello list, I'm using the quick start documentation to build a lab setup. Immediately after the task "Configure Networks", there is a task "Attach oVirt Node or Enterprise Linux Host" I haven't found a spot in the new GUI that matches the navigation tree in the manual. How would I navigate to that task? Thanks. -- Dave Thacker

2 1

Progetto di virtualizzazione ....vorremmo utilizzare oVirt
by Marco Tosato 06 Jul '18

06 Jul '18

Buongiorno a tutti! La mia azienda sta intraprendendo un nuovo progetto che richiede un cluster di virtualizzazione di medie dimensioni (6 nodi), vorremmo valutare oVirt e GlusterFS come soluzione e stiamo cercando un partner (azienda o professionista) che abbia già esperienza con questo software e che possa fornirci i seguenti servizi: * Installazione e messa in produzione del sistema * Risoluzione di eventuali problemi che si possano verificare in futuro * formazione e approfondimento su oVirt/GlusterFS Grazie a tutti! Marco Tosato Ricerca e Sviluppo ________________________________ [Esapro]<http://www.esapro.it/> Esapro Srl Sede Legale Largo G. Donegani 2 20121 Milano (MI) REA CCIAA MI 2515336 P.I./C.F. 03836010409 Cap. Sociale Euro 111.111,00 i.v. Sede Amministrativa Via Cappello 12/a 35010 San Pietro in Gu (PD) T: +39 049 9490075 F: +39 049 5960992 www.esapro.it<http://www.esapro.it/> - info(a)esapro.it<mailto:info@esapro.it> [CSQ IQNet - UNI EN ISO 9001:2015] Ai sensi del D. Lgs. 196/2003 e successive modificazioni ed integrazioni si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario. Sono vietati la riproduzione e l'uso di questa e-mail in mancanza di autorizzazione del mittente. Se avete ricevuto questa e-mail per errore, vi invitiamo ad eliminarla senza copiarla e a non inoltrarla a terzi, dandocene gentilmente comunicazione. Grazie per la collaborazione / This message, for the D. Lgs n. 196/2003 (Privacy Code), may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

3 2

ovirt-node: freshly installed node: network interfaces not visible
by etienne.charlier＠reduspaceservices.eu 06 Jul '18

06 Jul '18

Hello, I'm deploying a test cluster to get used to the ovirt product. My ovirt ( 4.2.2) engine is deployed in a vmware virtual machine. I'm busy deploying 5 hosts using the ovirt-node iso. I have issue with the additional physical network interface ( used for vm trafic and iSCSI) In ovirt manager I can't see the physical network interfaces. It's thus not possible to assign logical network to physical interfaces and my hosts stays in "non operational" status. How should I configure the additional interfaces in the ovirt-node installer to have them recognized ? I somehow managed to configure one host and I can see a comment line in /etc/sysconfig/network-script/ifcfg-... saying vdsm has acquired the interface.... No Such line in the ifcfg-* file in non operational hosts.... Any idea ? Etienne

3 4

ENGINE_SSO_AUTH_URL configuration
by Hari Prasanth Loganathan 05 Jul '18

05 Jul '18

Hi Team, I want oVirt to point to my Authentication / Authorization HTTP URL, so I modified the following property in */etc/ovirt-engine/engine.conf.d/11-setup-sso.conf* #ENGINE_SSO_AUTH_URL="https://${ENGINE_FQDN}:443/ovirt-engine/sso" ENGINE_SSO_AUTH_URL="http://172.30.39.176:9090/api/auth/sso" #SSO_ENGINE_URL="https://${ENGINE_FQDN}:443/ovirt-engine/" SSO_ENGINE_URL="http://172.30.39.176:9090/api/auth/" I verified in the log and found the following message : engine.log:2018-07-04 15:12:46,238+05 INFO [org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool -- 42) [] Value of property 'ENGINE_SSO_AUTH_URL' is ' http://172.30.39.176:9090/api/auth/sso'. engine.log:2018-07-04 15:12:46,244+05 INFO [org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool -- 42) [] Value of property 'SSO_ENGINE_URL' is ' http://172.30.39.176:9090/api/auth/'. But still it is not point to my Authentication URL, Is there any other change we need to make to point the oVirt Authentication to my HTTP URL? Thanks, Hari

3 6