Globus and LDAP

The well known Globus toolkit is based on LDAP.

However, the LDAP architecture is appropriate to store static information, like the number of processors in a cluster, or the size of a disk partition.

When data are more volatile, the LDAP architecture is the wrong choice: it is unsuitable to support frequent write operations.

Examples of characteristics that induce frequent writes:

• available computing power on a computing resource (e.g. number of idle nodes in a cluster);
• percent of free space in a partition;
• average roundtrip time on a link

In all these cases the LDAP architecture suffers serious performance and scalability problems.

next: From Globus LDAP to R-GMA SQL

previous: From NWS to LDAP

up: A modular approach to Grid Connectivity Monitoring

index