Note: This web site is only kept up to date for OSG Software 1.2 (VDT 2.0.0). If you are looking for information for the most recent release, the RPM-based OSG Software 3.0, please see the OSG documentation web site

Glue Schema and Information Providers in the VDT

VDT 1.1.10 and above have the Glue 1.1 Schema and Information providers. Although it is version 1.1, development has continued. To be clear about what the VDT contains, here are the specific versions that we have from the Glue CVS repository:

Glue CE Schema 1.1 (CVS version 1.2, 23-June-2003) (includes Core Schema, CE Schema and LCG-DataTAG Extensions for monitoring)
Glue SE Schema 1.1 (CVS version 1.5, 29-July-2003)
Glue CESEBind Schema 1.1 (CVS version 1.2, 29-July-2003)
Glue basic information providers 1.1 (CVS version 1.79, 25-July-2003)
A basic Glue static information setup, created by the VDT during installation.

The VDT installs the extended Glue schema, but only the basic Glue information providers. The extended Glue schema allows information about specific machines in your cluster. Currently, it requires a program named fmon to fill in this information. This program is not currently part of the VDT.

The Glue schema has a static portion. When the VDT installs the Glue schema, it attempts to fill in the static portion, but it is incomplete. You can extend the static portion by editing $VDT_LOCATION/globus/etc/glue-ce-static.ldif. There are several fields you should consider editing:

There is a line that begins "GlueClusterUniqueID=", and it is followed by the hostname that you installed on. You may wish to choose another unique ID. For example, an installation on my machine says:
```
dn: GlueSubClusterUniqueID=chopin.cs.wisc.edu, GlueClusterUniqueID=chopin.cs.wisc.edu, mds-vo-name=local, o=grid
```
I could change this to:
```
dn: GlueSubClusterUniqueID=uw-madison-cluster, GlueClusterUniqueID=chopin.cs.wisc.edu, mds-vo-name=local, o=grid
```
You may wish to choose other names for your GlueClusterName and your GlueSubClusterName.
There are some lines that have been commented out that indicate run-time environments. For example, you can see:
```
#Add your own run time environments here, if you like.
#GlueHostApplicationSoftwareRunTimeEnvironment: CMS-1.1.0
#GlueHostApplicationSoftwareRunTimeEnvironment: ATLAS-3.2.1
```
You can make a similar line that describes the software you have preinstalled on your system, so people can discover it. Of course, if you rely on static information to describe your dynamic environment, your users may be in for a surprise if the static description ever doesn't match reality.

Warning: if the Glue installation is updated (via "

pacman
-updateall

", your edits to this static information may be removed and placed in a backup file. You can retrieve these changes by looking at the old file.

Do you need more information about Glue? More information can be found online: