Difference: SystemAdministratorGuideForEMI1 (54 vs. 55)

Revision 552011-11-05 - MassimoSgaravatto

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

System Administrator Guide for CREAM for EMI-1 release

Line: 27 to 27
 If you plan to use LSF as batch system for your CREAM CE, you have to install and configure it before installing and configuring the CREAM software. Since LSF is a commercial software it can't be distributed together with the middleware.

If you plan to use GE as batch system for your CREAM CE, you have to install and configure it before installing and configuring the CREAM software. The CREAM CE integration was tested with GE 6.2u5 but it should work with any forked version of the original GE software. The support of the GE batch system software (or any of its forked versions) is out of the scope of this activity.

Added:
>
>
More information abut batch system integration is available in the relevant section.
 

0.1 Plan how to deploy the CREAM CE

0.1.1 CREAM CE and gLite-cluster

Line: 832 to 834
 
Changed:
<
<

Batch system integration

Grid Engine

Requirements

>
>

0.1 Batch system integration

0.1.1 Torque

0.1.1.1 Installation

If the CREAM-CE has to be also the torque server, install the emi-torque-server metapackage: yum install emi-torque-server

In all cases (Torque server in the CREAM-CE or in a different host) then install the emi-torque-utils metapackage: yum install emi-torque-utils

0.1.1.2 Configuration

Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for CREAM CE is available at CREAM CE: https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#cream_CE

The CREAM CE Torque integration is then configured running YAIM:

  • no cluster mode with CREAM-CE being also Torque server: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils
  • no cluster mode with CREAM-CE not being also Torque server: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_utils
  • cluster mode with glite-CLUSTER deployed on a different node with CREAM-CE being also Torque server: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils
  • cluster mode with glite-CLUSTER deployed on a different node with CREAM-CE not being also Torque server: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_utils
  • cluster mode with glite-CLUSTER deployed on the same node of the CREAM-CE with CREAM-CE being also Torque server : /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils -n glite-CLUSTER
  • cluster mode with glite-CLUSTER deployed on the same node of the CREAM-CE with CREAM-CE not being also Torque server : /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_utils -n glite-CLUSTER

0.1.2 LSF

0.1.2.1 Requirements

You have to install and configure the LSF batch system software before installing and configuring the CREAM software.

0.1.2.2 Installation

If you are running LSF, install the emi-lsf-utils metapackage: yum install emi-lsf-utils

0.1.2.3 Configuration

Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for CREAM CE is available at CREAM CE: https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#cream_CE

The CREAM CE LSF integration is then configured running YAIM:

  • no cluster mode: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n LSF_utils
  • cluster mode with glite-CLUSTER deployed on a different node: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n LSF_utils
  • cluster mode with glite-CLUSTER deployed on the same node of the CREAM-CE: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n LSF_utils -n glite-CLUSTER

0.1.3 Grid Engine

0.1.3.1 Requirements

  You have to install and configure the GE batch system software before installing and configuring the CREAM software. The CREAM CE integration was tested with GE 6.2u5 but it should work with any forked version of the original GE software. The support of the GE batch system software (or any of its forked versions) is out of the scope of this activity.
Line: 842 to 890
 
  1. CREAM CE must be installed in a separate node from the GE SERVER (GE QMASTER).
  2. CREAM CE must work as a GE submission host (use qconf -as <CE.MY.DOMAIN> in the GE QMASTER to set it up).
Changed:
<
<

Integration plugins

>
>

0.0.0.1 Integration plugins

  The GE integration with CREAM CE consists in deploying specific BLAH plugins and configure them to properly interoperate with Grid Engine batch system. The following GE BLAH plugins are deployed with CREAM CE installation: BUpdaterSGE, sge_hold.sh, sge_submit.sh, sge_resume.sh, sge_status.sh and sge_cancel.
Changed:
<
<

Instalation

>
>

0.0.0.1 Installation

 
Changed:
<
<
If you are running GE, install the emi-ge-utils metapackage: yum install emi-ge-utils
>
>
If you are running GE, install the emi-ge-utils metapackage: yum install emi-ge-utils
 
Changed:
<
<

Configuration

>
>

0.0.0.1 Configuration

  Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for CREAM CE and GE is available at
Line: 870 to 918
 
  1. BATCH_VERSION= <GE version>
Some sites use GE installations shared via NFS (or equivalent) in the CREAM CE. In order to prevent changes in that setup when YAIM is executed, define SGE_SHARED_INSTALL=yes in your site-info.def, otherwise YAIM may change your setup according to the definitions in your site-info.def.
Changed:
<
<
The CREAM CE GE integration in then configured running YAIM:
>
>
The CREAM CE GE integration is then configured running YAIM:
 
  • no cluster mode: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils
Changed:
<
<
  • in cluster mode with glite-CLUSTER deployed on a different node: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils
  • in cluster mode with glite-CLUSTER deployed on the same node of the CREAM-CE: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils -n glite-CLUSTER
>
>
  • cluster mode with glite-CLUSTER deployed on a different node: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils
  • cluster mode with glite-CLUSTER deployed on the same node of the CREAM-CE: /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils -n glite-CLUSTER

0.0.0.1 Important notes

 
Changed:
<
<

Important notes

File transfers
>
>
0.0.0.0.1 File transfers
  Besides the input/output sandbox files (transfered via GFTP) there are some other files that need to be transferred from/to the CREAM sandbox directory on the CE node to/from the Worker Node, namely:
  • The CREAM job wrapper and the user proxies, that are staged from the CE node to the WN where the job will run
Line: 901 to 950
 + system( 'scp', $localfile, "$remotemachine:$remotefile" ); } }
Changed:
<
<
GE accounting file
>
>
0.0.0.0.1 GE accounting file
  BUpdaterSGE needs to consult the GE accounting file to determine how did a given job ended. Therefore, the GE accounting file must be shared between the GE SERVER / QMASTER and the CREAM CE.
Changed:
<
<
Moreover, to guarantee that the accounting file is updated on the fly, the GE configuration should be tunned (using qconf -mconf) in order to add under the reporting_params the following definitions: accounting=true accounting_flush_time=00:00:00
>
>
Moreover, to guarantee that the accounting file is updated on the fly, the GE configuration should be tunned (using qconf -mconf) in order to add under the reporting_params the following definitions: accounting=true accounting_flush_time=00:00:00
 
Changed:
<
<
GE SERVER (QMASTER) tunning
>
>
0.0.0.0.1 GE SERVER (QMASTER) tuning
  The following suggestions should be implemented to achieve better performance when integrating with CREAM CE:
  1. The Cream CE machine must be set as a submission machine
 
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