Data Grid
Document Actions
RLS Application Deploy
A Replica Location Service
(RLS) is a distributed registry service that records the locations of
data copies and allows discovery of replicas. We use the term logical fine name (LFN) to denote a unique logical identifier for desired data content. The function of a RLS is to identify zero or more physical copies of the content specified by an LFN. Each
physical copy is specified by a unique physical file name (PFN), such
as a GridFTP[4] URL, that specifies its location on a storage system.
This concept of a unique logical identifier for a desired data content
is applicable only within the context of a virtual organization (VO)[5]
that brings together users and resources in the pursuit of common goals.
A RLS maintains mappings between logical identifiers and target names
–Physical targets: Map to exact locations of replicated data
–Logical targets: Map to another layer of logical names,
allowing storage system to move data without informing the RLS. RLS was
designed and implemented in a collaboration between Globus
project and DataGrid project.
SRB Implement/Improvement
The SDSC Storage Resource Brokeris a client/servermiddleware that virtualizes data space by providing a unified view to multiple heterogeneous storage Resources over the network. SRB is a software that sits in between users and resources and provides a storage service by managing users, file locations, storage resources and metadata information.
3D Development/Deploy
- Oracle advanced replication
- Oracle CA Development
- Oracle, X.509 and VOMS
- VOMS is a service for centrally managing VO user's group membership and roles.
The information is transferred to user using digitally signed messages. The VO user then includes these signed messages into a proxy certificate for accessing the resources. - We would like to make it possible to authenticate and authorize to a DB with such a certificate. However the proxy certificate is not a regular X.509 certificate. It is a self-signed certificate, with additional fields carrying VOMS message.
- To achieve little need for user maintenance on db side, we would
like to see an ability to map VO roles to database some kind of
database identities.
This can be achieved using Oracle's Enterprise User Security together with
shared schema. - n usual situation with SSL auth. It would be achieved this way:
- User is authenticated with a SSL Cert by a database.
- DBMS looks for a local schema for this user.
- DBMS asks Oracle Internet Directory ( or other LDAP server with Oracle context) for user->schema/role mapping.
- If such exists DBMS assigns this user to a given schema and role.