-
Notifications
You must be signed in to change notification settings - Fork 6
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
Usage of default posix credentials for direct I/O #47
Comments
Hi, We would like to use Onedata with JupyterHub and mount a space to share datasets amount users. We would like to use NFS as storage backend and hence the request to have direct I/O for decent performances. As in JupyetHub each user internally is using the same uid and gid we were wondering if we could use the default posix credentials in LUMA to configure the direct I/O and avoid to map each single user ( to the same uid) |
We will have to analyse this proposition, I'm not sure if it is viable as it does not align with our current LUMA concepts and assumptions. Maybe we will be able to propose some other mechanism that will cover your use case, other than changing the semantics of default posix credentials. |
Hello,
i was wondering if it would be possible to use the default posix credentials configured in LUMA ( both UID and GID) to enable direct I/O via oneclient, without having the need to add mapping to local UIDs for each users.
There are cases where the is no need to have a separate UIDs for each user.
thanks
Andrea
The text was updated successfully, but these errors were encountered: