Directory and data management services API and protocol: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
* registration of a policy - microservices | * registration of a policy - microservices | ||
= Data logistics = | |||
* Specify lun + upload, download | |||
* replication | |||
* allocate space | |||
* data migration | |||
* object life times | |||
* advanced resource allocation | |||
* workflows | |||
* data-pathing | |||
* quotas | |||
= Data integrity = | |||
* fault tolerance | |||
* recover failed mappings | |||
* object integrity | |||
* fsck/format/default options | |||
= Security = | |||
* permissions | |||
* auth/authz | |||
* encryption | |||
= Misc = | |||
* locking file & byte range (Persistency) | |||
* versioning (?) | |||
* object semantics - versioning/copy-on-write/locking etc (?) | |||
* other ideas ??? | |||
Revision as of 16:48, 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
Data logistics
- Specify lun + upload, download
- replication
- allocate space
- data migration
- object life times
- advanced resource allocation
- workflows
- data-pathing
- quotas
Data integrity
- fault tolerance
- recover failed mappings
- object integrity
- fsck/format/default options
Security
- permissions
- auth/authz
- encryption
Misc
- locking file & byte range (Persistency)
- versioning (?)
- object semantics - versioning/copy-on-write/locking etc (?)
- other ideas ???