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

Add table/value to map user id to storage id #15166

Closed
PVince81 opened this issue Mar 24, 2015 · 9 comments
Closed

Add table/value to map user id to storage id #15166

PVince81 opened this issue Mar 24, 2015 · 9 comments
Assignees
Milestone

Comments

@PVince81
Copy link
Contributor

At the moment it is very hard to find the storage of a given user, one needs to find the correct storage id (local:: or home::, also from LDAP's getHome()).

If would be much more convenient to have either a mapping table that maps user ids to numeric storage ids (numeric_id).

Also it could help solving the problems with legacy storages by having a stronger/stabler link with the storage numeric id (which isn't supposed to change)

@icewind1991 @MorrisJobke @Xenopathic @schiesbn @DeepDiver1975

@mmattel
Copy link
Contributor

mmattel commented Mar 25, 2015

👍

Maybe from singular to plural, which storage ID´s are available for a particular user ID or group ID.
If you add / delete / change a storage for a user / group, this is then just a DB change with minimum efforts and immediate effect.

uID, gID, stID (columns could be extended)

Example: a user can have a (or more) stID for himself AND some additional stID´s because he is part of a group and they can be differnt ID´s ect.

To consider: having eg SMB, you can declare that a user is directed based on an stID to a remote subfolder with his name. This is not declared seperately for each user, but in general for all users in one declaration (root = $user).

@PVince81
Copy link
Contributor Author

Or add an additional column in the oc_storages table at least.

@PVince81
Copy link
Contributor Author

A repair step will be needed to fill the table/column for existing users.

@PVince81
Copy link
Contributor Author

The basic requirement is at least knowing what home storage belongs to which user.
As an extension, which external storage is mapped to which user.
This PR which moves the ext storage config to the database already provides an "applicable" table which could be used for external storages: #20370

@PVince81
Copy link
Contributor Author

@icewind1991 let's use this ticket for the fstab-like mapping table.

Can you post the columns you suggested ?

@PVince81
Copy link
Contributor Author

@DeepDiver1975 talked with @nickvergessen and @icewind1991 and we'll need this mapping table.
As discussed in Berlin #18771 we suggested having a fstab-like table that lists mount points for all users for easier lookup. That table would also help to be able to resolve the owner of storages.

@PVince81
Copy link
Contributor Author

WIP PR here #20768

@PVince81
Copy link
Contributor Author

PR was merged already (oc_mounts table), closing

@MorrisJobke MorrisJobke modified the milestones: 9.0-current, 9.1-next Feb 23, 2016
@lock
Copy link

lock bot commented Aug 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants