Directory and data management services API and protocol: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
Functional areas can be added, and discussions of how each function applies to different frameworks (lStore, Lodn, ...) | Functional areas can be added, and discussions of how each function applies to different frameworks (lStore, Lodn, ...) | ||
= Name service = | |||
(create,delete,move,walk) | * 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) | - locking file & byte range (Persistency) | ||
| Line 11: | Line 17: | ||
- Specify lun + upload, download (Data logistics) | - Specify lun + upload, download (Data logistics) | ||
- replication (Data logistics) | - replication (Data logistics) | ||
| Line 25: | Line 30: | ||
- data migration (Data logistics) | - data migration (Data logistics) | ||
- recover failed mappings (Data integrity) | - recover failed mappings (Data integrity) | ||
| Line 31: | Line 35: | ||
- encryption (Security) | - encryption (Security) | ||
- object integrity (Data integrity) | - object integrity (Data integrity) | ||
| Line 45: | Line 48: | ||
- data-pathing (Data logistics) | - data-pathing (Data logistics) | ||
- quotas (Data logistics) | - quotas (Data logistics) | ||
Revision as of 16:45, 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, ...)
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 ???