Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

simple getting started guide #38

Open
raffaeleguidi opened this issue Mar 23, 2018 · 7 comments
Open

simple getting started guide #38

raffaeleguidi opened this issue Mar 23, 2018 · 7 comments

Comments

@raffaeleguidi
Copy link

raffaeleguidi commented Mar 23, 2018

In example, I assume that the glusterfs pool has to be up and running before using the driver, but it is not stated anywhere. Also I don't understand whether the docker host has to also partecipate in the gluster pool or not, needs fuse installed, etc. Overall documenting some prerequirements and pointers to gluster documentation where applicable would be a really nice addition - I can contribute if you gimme some directions

@sapk
Copy link
Owner

sapk commented Mar 23, 2018

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.

@raffaeleguidi
Copy link
Author

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
Copy link
Owner

sapk commented Mar 23, 2018

You should be ok.

@pascalandy
Copy link

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!

@antoniomtz
Copy link

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

@sapk
Copy link
Owner

sapk commented Nov 2, 2018

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
Copy link
Owner

sapk commented Nov 2, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants