Difference: CreamGlue2 (3 vs. 4)

Revision 42011-06-22 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamInformationService"

Glue2 support in CREAM

Line: 9 to 9
 

0.1 CREAM CE in no cluster mode

Changed:
<
<
If the CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.
>
>
We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

If a CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.

  The ServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement.

0.1 CREAM CE in cluster mode

Changed:
<
<
If instead the CREAM CE is configured in cluster mode:
>
>
Sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

If a CREAM CE is configured in cluster mode:

 
  • The resource BDII running on the CREAM CE publishes just the Endpoint and the AccessPolicy objectclasses
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node
Changed:
<
<
>
>
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
 

-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback