Comparison to other plugins GlusterFS Docker Volume Plugins

[Vad1mo]

Maybe you could elaborate in the README.md what is the difference of your plugin to https://github.com/amarkwalder/docker-volume-glusterfs and its many active forks like

https://github.com/watson81/docker-volume-glusterfs

This would help people to make a decision.

[sapk]

Yes mainly :

• It is possible to use it as docker plugin (new format).
• It use latest github.com/docker/go-plugins-helpers/volume format.
• It should have persistence across boot.
• The name of the docker volume is not attached to the name of the gluster volume -> (multiple mount possible and compatible with docker-compose)

For calavera based plugin :

• It support auto-creation
• It use glusterfs cli that support multiple server definition (I am planning to do that just want to find a way to pass it fuse opts) https://github.com/amarkwalder/docker-volume-glusterfs/blob/master/driver.go#L176

Overall, building this driver I look a lot to calavera code for information. The main purpose for me was the new docker plugin format.

[sapk]

Forgot that with calavera one you need to define the server list at the plugin level where mine you define it at volume level allowing to use any server without restarting the plugin.

[sapk]

Now you can also use subdir volume.

[Vad1mo]

I saw this already, great :) thank you.

[ssirag]

Sapk you stated we can use subdir volume... if I understand correctly, that means we can specify a subdir in a glusterfs volume to use as the target of the plugin, is that correct?

IE "gfs server:gfs volume/subdir"

If so, where do we specify this? In the docker volume creation or in the docker run command that uses the volume?