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

Give drives a mount point #6

Closed
butonic opened this issue Jul 19, 2021 · 1 comment
Closed

Give drives a mount point #6

butonic opened this issue Jul 19, 2021 · 1 comment

Comments

@butonic
Copy link
Member

butonic commented Jul 19, 2021

A deployment consists of a storage registry, storage providers, an ocdav handler and a graph api endpoint.

The storage registry organizes the storage spaces in a namespace.

The /webav endpoint then uses that namespace to provide human readable access to resources, but names and paths can change.

The /dav/spaces endpoint allows direct access to a storage space, regardless of the mount point.

To allow clients to build a custom registry (namespace) we need a way to expose the mount points for storage spaces.

When listing drives they should return a mountpoint property that contains the path in the global namespace that is accessible at /webdav, eg.: /personal/einstein for einsteins home space.

In oc10 / would be the users home and shares would be mounted in arbitrary locations.

In ocis we would make that /personal/einstein

The admin can build a namespace by mounting spaces in the storage registry as he sees fit. This is only a recommendation, because clients can build a completely different namespace if they desire. That includes storage spaces from other instances / deployments.

@micbar
Copy link
Contributor

micbar commented Mar 7, 2022

Possible Solution #36

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

2 participants