simple getting started guide about docker-volume-gluster

[sapk]

Great, I would gladly accept contribution. External point of view for documentation is really good. As maintainer I may assume a lot of things writing it.

For start the docker host doesn't have to be in the gluster pool it just need to be able to access each of the pool member. I think, I should add a way to test it since I think most issue come from this.

The gluster volumes need to be created before. It's planned on the roadmap to auto-create corresponding gluster volume via heketi (#5)

For dependency,
If you use the managed plugin docker plugin install sapk/plugin-gluster all the deps are in the containers that hold the plugin you just need fuse on host (the plugin hook itself on host /dev/fuse).
With the legacy mode, you also need glusterfs-client package (debian name) or the corresping in your distrib.

[pascalandy]

I'm trying to test this project and I'm confused.

From what I read here, there is pre-requirement in order to use this project right?

Thank you!

[raffaeleguidi]

So, let me see if I got it right:

1. a glusterfs pool with volumes already in place somewhere
2. fuse and glusterfs client installed on each docker host
3. all glusterfs required ports open on the client

is it right? In case I would just try to install everything and document the process in the meanwhile

[sapk]

You should be ok.

[antoniomtz]

I'm also trying to test this project from source code, any guidelines for development stand point?

[sapk]

If you want to compile it just look at the makefile. I will show you how the plugin is compiled for both legacy (make compile) and managed (make docker-plugin) plugin. You should have all the needed tools installed with make dev-deps

[sapk]

@pascalandy Sorry I forget your message. The only prerequisite would be having docker running and a working gluster volume.