-
Notifications
You must be signed in to change notification settings - Fork 187
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
[docs-only] Initial commit of collaborative storage notes #7833
Conversation
|
||
## Path Locations | ||
|
||
What is called "the oCIS file system" is defined as the entire filetree underneath a special path in the local POSIX file system, which might either be a real local file system or a mounted net filesystem. It is expected that oCIS is the only consumer of that file tree, except what is expected behaviour with a collaborative file system, that adds and edits files in that tree. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...in the local POSIX file system...
I am not confident with this statement because of POSIX and S3, see Available Filesystem Drivers in the admin documentation. IMHO we should be consistent and absolut clear right from the beginning also in the following sections of what we are talking about when it comes to the ocis filesystem
and blobs/metadata.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What exactly do you suggest to change here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have time today or tomorrow for an exchange via zoom? I would be available...
|
||
## Metadata Management | ||
|
||
Metadata are data "snippets" that are as tightly attached to files as ever possible. In best case, a rename of a file silently keeps the metadata as well. In POSIX, this can be achieved by extended file attributes with certain limitations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...by extended file attributes...
hmmm, havn't we kicked out extended file attributes with ocis v3 and we use from then on messagepack by default? Also see the prerequisites in the admin docs as linked in the comment before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the text is about collaborative storage where it is even more important that the metadata is attached to the file because there can be file system manipulation outside of oCIS' control.
If we can not use xattrs, we maybe can store a "link" to the messagepack file in xattrs - so that we can find the metadata even if the file was moved. Needs more investigation.
When ready to final review, maybe to add @EParzefall for a language check... |
Kudos, SonarCloud Quality Gate passed! |
[docs-only] Initial commit of collaborative storage notes
Notes about components of a storage driver, especially collaborative storage.
Lots more to add and clarify probably. Maybe not ready to merge.