Directory and data management services API and protocol

From ReddNet
Revision as of 16:45, 25 January 2008 by Wikiadmin (talk | contribs)
Jump to navigation Jump to search

This page lists all of the functions that we can think of that may be made interoperable. Functional areas can be added, and discussions of how each function applies to different frameworks (lStore, Lodn, ...)

Name service

  • Directory manipulation - opendir like interface (create,delete,move,walk)
  • Open/close; obtain a handle/ release handle
  • get file mappings
  • soft links - internal and external
  • add arbitrary metadata ala xfs
  • registration of a policy - microservices



- locking file & byte range (Persistency)

- Specify lun + upload, download (Data logistics)


- replication (Data logistics)

- fault tolerance (Data integrity)

- permissions (Security)

- auth/authz (Security)

- allocate space (Data logistics)

- data migration (Data logistics)


- recover failed mappings (Data integrity)

- encryption (Security)


- object integrity (Data integrity)

- fsck/format/default options (Data integrity)

- object life times (Data logistics)

- advanced resource allocation (Data logistics)

- workflows (Data logistics)

- data-pathing (Data logistics)


- quotas (Data logistics)

- versioning (?)

- obnject semantics - versioning/copy-on-write/locking etc (?)


- other ideas ???