Directory and data management services API and protocol

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, ...)

- Directory manipulation - opendir like interface (create,delete,move,walk) (Name service)

- Open/close; obtain a handle/ release handle (Name service)

- locking file & byte range (Persistency)

- Specify lun + upload, download (Data logistics)

- get file mappings (Name service)

- replication (Data logistics)

- fault tolerance (Data integrity)

- permissions (Security)

- auth/authz (Security)

- allocate space (Data logistics)

- data migration (Data logistics)

- soft links - internal and external (Name service)

- recover failed mappings (Data integrity)

- encryption (Security)

- add arbitrary metadata ala xfs (Name service)

- 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)

- registration of a policy - microservices(Name service)

- quotas (Data logistics)

- versioning (?)

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

- other ideas ???