[GEDI] [openstack-dev] [Cinder] Requirements for re-adding Gluster support

[Niels de Vos]

Thanks to everyone who replied! I'll try to summarize what we'll try to
get from the Gluster Community users that run OpenStack.

- find an owner/maintainer for the Gluster driver in Cinder
  little maintenance seems needed, no recent problems reported

- get someone to maintain the gate job(s) in a CI environment of their
  own choosing (OpenStack Infra, Gluster Community, CentOS CI, ..)

- send a patch to revert the change for removing the driver from Cinder

- send a patch to revert the change for removing the driver from Nova


With these tasks I'll try to find some of the OpenStack users in the
Gluster Community that want to volunteer for this. There are a few
Gluster developers (from Red Hat) that can assist these volunteers, but
developers working for Red Hat will not have this as a priority. It
falls in the "support the Gluster Community" bucket, and community users
will need to do most of the work. This is similar for any of the other
Open Source projects where Gluster is not productized by Red Hat.

A similar approach by Red Hat developers working on Cinder caused the
volume driver to be removed. We hope that interested users will step up
and offer their time.

Please let me know if I missed something or if this approach is
unacceptible or unclear.

Cheers,
Niels


On Wed, Jul 26, 2017 at 12:56:55PM +0200, Niels de Vos wrote:
> Hello,
> 
> In one of the last Cinder releases support for Gluster has been dropped.
> The commit message [1] mentions that the support has been marked
> deprecated during Newton.
> 
> It seems that there are quite some users in the Gluster Community that
> run OpenStack with Gluster storage. These users did not take action when
> Newton came out, but voiced their disappointment with more recent
> releases.
> 
> As one of the Gluster Maintainers that is watching over the integration
> of Gluster in other projects, I would like to know more about the tasks
> that it takes to get Gluster support back into Cinder. With those
> details, the Gluster Community can work with interested OpenStack users
> to add required CI jobs, and possibly other things. 
> 
> At the moment, the only knowledge I have on why Gluster support was
> removed from Cinder is in a messy email conversation [2]. Pointers to
> further clarifications and requirements that Gluster did not meet are
> welcome.
> 
> My current guess is that adding a 3rd party CI [3] for Gluster is the
> only missing piece? If that is the case, I expect that we could add one
> or more Jenkins jobs to one of our Gluster Community CI's. We run tests
> in our own Jenkins instance [4], but also use the CentOS CI [5] for some
> heavier testing.
> 
> Any guidance, suggestions and opinions are most welcome!
> 
> Many thanks,
> Niels
> 
> 
> 1. https://github.com/openstack/cinder/commit/16e93ccd4f3a6d62ed9d277f03b64bccc63ae060
> 2. http://lists.gluster.org/pipermail/integration/2017-May/000024.html
> 3. https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
> 4. https://build.gluster.org/
> 5. https://ci.centos.org/view/Gluster/
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev