On Fri, Nov 02, 2018 at 12:23:38PM +0000, Niels de Vos wrote:
> On Fri, Nov 02, 2018 at 12:52:59PM +0100, Sandro Bonazzola wrote:
> > Il giorno ven 2 nov 2018 alle ore 12:33 Niels de Vos <ndevos@redhat.com> ha
> > scritto:
> >
> > > On Thu, Nov 01, 2018 at 11:01:51AM +0200, Anssi Johansson wrote:
> > > ...
> > > > For reference and inspiration, here are some directories from
> > > > mirror.centos.org, including both up-to-date content and potentially EOL
> > > > content. SIGs should review the list to make sure these directories can
> > > > be copied over to 7.6.1810 when that time comes. Making the decisions
> > > > now would save a bit of time at 7.6.1810 release time.
> > > >
> > > ..
> > >
> > > > storage/x86_64/gluster-3.10
> > > > storage/x86_64/gluster-3.12
> > >
> > > The above two can be dropped (also for CentOS 6). This includes the
> > > centos-release-gluster310 and centos-release-gluster-312 packages in
> > > Extras.
> > >
> > >
> > Can we keep 3.12? It's still consumed by oVirt 4.2.
> > Adding oVirt devel team, just in case we'll need urgently to rebase on
> > newer Gluster on CentOS 7.6 GA or block upgrade to CentOS 7.6 from oVirt
> > side till we figure out how to handle.
>
> 3.12 does not get any updates anymore... Ideally users do not consume
> that version but have moved on to 4.0 or 4.1 already. Gluster 5 is
> available and should get announced soon (not sure if that can happen
> with the CentOS 7.6 release).

Is it possible for us to remove the centos-release-gluster312 package
from CentOS Extras, but keep the gluster-3.12 repository available for
you to consume with oVirt 4.2? That would prevent users from installing
an unmaintained version, but you can still download the packages.

We also forcefully disable the unmaintained repositories (as they will
get deleted later), but I can wait with that if it helps. This is done
through
https://github.com/CentOS-Storage-SIG/centos-release-gluster-legacy in
case you're interested.

So, what I need from you, is an estimation of dates of when the
following actions can be done:

1. delete centos-release-gluster312 from CentOS Extras

2. remove the gluster-3.12 repository from the mirrors

3. update centos-release-gluster-legacy with Gluster 3.12 deprecation

Thanks,
Niels