Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread nicola.gentile.to

Il 03/08/2016 14:04, Yedidyah Bar David ha scritto:
On Wed, Aug 3, 2016 at 2:51 PM, nicola.gentile.to 
 > wrote:


Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:

On Wed, Aug 3, 2016 at 2:30 PM,nicola.gentile.to 
   wrote:

Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:

Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:

After install you have to make a dependency so that VDSM Broker starts after
NFS Server

In /usr/lib/systemd/system/ovirt-ha-broker.service

Added in section  [Unit] the line:

After=nfs-server.service

Also, for vdsmd service, in file vdsmd.service changed from:

After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service

to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service \
   nfs-server.service

NOTE: the files will be overwritten by future updates, so you have to keep
in mind...

Hi,

I try to upgrade from ovirt 3.6.7 to 4.0.1.

I follow this steps:

1. Update repository for 4.0.1

2. Disable old repository 3.6.7

3. run: yum update "ovirt-engine-setup*"

now an error occured:

yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
  * base:artfiles.org 
  * extras:ba.mirror.garr.it 
  * ovirt-4.0:ftp.nluug.nl 
  * ovirt-4.0-epel:epel.besthosting.ua 
  * updates:ba.mirror.garr.it 
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread Yedidyah Bar David
On Wed, Aug 3, 2016 at 2:51 PM, nicola.gentile.to <
nicola.gentile...@gmail.com> wrote:

> Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:
>
> On Wed, Aug 3, 2016 at 2:30 PM, 
> nicola.gentile.to  
> wrote:
>
> Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
>
> Two final steps I've done that are only necessary in my environment, where
> the host itslef is providing the NFS service for storage domains:
>
> After install you have to make a dependency so that VDSM Broker starts after
> NFS Server
>
> In /usr/lib/systemd/system/ovirt-ha-broker.service
>
> Added in section  [Unit] the line:
>
> After=nfs-server.service
>
> Also, for vdsmd service, in file vdsmd.service changed from:
>
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service
>
> to:
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service \
>   nfs-server.service
>
> NOTE: the files will be overwritten by future updates, so you have to keep
> in mind...
>
> Hi,
>
> I try to upgrade from ovirt 3.6.7 to 4.0.1.
>
> I follow this steps:
>
> 1. Update repository for 4.0.1
>
> 2. Disable old repository 3.6.7
>
> 3. run: yum update "ovirt-engine-setup*"
>
> now an error occured:
>
> yum update "ovirt-engine-setup*"
> Plugin abilitati:fastestmirror, langpacks, versionlock
> Repository centos-ovirt36 is listed more than once in the configuration
> Repository virtio-win-stable is listed more than once in the configuration
> Loading mirror speeds from cached hostfile
>  * base: artfiles.org
>  * extras: ba.mirror.garr.it
>  * ovirt-4.0: ftp.nluug.nl
>  * ovirt-4.0-epel: epel.besthosting.ua
>  * updates: ba.mirror.garr.it
> Risoluzione dipendenze
> --> Esecuzione del controllo di transazione
> ---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
> per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
> pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> --> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
> ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
> ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> --> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
> otopi-java-1.4.2-1.el7.centos.noarch
> ---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
> per essere un aggiornamento
> ---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> ---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> --> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> va in conflitto con ovirt-engine-reports-setup < 4.0.0
> --> Risoluzione delle dipendenze completata
> Errore: ovirt-engine-setup-base conflicts with
> ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
>  Si può 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread nicola.gentile.to

Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:

On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to
 wrote:

Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:

Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:

After install you have to make a dependency so that VDSM Broker starts after
NFS Server

In /usr/lib/systemd/system/ovirt-ha-broker.service

Added in section  [Unit] the line:

After=nfs-server.service

Also, for vdsmd service, in file vdsmd.service changed from:

After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service

to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service \
   nfs-server.service

NOTE: the files will be overwritten by future updates, so you have to keep
in mind...

Hi,

I try to upgrade from ovirt 3.6.7 to 4.0.1.

I follow this steps:

1. Update repository for 4.0.1

2. Disable old repository 3.6.7

3. run: yum update "ovirt-engine-setup*"

now an error occured:

yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
  * base: artfiles.org
  * extras: ba.mirror.garr.it
  * ovirt-4.0: ftp.nluug.nl
  * ovirt-4.0-epel: epel.besthosting.ua
  * updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
--> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
va in conflitto con ovirt-engine-reports-setup < 4.0.0
--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
  Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread Yedidyah Bar David
On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to
 wrote:
> Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
>
> Two final steps I've done that are only necessary in my environment, where
> the host itslef is providing the NFS service for storage domains:
>
> After install you have to make a dependency so that VDSM Broker starts after
> NFS Server
>
> In /usr/lib/systemd/system/ovirt-ha-broker.service
>
> Added in section  [Unit] the line:
>
> After=nfs-server.service
>
> Also, for vdsmd service, in file vdsmd.service changed from:
>
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service
>
> to:
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service \
>   nfs-server.service
>
> NOTE: the files will be overwritten by future updates, so you have to keep
> in mind...
>
> Hi,
>
> I try to upgrade from ovirt 3.6.7 to 4.0.1.
>
> I follow this steps:
>
> 1. Update repository for 4.0.1
>
> 2. Disable old repository 3.6.7
>
> 3. run: yum update "ovirt-engine-setup*"
>
> now an error occured:
>
> yum update "ovirt-engine-setup*"
> Plugin abilitati:fastestmirror, langpacks, versionlock
> Repository centos-ovirt36 is listed more than once in the configuration
> Repository virtio-win-stable is listed more than once in the configuration
> Loading mirror speeds from cached hostfile
>  * base: artfiles.org
>  * extras: ba.mirror.garr.it
>  * ovirt-4.0: ftp.nluug.nl
>  * ovirt-4.0-epel: epel.besthosting.ua
>  * updates: ba.mirror.garr.it
> Risoluzione dipendenze
> --> Esecuzione del controllo di transazione
> ---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
> per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
> pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> --> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
> ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
> ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> --> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
> otopi-java-1.4.2-1.el7.centos.noarch
> ---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
> per essere un aggiornamento
> ---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> ---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> --> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> va in conflitto con ovirt-engine-reports-setup < 4.0.0
> --> Risoluzione delle dipendenze completata
> Errore: ovirt-engine-setup-base conflicts with
> ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
>  Si può provare ad usare --skip-broken per aggirare il problema
> ** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
> bash-4.2.46-20.el7_2.x86_64 è un duplicato di 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread nicola.gentile.to

Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
Two final steps I've done that are only necessary in my environment, 
where the host itslef is providing the NFS service for storage domains:


After install you have to make a dependency so that VDSM Broker starts 
after NFS Server


In /usr/lib/systemd/system/ovirt-ha-broker.service

Added in section  [Unit] the line:

After=nfs-server.service

Also, for vdsmd service, in file vdsmd.service changed from:

After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
  supervdsmd.service sanlock.service vdsm-network.service

to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
  supervdsmd.service sanlock.service vdsm-network.service \
  nfs-server.service

NOTE: the files will be overwritten by future updates, so you have to 
keep in mind...



Hi,

I try to upgrade from ovirt 3.6.7 to 4.0.1.

I follow this steps:

1. Update repository for 4.0.1

2. Disable old repository 3.6.7

3. run: yum update "ovirt-engine-setup*"

now an error occured:

yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: artfiles.org
 * extras: ba.mirror.garr.it
 * ovirt-4.0: ftp.nluug.nl
 * ovirt-4.0-epel: epel.besthosting.ua
 * updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato 
per essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato 
per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos 
settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos 
settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos 
per il pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto: 
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il 
pacchetto: 
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento

--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere 
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il 
pacchetto: otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un 
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos 
settato per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos 
settato per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato 
per essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato 
per essere un aggiornamento

--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere 
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere 
un aggiornamento
--> Analisi conflitto: 
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch va in conflitto con 
ovirt-engine-reports-setup < 4.0.0

--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with 
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch

 Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di 
1:dbus-libs-1.6.12-13.el7.x86_64
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-05 Thread Gianluca Cecchi
Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:

After install you have to make a dependency so that VDSM Broker starts
after NFS Server

In /usr/lib/systemd/system/ovirt-ha-broker.service

Added in section  [Unit] the line:

After=nfs-server.service

Also, for vdsmd service, in file vdsmd.service changed from:

After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
  supervdsmd.service sanlock.service vdsm-network.service

to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
  supervdsmd.service sanlock.service vdsm-network.service \
  nfs-server.service

NOTE: the files will be overwritten by future updates, so you have to keep
in mind...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-05 Thread Gianluca Cecchi
On Mon, Jul 4, 2016 at 1:56 PM, Arman Khalatyan  wrote:

> about a n hour ago I just tested to setup ovirt 3.6, then upgrade it, 2
> nodes: host and ovirt on separated machines.
> very smoothly upgraded, first engine upgrade then host upgrade.
> The only trouble on hosts is that some pacages are still reffering to
> ovirt-3.6 repository even ovirt-4.0 is there.
> it is simple to fix: yum list installed| grep ovirt-3.6 then removing all
> possible packages
> next reinstall host from GUI.
> Thats it.
>
>
>
>
For the repo part I posted a question for clarification:
http://lists.ovirt.org/pipermail/users/2016-July/040910.html
see there for follow ups

In my case for single host environment with both host and hosted engine
(deployed as appliance) on CentOS 7.2 and storage domains on NFS served by
the host itself, this is the flow I followed to bring a 3.6.5 environment
to 4.0.
Problem still here is inability to upgrade the only existing cluster to 4.0
and then the datacenter to 4.0
Currently not possible due to :
https://bugzilla.redhat.com/show_bug.cgi?id=1351533

To update I kept valid what explained in the thread started here:
http://lists.ovirt.org/pipermail/users/2016-June/040649.html


yum update doesn't propose ovirt 4.0 packages
So I installed ovirt 4.0 repo (as in clean install description) and
disabled 3.6 ones.

yum update "ovirt-engine-setup*"

gives
Dependencies Resolved

===
 PackageArch Version
  Repository   Size
===
Updating:
 ovirt-engine-setup noarch
4.0.0.6-1.el7.centosovirt-4.0   8.6 k
 ovirt-engine-setup-basenoarch
4.0.0.6-1.el7.centosovirt-4.095 k
 ovirt-engine-setup-plugin-ovirt-engine noarch
4.0.0.6-1.el7.centosovirt-4.0   161 k
 ovirt-engine-setup-plugin-ovirt-engine-common  noarch
4.0.0.6-1.el7.centosovirt-4.080 k
 ovirt-engine-setup-plugin-vmconsole-proxy-helper   noarch
4.0.0.6-1.el7.centosovirt-4.027 k
 ovirt-engine-setup-plugin-websocket-proxy  noarch
4.0.0.6-1.el7.centosovirt-4.026 k
Installing for dependencies:
 antlr-tool noarch   2.7.7-30.el7
 base357 k
 apache-commons-collections noarch   3.2.1-22.el7_2
 updates 509 k
 bea-stax   noarch   1.2.0-9.el7
  base176 k
 dom4j  noarch   1.6.1-20.el7
 base277 k
 hsqldb noarch
1:1.8.1.3-13.el7base950 k
 isorelax   noarch
1:0-0.15.release20050331.el7base 75 k
 jaxen  noarch   1.1.3-11.el7
 base204 k
 jdom   noarch   1.1.3-6.el7
  base174 k
 msv-msvnoarch
1:2013.5.1-6.el7base3.7 M
 msv-xsdlib noarch
1:2013.5.1-6.el7base1.1 M
 ovirt-engine-dwh   noarch
4.0.0-2.git38f5db5.el7.centos   ovirt-4.0   2.1 M
 ovirt-engine-dwh-setup noarch
4.0.0-2.git38f5db5.el7.centos   ovirt-4.069 k
 postgresql-jdbcnoarch   9.2.1002-5.el7
 base447 k
 relaxngDatatypenoarch   1.0-11.el7
 base 15 k
 ws-jaxme   noarch   0.5.2-10.el7
 base1.1 M
 xpp3   noarch   1.1.3.8-11.el7
 base336 k
Updating for dependencies:
 otopi  noarch
1.5.0-1.el7.centos  ovirt-4.0   160 k
 otopi-java noarch
1.5.0-1.el7.centos  ovirt-4.025 k
 ovirt-engine-lib   noarch
4.0.0.6-1.el7.centosovirt-4.028 k

Transaction Summary
===
Install ( 16 Dependent packages)
Upgrade  6 Packages (+ 3 Dependent packages)

engine-setup brings in the DWH database that I didn't have in 3.6 and now
seems to be required (probably for dashboard?).

[root@ractorshe ~]# engine-setup
...

  --== DATABASE CONFIGURATION ==--

  Where is the 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-04 Thread Arman Khalatyan
about a n hour ago I just tested to setup ovirt 3.6, then upgrade it, 2
nodes: host and ovirt on separated machines.
very smoothly upgraded, first engine upgrade then host upgrade.
The only trouble on hosts is that some pacages are still reffering to
ovirt-3.6 repository even ovirt-4.0 is there.
it is simple to fix: yum list installed| grep ovirt-3.6 then removing all
possible packages
next reinstall host from GUI.
Thats it.




***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 4, 2016 at 12:59 PM, nicola.gentile.to <
nicola.gentile...@gmail.com> wrote:

> alse I am interested.
>
> Nicola
>
>
> Il 04/07/2016 11:25, Arman Khalatyan ha scritto:
>
> Hi,
> I am also interested to upgrade my system from centos 7 ovirt 3.6.7 to
> ovirt4, are there any preferable order to upgrade? Host then engine? or
> engine then host?
> thanks,
> Arman.
>
>
> ***
>
>  Dr. Arman Khalatyan  eScience -SuperComputing
>  Leibniz-Institut für Astrophysik Potsdam (AIP)
>  An der Sternwarte 16, 14482 Potsdam, Germany
>
> ***
>
> On Mon, Jul 4, 2016 at 11:11 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>> Il 04/Lug/2016 09:12, "Yaniv Dary" < yd...@redhat.com>
>> ha scritto:
>> >
>> > Yes, this is correct.
>> >
>> > Yaniv Dary
>> > Technical Product Manager
>> > Red Hat Israel Ltd.
>> > 34 Jerusalem Road
>> > Building A, 4th floor
>> > Ra'anana, Israel 4350109
>> >
>> > Tel : +972 (9) 7692306
>> > 8272306
>> > Email: yd...@redhat.com
>> > IRC : ydary
>> >
>> >
>> > On Jul 4, 2016 08:15,  wrote:
>> >>
>> >> Hi,
>> >>
>> >> in my setup I have two servers on CentOS7. One  of these servers is
>> also running the engine.
>> >>
>> >> From your email I understood that in such case there is not special
>> procedure for me right?
>> >>
>> >> Best regards
>> >>
>> >> Christoph
>> >>
>>
>> Is it the same in case of single host with CentOS 7 and hosted engine?
>> Any caveat in this scenario?
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-04 Thread nicola.gentile.to

alse I am interested.

Nicola

Il 04/07/2016 11:25, Arman Khalatyan ha scritto:

Hi,
I am also interested to upgrade my system from centos 7 ovirt 3.6.7 to 
ovirt4, are there any preferable order to upgrade? Host then engine? 
or engine then host?

thanks,
Arman.


***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 4, 2016 at 11:11 AM, Gianluca Cecchi 
> wrote:



Il 04/Lug/2016 09:12, "Yaniv Dary" > ha scritto:
>
> Yes, this is correct.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306 
> 8272306
> Email: yd...@redhat.com 
> IRC : ydary
>
>
> On Jul 4, 2016 08:15, >
wrote:
>>
>> Hi,
>>
>> in my setup I have two servers on CentOS7. One of these servers
is also running the engine.
>>
>> From your email I understood that in such case there is not
special procedure for me right?
>>
>> Best regards
>>
>> Christoph
>>

Is it the same in case of single host with CentOS 7 and hosted engine?
Any caveat in this scenario?


___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-04 Thread Arman Khalatyan
Hi,
I am also interested to upgrade my system from centos 7 ovirt 3.6.7 to
ovirt4, are there any preferable order to upgrade? Host then engine? or
engine then host?
thanks,
Arman.


***

 Dr. Arman Khalatyan  eScience -SuperComputing
 Leibniz-Institut für Astrophysik Potsdam (AIP)
 An der Sternwarte 16, 14482 Potsdam, Germany

***

On Mon, Jul 4, 2016 at 11:11 AM, Gianluca Cecchi 
wrote:

>
> Il 04/Lug/2016 09:12, "Yaniv Dary"  ha scritto:
> >
> > Yes, this is correct.
> >
> > Yaniv Dary
> > Technical Product Manager
> > Red Hat Israel Ltd.
> > 34 Jerusalem Road
> > Building A, 4th floor
> > Ra'anana, Israel 4350109
> >
> > Tel : +972 (9) 7692306
> > 8272306
> > Email: yd...@redhat.com
> > IRC : ydary
> >
> >
> > On Jul 4, 2016 08:15,  wrote:
> >>
> >> Hi,
> >>
> >> in my setup I have two servers on CentOS7. One  of these servers is
> also running the engine.
> >>
> >> From your email I understood that in such case there is not special
> procedure for me right?
> >>
> >> Best regards
> >>
> >> Christoph
> >>
>
> Is it the same in case of single host with CentOS 7 and hosted engine?
> Any caveat in this scenario?
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-04 Thread Gianluca Cecchi
Il 04/Lug/2016 09:12, "Yaniv Dary"  ha scritto:
>
> Yes, this is correct.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Jul 4, 2016 08:15,  wrote:
>>
>> Hi,
>>
>> in my setup I have two servers on CentOS7. One  of these servers is also
running the engine.
>>
>> From your email I understood that in such case there is not special
procedure for me right?
>>
>> Best regards
>>
>> Christoph
>>

Is it the same in case of single host with CentOS 7 and hosted engine?
Any caveat in this scenario?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-04 Thread ovirt

Thank you for the quick answer.

Best regards
Christoph


Am 04.07.2016 um 09:12 schrieb Yaniv Dary:


Yes, this is correct.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com 
IRC : ydary


On Jul 4, 2016 08:15, > wrote:

Hi,

in my setup I have two servers on CentOS7. One  of these servers
is also running the engine.

From your email I understood that in such case there is not
special procedure for me right?

Best regards

Christoph



Am 03.07.2016 um 21:37 schrieb Yedidyah Bar David:

On Sun, Jul 3, 2016 at 7:48 PM,  > wrote:

Hi List,

is there a special upgrade procedure to get from 3.6 to
4.0 of oVirt?

Depends on your current system.

Or it is just a normal upgrade procedure?

It is in some cases.

I'm currently running oVirt 3.6.7 on CentOS 7.

If not hosted-engine, normal upgrade.

For hosted-engine please see a recent thread on this list with
subject line "upgrade hosted-engine os ( not hosts )".

For an engine on el6, in-place direct upgrade to el7 is not
supported. You can use backup/restore migration:

https://bugzilla.redhat.com/1318580

Best,

Best regards and thank you for the answer.
Christoph

___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-04 Thread Yaniv Dary
Yes, this is correct.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary

On Jul 4, 2016 08:15,  wrote:

> Hi,
>
> in my setup I have two servers on CentOS7. One  of these servers is also
> running the engine.
>
> From your email I understood that in such case there is not special
> procedure for me right?
>
> Best regards
>
> Christoph
>
>
>
> Am 03.07.2016 um 21:37 schrieb Yedidyah Bar David:
>
>> On Sun, Jul 3, 2016 at 7:48 PM,   wrote:
>>
>>> Hi List,
>>>
>>> is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt?
>>>
>> Depends on your current system.
>>
>> Or it is just a normal upgrade procedure?
>>>
>> It is in some cases.
>>
>> I'm currently running oVirt 3.6.7 on CentOS 7.
>>>
>> If not hosted-engine, normal upgrade.
>>
>> For hosted-engine please see a recent thread on this list with
>> subject line "upgrade hosted-engine os ( not hosts )".
>>
>> For an engine on el6, in-place direct upgrade to el7 is not
>> supported. You can use backup/restore migration:
>>
>> https://bugzilla.redhat.com/1318580
>>
>> Best,
>>
>> Best regards and thank you for the answer.
>>> Christoph
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>>
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-03 Thread ovirt

Hi,

in my setup I have two servers on CentOS7. One  of these servers is also 
running the engine.


From your email I understood that in such case there is not special 
procedure for me right?


Best regards

Christoph



Am 03.07.2016 um 21:37 schrieb Yedidyah Bar David:

On Sun, Jul 3, 2016 at 7:48 PM,   wrote:

Hi List,

is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt?

Depends on your current system.


Or it is just a normal upgrade procedure?

It is in some cases.


I'm currently running oVirt 3.6.7 on CentOS 7.

If not hosted-engine, normal upgrade.

For hosted-engine please see a recent thread on this list with
subject line "upgrade hosted-engine os ( not hosts )".

For an engine on el6, in-place direct upgrade to el7 is not
supported. You can use backup/restore migration:

https://bugzilla.redhat.com/1318580

Best,


Best regards and thank you for the answer.
Christoph

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-07-03 Thread Yedidyah Bar David
On Sun, Jul 3, 2016 at 7:48 PM,   wrote:
> Hi List,
>
> is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt?

Depends on your current system.

>
> Or it is just a normal upgrade procedure?

It is in some cases.

>
> I'm currently running oVirt 3.6.7 on CentOS 7.

If not hosted-engine, normal upgrade.

For hosted-engine please see a recent thread on this list with
subject line "upgrade hosted-engine os ( not hosts )".

For an engine on el6, in-place direct upgrade to el7 is not
supported. You can use backup/restore migration:

https://bugzilla.redhat.com/1318580

Best,

>
> Best regards and thank you for the answer.
> Christoph
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users