[ovirt-devel] Community ads on StackOverflow, 1st half 2015

2015-01-08 Thread Brian Proffitt
We have a new community ad set to go for the next StackOverflow campaign for the first half of the year. Allon Mureinik has posted it at: http://meta.stackoverflow.com/a/283016/2422776 Now we just need some upvotes there to have the ad approved. The current threshold is +6. If you are a member

Re: [ovirt-devel] engine.ear fails on current ovirt-3.5 branch

2015-01-08 Thread Adam Litke
On 08/01/15 10:44 -0500, Alon Bar-Lev wrote: - Original Message - From: "Adam Litke" To: devel@ovirt.org Cc: "Alon Bar-Lev" Sent: Thursday, January 8, 2015 5:35:20 PM Subject: Re: [ovirt-devel] engine.ear fails on current ovirt-3.5 branch On 07/01/15 16:43 -0500, Adam Litke wrote: >

Re: [ovirt-devel] engine.ear fails on current ovirt-3.5 branch

2015-01-08 Thread Alon Bar-Lev
- Original Message - > From: "Adam Litke" > To: devel@ovirt.org > Cc: "Alon Bar-Lev" > Sent: Thursday, January 8, 2015 5:35:20 PM > Subject: Re: [ovirt-devel] engine.ear fails on current ovirt-3.5 branch > > On 07/01/15 16:43 -0500, Adam Litke wrote: > >Hi all, > > > >Back from a long

Re: [ovirt-devel] engine.ear fails on current ovirt-3.5 branch

2015-01-08 Thread Adam Litke
On 07/01/15 16:43 -0500, Adam Litke wrote: Hi all, Back from a long vacation I decided to build a fresh engine from the tip of the ovirt-3.5 branch (447ff7) and to my dismay, the deployed build will not start within jboss. The following error seems of paramount importance (full log attached).

Re: [ovirt-devel] Adding support for 3.6 in engine database

2015-01-08 Thread Eli Mesika
- Original Message - > From: "Eli Mesika" > To: "Lior Vernia" > Cc: "Oved Ourfali" , "Dan Kenigsberg" , > "engine-de...@ovirt.org" > , "Yaniv Bronheim" > Sent: Thursday, January 8, 2015 4:06:58 PM > Subject: Re: [ovirt-devel] Adding support for 3.6 in engine database > > > > -

Re: [ovirt-devel] Adding support for 3.6 in engine database

2015-01-08 Thread Eli Mesika
- Original Message - > From: "Lior Vernia" > To: "Oved Ourfali" > Cc: "Dan Kenigsberg" , "engine-de...@ovirt.org" > , "Yaniv Bronheim" > , "Eli Mesika" > Sent: Thursday, January 8, 2015 3:48:53 PM > Subject: Re: [ovirt-devel] Adding support for 3.6 in engine database > > > > On 08/

Re: [ovirt-devel] Adding support for 3.6 in engine database

2015-01-08 Thread Lior Vernia
On 08/01/15 15:46, Oved Ourfali wrote: > > > - Original Message - >> From: "Eli Mesika" >> To: "Lior Vernia" , "Oved Ourfali" >> Cc: "engine-de...@ovirt.org" , "Dan Kenigsberg" >> , "Yaniv Bronheim" >> >> Sent: Thursday, January 8, 2015 3:41:31 PM >> Subject: Re: [ovirt-devel] Addin

Re: [ovirt-devel] Adding support for 3.6 in engine database

2015-01-08 Thread Oved Ourfali
- Original Message - > From: "Eli Mesika" > To: "Lior Vernia" , "Oved Ourfali" > Cc: "engine-de...@ovirt.org" , "Dan Kenigsberg" > , "Yaniv Bronheim" > > Sent: Thursday, January 8, 2015 3:41:31 PM > Subject: Re: [ovirt-devel] Adding support for 3.6 in engine database > > > > -

Re: [ovirt-devel] Adding support for 3.6 in engine database

2015-01-08 Thread Eli Mesika
- Original Message - > From: "Lior Vernia" > To: "Eli Mesika" > Cc: "engine-de...@ovirt.org" , "Dan Kenigsberg" > , "Yaniv Bronheim" > > Sent: Thursday, January 8, 2015 3:08:24 PM > Subject: Re: [ovirt-devel] Adding support for 3.6 in engine database > > Tried to work with it, and no

Re: [ovirt-devel] Adding support for 3.6 in engine database

2015-01-08 Thread Michal Skrivanek
On Jan 8, 2015, at 14:08 , Lior Vernia wrote: > Tried to work with it, and noticed that: > 1. The engine doesn't list 4.17 as a supported vdsm version. > 2. 4.17 vdsm doesn't report 3.6 as a supported engine version. > > This basically means that no host could be operational in a 3.6 cluster, >

Re: [ovirt-devel] Adding support for 3.6 in engine database

2015-01-08 Thread Lior Vernia
Tried to work with it, and noticed that: 1. The engine doesn't list 4.17 as a supported vdsm version. 2. 4.17 vdsm doesn't report 3.6 as a supported engine version. This basically means that no host could be operational in a 3.6 cluster, as to my understanding 4.17 is exactly the version supportin