Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
System Administrator Guide for CREAM for EMI-1 release | ||||||||
Line: 32 to 32 | ||||||||
glite-CLUSTER is a node type that can publish information about clusters and subclusters in a site, referenced by any number of compute elements. In particular it allows to deal with sites having multiple CREAM CE nodes and/or multiple subclusters (i.e. disjoint sets of worker nodes, each set having sufficiently homogeneous properties). | ||||||||
Changed: | ||||||||
< < | In Glue1, batch system queues are represented through GlueCE objectclasses. Each GlueCE refers to a Cluster, which can be composed by one or more SubClusters. However the gLite WMS requires the publication of exactly one SubCluster per Cluster (and hence per batch queue). | |||||||
> > | In Glue1, batch system queues are represented through GlueCE objectclasses. Each GlueCE refers to a Cluster, which can be composed by one or more SubClusters. However the gLite WMS requires the publication of exactly one SubCluster per Cluster (and hence per batch queue). | |||||||
Thus sites with heterogeneous hardware have two possible choices:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
However, without the use of the gLite-cluster, YAIM allows configuring a single Cluster per CREAM head node. A second problem, addressed by gLite-cluster arises for larger sites which install multiple CE headnodes submitting to the same | ||||||||
Changed: | ||||||||
< < | batch queues for redundancy or load-balancing. Without the use of gLite-cluster, YAIM generates a separate Cluster/SubCluster pair for each head node even though they all describe the same hardware. This causes no problems for job submission, but by default would overcount the installed capacity at the site by a multiple of the number of SubClusters. The workaround, before introducing the gLite-cluster, was to publish zero values for the installed capacity from all but one of the nodes (but this is clearly far from being an ideal solution). | |||||||
> > | batch queues for redundancy or load-balancing. Without the use of gLite-cluster, YAIM generates a separate Cluster/SubCluster pair for each head node even though they all describe the same hardware. This causes no problems for job submission, but by default would overcount the installed capacity at the site by a multiple of the number of SubClusters. The workaround, before introducing the gLite-cluster, was to publish zero values for the installed capacity from all but one of the nodes (but this is clearly far from being an ideal solution). | |||||||
Changed: | ||||||||
< < | The glite-CLUSTER node addresses this issue. It contains a subset of the functionality incorporated in the CREAM node types: the publication of the Glue1 GlueCluster and its dependent objects, the publication of the Glue1 GlueService object for the GridFTP endpoint, and the directories which store the RunTimeEnvironment tags, together with the YAIM functions which configure them. | |||||||
> > | The glite-CLUSTER node addresses this issue. It contains a subset of the functionality incorporated in the CREAM node types: the publication of the Glue1 GlueCluster and its dependent objects, the publication of the Glue1 GlueService object for the GridFTP endpoint, and the directories which store the RunTimeEnvironment tags, together with the YAIM functions which configure them. | |||||||
So, gLite-CLUSTER should be considered: | ||||||||
Line: 54 to 54 | ||||||||
When configuring a gLite-cluster, please consider that there should be: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
glite-CLUSTER can be deployed in the same host of a CREAM-CE or in a different one. | ||||||||
Changed: | ||||||||
< < | The following deployment models are therefore possible for a CREAM-CE: | |||||||
> > | The following deployment models are possible for a CREAM-CE: | |||||||
| ||||||||
Line: 377 to 380 | ||||||||
0.0.1 Installation of the CREAM CLI | ||||||||
Changed: | ||||||||
< < | The CREAM CLI is part of the EMI-UI. To install it please refer to xxx. | |||||||
> > | The CREAM CLI is part of the EMI-UI. To install it please refer to https://twiki.cern.ch/twiki/bin/view/EMI/EMIui#Client_Installation_Configuratio . | |||||||
0.1 Configuration | ||||||||
Line: 536 to 539 | ||||||||
Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for glite-CLUSTER is available at https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#CLUSTER | ||||||||
Deleted: | ||||||||
< < | You should have:
| |||||||
0.0.0.1 Run yaim | ||||||||
Line: 646 to 638 | ||||||||
0.0.1 Configuration of the CREAM CLI | ||||||||
Changed: | ||||||||
< < | The CREAM CLI is part of the EMI-UI. To configure it please refer to xxx. | |||||||
> > | The CREAM CLI is part of the EMI-UI. To configure it please refer to https://twiki.cern.ch/twiki/bin/view/EMI/EMIui#Client_Installation_Configuratio. | |||||||
0.0.1 Manual configuration |