John Strunk

> I don't think I have write access to that branch. Any help to remedy that would be appreciated. I'm not sure where the switch would be... You have write...

I'm not aware of any plans to take this forward. Sorry.

At the current time, I would not recommend this for production usage. @amarts Can either point you to a current roadmap for Gluster or provide an update.

By "products", he's referring to companies shipping a supported storage product based on this code. Having products based on the code typically provide a steady stream of features, fixes, and...

After taking a quick look, I think this is going to need a design doc and significant discussion. Perhaps I'm misunderstanding things like the `client` directory, but it looks like...

> @Madhu-1 This allows logic isolation of the different roles, and is a precursor to bringing in different types of Controllers, such as for heketi and gluster-block. I'm still not...

> > I'm still not understanding the motivation. Now each type of CSI driver has multiple containers that must be built. > > Modularizing the code (e.g., abstracting the client...

> There was already talk of having a separate driver for gluster-block, at the very least, under the name of something like glusterblock.gluster.org. It would seem like an unnecessary burden...

> @JohnStrunk any update on this PR? I have nothing to add to my previous comments.

The CSI driver will not use Heketi. [GlusterD2](https://github.com/gluster/glusterd2) is the new management layer for gluster. It will be incorporating an intelligent volume provisioner (some functionality has already been merged), subsuming...