-
-
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
Feature: creation of sub directory into glusterfs volume #35
Comments
That shouldn't be too hard to do. It maybe possible to add the subdir inside voluri and keep backward compat. |
You need to have GlusterFS 3.12 at minimum for this to work. I think you may be using an older version of GlusterFS which is causing it to fail on my set up. |
@trajano this is not implemented yet. I was just talking about a way to implement it. |
I think if you just use Gluster 3.12 or assume Gluster 3.12 is installed (I don't think you make any assumption on what is installed though because I see the volume mounted even without the glusterfs client installed by yum) then you can simply pass in
|
In managed plugin, glusterfs should be 3.13 https://packages.debian.org/fr/testing/glusterfs-client. But, I use the glusterfs command and not mount (https://github.com/sapk/docker-volume-gluster/blob/master/gluster/driver/driver.go#L44). |
The parseVolUri needs to add |
I tried to make it but I don't know Go well enough here's my cut
|
I will have a look at it tommorrow. |
Great job guys :) |
Doing more tests but should release soon. |
@sapk Has this feature made it into any of the releases yet? I am still having issues with gluster 5.3 |
@sapk
Is it ppssible add a feature (e.g. additional parameter of volume create) to allow creation of sub-directory into GlusterFS volume so we can use 1 volume for multiple containers (lots of sub folders)?
It should be better then create lots of volumes (per-container) on dense environments.
Gluster cli already allow managing of directory quotas even if folders are not yet created.
The text was updated successfully, but these errors were encountered: