Directory and data management services API and protocol: Difference between revisions
No edit summary |
|||
| Line 3: | Line 3: | ||
- Directory manipulation - opendir like interface | - Directory manipulation - opendir like interface | ||
(create,delete,move,walk) | (create,delete,move,walk) (Name service) | ||
- Open/close; obtain a handle/ release handle | - Open/close; obtain a handle/ release handle (Name service) | ||
- locking file & byte range | - locking file & byte range (Persistency) | ||
- Specify lun + upload, download | - Specify lun + upload, download (Data logistics) | ||
- get file mappings | - get file mappings (Name service) | ||
- replication | - replication (Data logistics) | ||
- fault tolerance | - fault tolerance (Data integrity) | ||
- permissions | - permissions (Security) | ||
- auth/authz | - auth/authz (Security) | ||
- allocate space | - allocate space (Data logistics) | ||
- data migration | - data migration | ||
Revision as of 16:02, 25 January 2008
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
- soft links - internal and external
- recover failed mappings
- encryption
- add arbitrary metadata ala xfs
- object integrity
- fsck/format/default options
- object life times
- advanced resource allocation
- workflows
- data-pathing
- registration of a micro-services framework
- quotas
- versioning
- file semantics - versioning/cow/locking etc
- other ideas ???