-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Comments
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, |
So, let me see if I got it right:
is it right? In case I would just try to install everything and document the process in the meanwhile |
You should be ok. |
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! |
I'm also trying to test this project from source code, any guidelines for development stand point? |
If you want to compile it just look at the makefile. I will show you how the plugin is compiled for both legacy ( |
@pascalandy Sorry I forget your message. The only prerequisite would be having docker running and a working gluster volume. |
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
The text was updated successfully, but these errors were encountered: