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 to move to 5 directly and possibly the best outcome for this issue Shyam On 11/27/2018 09:11 AM, Niels de Vos wrote:
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 <ndevos@redhat.com> 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 getting an agreement on what we should require in oVirt 4.3: CentOS Storage SIG provides bot 4.1 and 5 for x86_64[1] and ppc64le[2]
If I understood correctly, 5 is shipping glusterd2 which requires a significant effort to get support for while 4.1 is still on glusterd which should work with current oVirt code.
Also Gluster 5 still offers the traditional glusterd service. glusterd2 is available for both 4.1 and 5, but it is still an opt-in.
HTH, Niels
PS: Gluster 5 is not announced for CentOS yet, the centos-release-gluster5 package is not yet publicly available
I think we should move to latest version, i.e Gluster 5. Niels, is there any ETA for when the package will be available in CentOS?
We're waiting for CentOS 7.6 to be released. After that the updates for the SIGs can be pushed again. ETA is not known yet, but Twitter feeds from the CentOS developers are positive and may suggest a release in a few days?
Niels