90 likes | 99 Views
This evaluation examines the Grid Information Service (GIS), its implementation through LDAP, and its use in the INFN organization. It also discusses the strengths and weaknesses of the current system and explores possible improvements with the Globus 1.1.3 release.
E N D
INFN “Grid Information Service” evaluation Giuseppe Lo Biondo - INFN Sez. Di Milano Giulietta Vita Finzi - INFN CNAF Padova June 16 2000
Grid Information Service (background). • GIS organizes in a coherent way information about computing resources in the Grid. • This information service is critical in Grid environments since it gives a dynamic view of computing resources. • The Metacomputing Directory Service (MDS) implements GIS through LDAP (Lightweight Directory Access Protocol / RFC 1777) as a uniform access protocol.
MDS at INFN • INFN (Istituto Nazionale di Fisica Nucleare) at the moment has an organizational MDS server (mds.infn.it:391), since the American MDS server was found to be almost unusable (long access times) from our test hosts. • It is based on Netscape Directory Server 4.1 on RedHat Linux 6.0. • At the moment it contains almost 208 entries (Distinguished Names) spanning 12 Organizational Units.
INFN MDS tools • A simple web interface allows tree browsing (http://bond.cnaf.infn.it/cgi-bin/mdsbrowse.pl) • A web form (http://bond.cnaf.infn.it/enroll.html) allows to ask for INFN department enrolment. • The enrolment procedure is borrowed from the enrolment scripts used by the US MDS administrators.
MDS service status • The MDS service is stable, it is serving globus 1.1.1 and 1.1.2 installations . Little maintenance is required and no problems (for the MDS itself) were found.
Globus LDAP schema evaluation • The Globus schema is very complete from the computing resources description perspective. • LDAP could also be used to store AAA (Accounting Authorisation,Authentication) data such as policies (ACLs), user certificates and CRLs (Certificate Revocation Lists).
(Known) Problems Weaknesses of this model concerns: • Monolithic world wide DIT (Directory Information Tree) and high number of clients updates on the server can be an overkill. • Single point of failure (INFN LDAP replica server needed.., not yet implemented). • This problems seem to be addressed in the current Globus release (1.1.3) with a more distribuited environment and a pull model for information retrieval.
Globus 1.1.3 (conclusions) • Globus 1.1.3 seems to address DIT update and redundancy problems, it could still be useful to: • Have user data in the DIT for AAA purposes • Have a representation for mass storage resources on the Grid. • Have the possibility to glue together various GIISes through a GIIS meta-index. • Establish a collaborative effort with OpenLDAP to avoid the usage of a modified OpenLDAP version.