Directory and data management services API and protocol: Difference between revisions

From ReddNet
Jump to navigation Jump to search
(New page: 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 framework...)
 
No edit summary
 
(5 intermediate revisions by 2 users not shown)
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, ...)  


- Directory manipulation - opendir like interface
Are there aspects of logistical networking that this list is missing?
(create,delete,move,walk)


- Open/close; obtain a handle/ release handle
= 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
= Data logistics =
* Specify lun + upload, download
* replication
* allocate space
* data migration
* object life times
* advanced resource allocation
* workflows
* data-pathing
* quotas


- Specify lun + upload, download
= Data integrity =
* fault tolerance
* recover failed mappings
* object integrity
* fsck/format/default options


- get file mappings
= Security =
* permissions
* auth/authz
* encryption


- replication
= Misc =
 
* locking file & byte range (Persistency)
- fault tolerance
* versioning (?)
 
* object semantics - versioning/copy-on-write/locking etc (?)
- permissions
* other ideas ???
 
- auth/authz
 
- allocate space
 
- 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 ???

Latest revision as of 17:09, 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, ...)

Are there aspects of logistical networking that this list is missing?

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 ???
Retrieved from "http://www.reddnet.org/mwiki/index.php?title=Directory_and_data_management_services_API_and_protocol&oldid=3185"