You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "Xuanwo (via GitHub)" <gi...@apache.org> on 2026/07/30 09:08:40 UTC

[PR] RFC: Define ofs filesystem architecture [opendal-ofs]

Xuanwo opened a new pull request, #16:
URL: https://github.com/apache/opendal-ofs/pull/16

   # Which issue does this PR close?
   
   N/A. This PR starts the RFC discussion. A tracking issue can be created after the RFC is accepted.
   
   # Rationale for this change
   
   ofs needs a stable cross-platform contract that separates storage authority from the way applications access files. The RFC defines Direct and Managed volume models, Mount and Sync access models, and capability negotiation across storage backends and OS frontends.
   
   This keeps zero-migration access to existing storage while providing a path to transactional filesystem semantics and offline-capable replicas.
   
   # What changes are included in this PR?
   
   This PR adds an architecture RFC following the OpenDAL RFC format. It defines user-visible durability and conflict semantics, the core filesystem contract, portability profiles, migration boundaries, and the role of platform-specific frontends.
   
   # Are there any user-facing changes?
   
   No immediate runtime behavior changes. If accepted and implemented, the RFC will introduce volume-oriented mount and sync interfaces while preserving the existing CLI as a Direct Mount compatibility form.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] RFC-0016: Define ofs filesystem architecture [opendal-ofs]

Posted by "PsiACE (via GitHub)" <gi...@apache.org>.
PsiACE merged PR #16:
URL: https://github.com/apache/opendal-ofs/pull/16


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] RFC-0016: Define ofs filesystem architecture [opendal-ofs]

Posted by "jiengup (via GitHub)" <gi...@apache.org>.
jiengup commented on PR #16:
URL: https://github.com/apache/opendal-ofs/pull/16#issuecomment-5140996495

   The RFC is very inspiring!
   
   I have a question: does the `Sync` model work more like a GitHub version of a filesystem? It sounds like we have distributed local versions and a centralized repo. Is there any scenario in which we should use this pattern as a filesystem?
   
   And for the Unresolved question 1, I think we should embed a KV database which has a light-weight semantics and is enough to support filesystem namespace operation, and we can leverage the naive transaction support of that component. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org