Data Breakout
OGSA Architecture –
databases
•
Eldas, OGSA-DAI and GridMiner implement a slightly old version of
OGSA / DAIS
– Architecture doc describes capabilities; DAIS explores details
•
Current OGSA / DAIS spec does not include:
– Extensibility (e.g. as used in e-Diamond)
– Packing of multiple tasks and multiple data sets
– Translation
•
Definitely need (* as noted in OGSA doc):
–
–
–
–
•
Data connection / third-party delivery*
Unique names for identifying data content and data instance*
Robust and integrated architecture*
Model of metadata for databases
Eldas and OGSA-DAI have OGSI, WSRF and WS-I interfaces
planned
– OGSA explicitly assumes WSRF
– Some resistance to this; a federated approach suggested
OGSA Architecture – Files
•
•
•
•
File Storage – GSM (SRM-like)
Directory structure – GFS
Replica Catalogs – OREP
Metadata Catalogs
– File stats (locking, mutability, ACLs)
– User attributes
• API for access – ADF (POSIX-like)
• Definitely need:
– Naming
– Data Movement
Web Service Interfaces
• SRM is not WS-I compliant (yet)
• Eldas supports message-level encryption
– https for Wed Services
– WS-Security for Grid services
• OGSA-DAI requires XSLT
• Other standards that we have to adhere to
– POSIX, Windows, NFS, FTP, Gzip, …
APIs: User commands
• Files: Explorer equivalent
– Including ls, tail, find, … ?
• Need to prioritise
– Quota management
– ACLs
• Files: Directories
– Familiar interface
• Databases: Query tool
– OGSA-DAI and Eldas provide GUI tools
– Quick query, schema inspection, etc
– No existing standard
• Databases: DBA Tools
– No existing standard
APIs: programming
interfaces
•
Files: SRM
– POSIX-like
• Need to prioritise
– plus management interface to handle scalable systems
•
Files: Directories
– Familiar interface
•
Files: Catalogs
– One-shot interface (because content unknown)
– Bulk operations
•
Databases:
– “OGSA-DAI client API”
• E.g. simple query
• Add to SAGA or form DAIS API group?
– Extensibility interface (client and server)
– Bulk operation and bulk data interface (client and server)