Providing information

GIP is the component that accepts data. It takes dynamic and static information in the LDIF format and merges them: attributes from the dynamic LDIF will override the static LDIF values. After the data has been merged, it checks that the resulting LDIF is well-formed LDIF and validates it against the GLUE Schema.

Dynamic and static information is provided to GIP in different ways. This is described in the following sections.

[return to top]

Providing Static information to GIP

[root@dcache-node] # ls /opt/glite/etc/gip/ldif/
static-file-dSE.ldif  static-file-SE.ldif  stub-resource.ldif

The two important files are static-file-dSE.ldif and static-file-SE.ldif. Each contains a series of objects. The following is an example of the LDIF representation of an LDAP object:

dn: GlueSEControlProtocolLocalID=srm_v2@dcache-node.fzk.de,GlueSEUniqueID=dcache-node.fzk.de
,mds-vo-name=resource,o=grid
objectClass: GlueSETop
objectClass: GlueSEControlProtocol
objectClass: GlueKey
objectClass: GlueSchemaVersion
GlueSEControlProtocolLocalID: srm_v2@dcache-node.fzk.de
GlueSEControlProtocolType: SRM
GlueSEControlProtocolEndpoint: httpg://dcache-node.fzk.de:8443/srm/managerv2
GlueSEControlProtocolCapability: space allocation
GlueSEControlProtocolCapability: space management
GlueSEControlProtocolVersion: 2.2.0
GlueChunkKey: GlueSEUniqueID=dcache-node.fzk.de
GlueSchemaVersionMajor: 1
GlueSchemaVersionMinor: 3

These files can be manually edited by the administrator to include additional attributes or objects. Many of the attributes can be customised to express details about the site.

Make a backup

These files will be over written by the dcacheConfigure.sh script. It is important to keep a backup copy whenever they are edited.

[return to top]

Providing Dynamic information

Information about dCache's current status is queried by a small application. This application connects to the InfoProvider cell to gather the current status of dCache. It then emits this information as a small amount of LDIF data, replacing the corresponding LDIF in the static LDIF files.

If this application isn't able to run, or is unable to gather information about dCache then it will not emit LDIF data, so exposing the default values in the static LDAP files.

The current dynamic information provider has some limitations. We are in the process of evaluating a new information system, which we anticipate being part of the next major release of dCache.