What's new

This is the first release of lcg-CE that can be used in conjunction with the new glite-CLUSTER node type.

Configuration

A new lcg-CE configuration variable can be defined, which when set enables "cluster mode"; in cluster mode the publishing of information about clusters and subclusters by the lcg-CE is disabled. The node type glite-CLUSTER would need to be installed on either the lcg-CE itself or another machine.

In the default, non-cluster, mode the configuration and operation of the lcg-CE remains the same. i.e. a single cluster/subcluster will be published by the lcg-CE and cluster/subclusters with the same IDs should not be published by any glite-CLUSTER node that might be installed at the site.

In cluster mode there are some new yaim configuration variables which must be set in order to configure the lcg-CE. At the same time many of the previous non-cluster mode variables are no longer required. (The information should still be retained, but is provided by setting new variables when configuring the glite-CLUSTER node). Please consult the documentation to find out about them and the selection of the cluster mode itself.

If a glite-CLUSTER node is to be used with the lcg-CE on a separate machine then it becomes possible for VO managers who want to set their application tags to do so per subcluster, using the --sc option in the lcg-tags or lcg-ManageVOTag commands. In turn that requires that a user can discover the relevant subcluster name on a given worker node. The glite-wn-info command is used to do that using the configuration file ${GLITE_LOCATION}/etc/glite-wn-info.conf. Therefore the WNs should have their subcluster ID set in the configuration file. YAIM will do this if given the information in the WN_LIST file at the time the worker nodes are configured.

Known issues

If using cluster mode and installing the glite-CLUSTER node on the lcg-CE node the following "known issue" of glite-CLUSTER 3.1.4 is relevant: In case your new or reconfigured subclusters are named differently than before, the old directory in /opt/glite/var/info/<oldsubcluster> should be deleted, otherwise details of the old subcluster keep being published. See also the relase notes section of glite-CLUSTER 3.1.4.

The cluster unique ID (i.e. set with the CE_HOST_<host-name>_CLUSTER_UniqueID in cluster mode) must not contain upper case letters, i.e. it may contain only lower case alpha numeric, or the three characters '.', '_' and '-'.

When setting up the lcg-CE with a glite-CLUSTER node on a separate machine the VO application tag directories at lcgce:$EDG_LOCATION/var/info/ should be shared with cluster:$EDG_LOCATION/var/info/.

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

If you want to define the LCGCE_CLUSTER_MODE variable you have to set it in your site-info.def not in services/lcg-ce.