First version of glite-CLUSTER

This is the first release of glite-CLUSTER. It is a new node type that can publish information about clusters and subclusters in a site, referenced by any number of compute elements. However, it should not publish cluster/subcluster UniqueIDs which are already published by another node such as lcg-CE or creamCE. For instance since version 3.1.46 the lcg-CE can be configured in 'cluster mode' which will prevent it from publishing its own cluster/subcluster IDs and allow the glite-CLUSTER node to be used to do that. (The glite-CLUSTER node can be on the same machine as the lcg-CE or a separate one).

Please note also that the gLite 3.2 version of glite-CLUSTER will be released soon.

Configuration

Currently the creamCE yaim configuration has no option to disable the publication of its own cluster and subcluster IDs and so can not be directly configured to work with glite-CLUSTER. However see the release notes of glite-CLUSTER for SL5 for a set of manual steps to allow glite-CLUSTER to be used with creamCE.

Known issues

• There is a known issue when reconfiguring a glite-CLUSTER so that a subcluster ID is removed from the configuration. (e.g. a subcluster is completely removed or the subcluster's UniqueID is changed): Directories with the name of the old subcluster Unique IDs are not removed and need to be removed manually from the glite-CLUSTER node or they will continue to be published:

  cd $GLITE_LOCATION/var/info
  rm -rf old_subcluster_name

  where <old_subcluster_name> is the UniqueID of any subcluster which is no longer defined.

• The cluster and subcluster Unique IDs, set with

  CLUSTER_<cluster-identifier>_CLUSTER_UniqueID 

  SUBCLUSTER_<subcluster-identifier>_SUBCLUSTER_UniqueID

  must not contain upper case letters, i.e. they may contain only lower case alpha numeric characters and any of the three characters '.', '_' and '-'. The unique IDs must be globally unique, for instance base it on the DNS domain to ensure it will not collide with an ID at another site. However, the cluster Unique ID do not have to be unique with respect to subcluster Unique IDs. e.g. currently a cluster will only have one subcluster and the subcluster UniqueID may be the same as the cluster UniqueID.

• There should only be one subcluster defined per cluster. This is currently a restriction needed for correct operation of the workload management system.

• The variable CE_HOST_<ce name>_QUEUES should be set in the yaim cluster configuration file, but if it is missing yaim does not give a warning or error.