Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-21 Thread Yaniv Kaul
On Tue, Jun 21, 2016 at 10:05 AM, Moran Goldboim wrote: > > > On Tue, Jun 21, 2016 at 9:39 AM, Sandro Bonazzola > wrote: > >> >> >> On Sun, Jun 19, 2016 at 3:06 PM, Moran Goldboim >> wrote: >> >>> my pov - really depends on when do

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-21 Thread Moran Goldboim
On Tue, Jun 21, 2016 at 9:39 AM, Sandro Bonazzola wrote: > > > On Sun, Jun 19, 2016 at 3:06 PM, Moran Goldboim > wrote: > >> my pov - really depends on when do we release 4.1. >> short version (Dec 16) - we should keep it, and 3.6 api as well >> long

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-20 Thread Nir Soffer
On Mon, Jun 20, 2016 at 7:49 PM, Nir Soffer wrote: > On Sun, Jun 19, 2016 at 3:40 PM, Dan Kenigsberg wrote: >> On Sun, Jun 19, 2016 at 02:13:40PM +0300, Nir Soffer wrote: >>> Hi all, >>> >>> We should not support now Engine 3.5 with ovirt 4.0, but vdsm

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-20 Thread Nir Soffer
On Sun, Jun 19, 2016 at 3:40 PM, Dan Kenigsberg wrote: > On Sun, Jun 19, 2016 at 02:13:40PM +0300, Nir Soffer wrote: >> Hi all, >> >> We should not support now Engine 3.5 with ovirt 4.0, but vdsm still >> accept 3.5 engines - I guess we forgot to disable it in 4.0. > > Correct.

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-20 Thread Nir Soffer
On Sun, Jun 19, 2016 at 4:00 PM, Yaniv Dary wrote: > What is the cost of keeping them? Hard to tell, I guess each time you touch code related to the api, your effort is doubled. > Yaniv Dary > Technical Product Manager > Red Hat Israel Ltd. > 34 Jerusalem Road > Building A,

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-20 Thread Michal Skrivanek
> On 19 Jun 2016, at 15:06, Moran Goldboim wrote: > > my pov - really depends on when do we release 4.1. > short version (Dec 16) - we should keep it, and 3.6 api as well > long version (Mar 17) - let's drop it than. I would concur So we need a decision regarding short vs

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-19 Thread Moran Goldboim
my pov - really depends on when do we release 4.1. short version (Dec 16) - we should keep it, and 3.6 api as well long version (Mar 17) - let's drop it than. bottom line - we would like to give customers/community the time to migrate their el6 base deployment to el7 , while allowing them dual

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-19 Thread Yaniv Dary
What is the cost of keeping them? 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 Sun, Jun 19, 2016 at 3:40 PM, Dan Kenigsberg

Re: [ovirt-devel] Ending support for 3.x engines on master

2016-06-19 Thread Dan Kenigsberg
On Sun, Jun 19, 2016 at 02:13:40PM +0300, Nir Soffer wrote: > Hi all, > > We should not support now Engine 3.5 with ovirt 4.0, but vdsm still > accept 3.5 engines - I guess we forgot to disable it in 4.0. Correct. There was a moment in time where we considered supporting 3.5 as well. > > In

[ovirt-devel] Ending support for 3.x engines on master

2016-06-19 Thread Nir Soffer
Hi all, We should not support now Engine 3.5 with ovirt 4.0, but vdsm still accept 3.5 engines - I guess we forgot to disable it in 4.0. In 4.1, I don't think we should support any 3.x Engine - otherwise we will have to waste time maintaining old apis and infrastructure, instead of adding new