[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-28 Thread Sandro Bonazzola
Il giorno mer 28 nov 2018 alle ore 17:56 Sandro Bonazzola < sbona...@redhat.com> ha scritto: > > > Il giorno mer 28 nov 2018 alle ore 17:39 Niels de Vos > ha scritto: > >> On Wed, Nov 28, 2018 at 05:22:32PM +0100, Sandro Bonazzola wrote: >> > Il giorno mer 28 nov 2018 alle ore 17:13 Niels de Vos

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-28 Thread Sandro Bonazzola
Il giorno mer 28 nov 2018 alle ore 17:39 Niels de Vos ha scritto: > On Wed, Nov 28, 2018 at 05:22:32PM +0100, Sandro Bonazzola wrote: > > Il giorno mer 28 nov 2018 alle ore 17:13 Niels de Vos > > > ha scritto: > > > > > On Wed, Nov 28, 2018 at 10:42:18AM -0500, Shyam Ranganathan wrote: > > > >

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-28 Thread Niels de Vos
On Wed, Nov 28, 2018 at 05:22:32PM +0100, Sandro Bonazzola wrote: > Il giorno mer 28 nov 2018 alle ore 17:13 Niels de Vos > ha scritto: > > > On Wed, Nov 28, 2018 at 10:42:18AM -0500, Shyam Ranganathan wrote: > > > Top posting > > > > > > 1) Glusterd2 is not yet the default in release-5, and in

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-28 Thread Sandro Bonazzola
Il giorno mer 28 nov 2018 alle ore 17:13 Niels de Vos ha scritto: > On Wed, Nov 28, 2018 at 10:42:18AM -0500, Shyam Ranganathan wrote: > > Top posting > > > > 1) Glusterd2 is not yet the default in release-5, and in all probability > > will not be in release-6 as well. So that concern can be

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-28 Thread Niels de Vos
On Wed, Nov 28, 2018 at 10:42:18AM -0500, Shyam Ranganathan wrote: > Top posting > > 1) Glusterd2 is not yet the default in release-5, and in all probability > will not be in release-6 as well. So that concern can be avoided for > this decision. (as Niels stated) > > 2) In the provided mirror

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-28 Thread Shyam Ranganathan
Top posting 1) Glusterd2 is not yet the default in release-5, and in all probability will not be in release-6 as well. So that concern can be avoided for this decision. (as Niels stated) 2) In the provided mirror links I see release-5 now, so Niels this is now published? If so we can ask ovirt

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-27 Thread Niels de Vos
On Tue, Nov 27, 2018 at 02:02:42PM +0100, Sandro Bonazzola wrote: > Il giorno lun 19 nov 2018 alle ore 14:42 Sahina Bose ha > scritto: > > > On Tue, Nov 13, 2018 at 3:48 PM Niels de Vos wrote: > > > > > > On Tue, Nov 13, 2018 at 10:01:15AM +0100, Sandro Bonazzola wrote: > > > > According to

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-27 Thread Niels de Vos
On Mon, Nov 19, 2018 at 07:12:30PM +0530, Sahina Bose wrote: > On Tue, Nov 13, 2018 at 3:48 PM Niels de Vos wrote: > > > > On Tue, Nov 13, 2018 at 10:01:15AM +0100, Sandro Bonazzola wrote: > > > According to Sahina we dropped dependency on gluster-gnfs and it's safe to > > > move on from the

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-27 Thread Sandro Bonazzola
Il giorno lun 19 nov 2018 alle ore 14:42 Sahina Bose ha scritto: > On Tue, Nov 13, 2018 at 3:48 PM Niels de Vos wrote: > > > > On Tue, Nov 13, 2018 at 10:01:15AM +0100, Sandro Bonazzola wrote: > > > According to Sahina we dropped dependency on gluster-gnfs and it's > safe to > > > move on from

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-19 Thread Sahina Bose
On Tue, Nov 13, 2018 at 3:48 PM Niels de Vos wrote: > > On Tue, Nov 13, 2018 at 10:01:15AM +0100, Sandro Bonazzola wrote: > > According to Sahina we dropped dependency on gluster-gnfs and it's safe to > > move on from the unsupported 3.12 version to a newer one 4.1 / 5.0. > > > > This is for

[ovirt-devel] Re: GlusterFS rebase for oVirt 4.3

2018-11-13 Thread Niels de Vos
On Tue, Nov 13, 2018 at 10:01:15AM +0100, Sandro Bonazzola wrote: > According to Sahina we dropped dependency on gluster-gnfs and it's safe to > move on from the unsupported 3.12 version to a newer one 4.1 / 5.0. > > This is for getting an agreement on what we should require in oVirt 4.3: >