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

[docs-only] Initial commit of collaborative storage notes #7833

Merged
merged 2 commits into from
Nov 21, 2024

Conversation

dragotin
Copy link
Contributor

Notes about components of a storage driver, especially collaborative storage.

Lots more to add and clarify probably. Maybe not ready to merge.


## 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.
Copy link
Contributor

@mmattel mmattel Nov 29, 2023

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.

Copy link
Contributor Author

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?

Copy link
Contributor

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.
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@mmattel
Copy link
Contributor

mmattel commented Nov 29, 2023

When ready to final review, maybe to add @EParzefall for a language check...

Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@micbar micbar merged commit 2ea9680 into master Nov 21, 2024
2 checks passed
@micbar micbar deleted the docs-add-collstorage branch November 21, 2024 07:14
ownclouders pushed a commit that referenced this pull request Nov 21, 2024
[docs-only] Initial commit of collaborative storage notes
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

Successfully merging this pull request may close these issues.

3 participants