0.0.0.1 Munge Configuration

Torque makes use of munge as a inter node authentication method. To enable munge on your torque cluster:

• Install the munge package on your pbs_server and submission hosts in your cluster.
• On one host generate a key with /usr/sbin/create-munge-key
• Copy the key, /etc/munge/munge.key to your in the same location of the TORQUE server host and submission hosts on your cluster
• Start the munge daemon on these nodes.

  service munge start && chkconfig munge on

0.0.0.1 Installation of the batch system specific software

After the installation of the glite-CLUSTER metapackage it is necessary to install the batch system specific metapackage(s).

On sl5_x86_64 and sl6_x86_64:

• If you are running Torque, install the emi-torque-utils metapackage:

yum install emi-torque-utils

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

yum install emi-lsf-utils

* If you are running GE, install the emi-ge-utils metapackage:

yum install emi-ge-utils

0.0.0.1 Manual Tuning

YAIM modules for TORQUE server don't configure all the parameters available for a queue. Several parameters must be set up manually otherwise default values (999999999) are published. The parameters are:

• resources_default.walltime
• resources_max.walltime
• resources_default.cput
• resources_default.pcput
• resources_max.cput
• resources_max.pcput
• resources_default.procct
• resources_max.procct
• max_queuable
• max_running
• Priority

The following table shows how GLUE1 and GLUE2 attributes are calculated from the parameters above

• How to define a policy in the ARGUS box:
  • Create a file policy.txt

            # cat policy.txt
            resource "http://pd.infn.it/cream-18" {
              obligation "http://glite.org/xacml/obligation/local-environment-map" {}
              action ".*" {
                  rule permit { vo = "XYZ" }
              }
            }
           

  • Add the policy form file

             pap-admin apf policy/policy.txt
           

  • Clear pepd cache

            /etc/init.d/argus-pepd clearcache
           

  • Re-load policies:

            /etc/init.d/argus-pdp reloadpolicy
           

• copy the new certificate (i.e. hostcert.pem, hostkey.pem) into the /etc/grid-security and $GLITE_HOME_DIR/.certs (NB: the glite home directory may be located in /home/glite/.certs/ or /var/glite/.certs/, depending if the CREAM installation has been done as EMI-1 upgrade or not) directories
• make a copy of the new certificate as follows:

• • glite-lb-locallogger

0.0.0.1 Install the host certificate

0.0.0.0.1 What to do in case of host certificate update

via YAIM:

• copy the new certificate (i.e. hostcert.pem, hostkey.pem) into the /etc/grid-security directory
• set the proper mode and ownerships doing:

chown root.root /etc/grid-security/hostcert.pem
chown root.root /etc/grid-security/hostkey.pem
chmod 600 /etc/grid-security/hostcert.pem
chmod 400 /etc/grid-security/hostkey.pem

• reconfigure CREAM via YAIM

by manually:

• copy the new certificate (i.e. hostcert.pem, hostkey.pem) into the /etc/grid-security and /home/glite/.certs/ directories
• make a copy of the new certificate as following:

cp /etc/grid-security/hostcert.pem /etc/grid-security/tomcat-cert.pem
cp /etc/grid-security/hostkey.pem /etc/grid-security/tomcat-key.pem

• set the proper mode and ownerships doing:

chown root.root /etc/grid-security/hostcert.pem
chown root.root /etc/grid-security/hostkey.pem
chown root.root /etc/grid-security/tomcat-cert.pem
chown root.root /etc/grid-security/tomcat-key.pem
chown root.root /home/glite/.certs/hostcert.pem
chown root.root /home/glite/.certs/hostkey.pem
chmod 600 /etc/grid-security/hostcert.pem
chmod 400 /etc/grid-security/hostkey.pem
chmod 600 /etc/grid-security/tomcat-cert.pem
chmod 400 /etc/grid-security//tomcat-key.pem
chmod 600 /home/glite/.certs/hostcert.pem
chmod 400 /home/glite/.certs/hostkey.pem

• restart the following services:
  • tomcat5 on SL5 (or tomcat6 on SL6)
  • globus-gridftp
  • LB

• CREAM-CE can be configured without worrying about the glite-CLUSTER node. This can be useful for small sites who don't want to worry about cluster/subcluster configurations because they have a very simple setup. In this case CREAM-CE will publish a single cluster/subcluster. This is called no cluster mode. This is done as described below by defining the yaim setting CREAM_CLUSTER_MODE=no (or by no defining at all that variable).
• CREAM-CE can work on cluster mode using the glite-CLUSTER node type. This is done as described below by defining the yaim setting CREAM_CLUSTER_MODE=yes. The CREAM-CE can be in the same host or in a different host wrt the glite-CLUSTER node.

• for EPEL5:

• for EPEL6:

    http://www.nic.funet.fi/pub/mirrors/fedora.redhat.com/pub/epel/6/x86_64/ 

• for EPEL5 on x86_64:

wget http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-X-Y.noarch.rpm
rpm -Uvh epel-release-X-Y.noarch.rpm

• for EPEL6 on x86_64:

wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-X-Y.noarch.rpm
rpm -Uvh epel-release-X-Y.noarch.rpm

• for EPEL5:

[extras]
name=epel
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch
protect=0

• for EPEL6:

0.1 CREAM CE update

To update the CREAM CE from EMI-2 Update x to EMI-2 Update y:

• Run yum update
• Reconfigure via yaim

wget http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl6/x86_64/base/emi-release-2.0.0-1.sl6.noarch.rpm
yum install ./emi-release-2.0.0-1.sl6.noarch.rpm

0.0.1 Installation of the EDGI connector

If you want to install the EDGI connector, after the installation of the CREAM CE metapackage it is necessary to install two other packages. On sl5_x86_64 this can be done issuing:

yum install edgiexecutor glite-yaim-edgi-bridge

Information for configuration is then available in the man page yaim-edgi-bridge(1) shipped in the glite-yaim-edgi-bridge package.

The EDGI connector packages for the time being are only available for sl5_x86_64.

0.0.0.1 Using btools

When the new blparser is used, it is possible to integrate the Bupdater process with the btools package implemented at Cern in order to improve performance.

To enable such integration, after having configured via yaim add the following lines in /etc/blah.config:

bupdater_use_btools=yes
bupdater_btools_path=/usr/local/bin

Then restart the blparser:

service glite-ce-blah-parser restart

0.0.1 EMI Execution Service

Starting with EMI-2 release, CREAM supports the EMI Execution Service (EMI-ES for short) specification.

So, besides deploying the usual legacy interface, it is also possible to install the EMI-ES interface. By default this EMI-ES is not deployed. If you want to install it, before configuring via yaim make sure that the yaim variable USE_EMIES is set to true.

The limiter script is run every 10 minutes.

To disable the limiter, it is necessary to edit the CREAM configuration file /etc/glite-ce-cream/cream-config.xml setting JOB_SUBMISSION_MANAGER_ENABLE to false and restarting tomcat.

The values that are currently taken into account are the following:

If needed, the thresholds can be modified editing the configuration file /etc/glite-ce-cream/cream-config.xml.

If needed, the limiter script can be easily augmented to take into account some other parameters.

To check if job submissions on a specific CREAM CE are allowed, the command glite-ce-allowed-submission can be used.

It is possible to resume the job submission calling the proper operation ( glite-ce-enable-submission).

E.g.:

> glite-ce-disable-submission grid006.pd.infn.it:8443
Operation for disabling new submissions succeeded
>
> glite-ce-allowed-submission grid006.pd.infn.it:8443
Job Submission to this CREAM CE is disabled
>
> glite-ce-enable-submission grid006.pd.infn.it:8443
Operation for enabling new submissions succeeded
>
> glite-ce-allowed-submission grid006.pd.infn.it:8443
Job Submission to this CREAM CE is enabled

• SL6 64 bit

• for sl5_x86_64 and sl6_x86_64: yum install emi-torque-server

• for sl5_x86_64 and sl6_x86_64: yum install emi-torque-utils

rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-5.noarch.rpm

JobDBAdminPurger.sh  [-c|--conf CREAMConfPath] [-j|--jobIds jobId1:jobId2:...] | [-f|--filejobIds filenameJobIds] | [-s|--status statusType0,deltaTime:statusType1:...] [-h|--help]

Options:

• -c | --conf : the CREAM conf file (to be specified only if it is not the standard value /etc/glite-ce-cream/cream-config.xml)
• -j | --jobids: the IDs (list of values separated by ':') of the jobs to be purged
• -f | --filejobIds: the file containing a list of jobids (one per line) to be purged
• -s | --status: the list of state,deltatime (list of values separated by ':') of the jobs to be purged. A job is purged if it is in specified state for more that deltatime days. deltatime can be omitted (which means that all jobs in that status will be purged). The possible states are:

• REGISTERED
• PENDING
• IDLE
• RUNNING
• REALLY-RUNNING
• CANCELLED
• HELD
• DONE-OK
• DONE-FAILED
• PURGED
• ABORTED

Examples:

JobDBAdminPurger.sh  -j CREAM217901296:CREAM324901232

JobDBAdminPurger.sh  -s registered:pending:idle

JobDBAdminPurger.sh  -s registered,3:pending:idle,5

JobDBAdminPurger.sh  -c /etc/glite-ce-cream/cream-config.xml --status registered:idle

JobDBAdminPurger.sh  --jobIds CREAM217901296:CREAM324901232

JobDBAdminPurger.sh  -f /tmp/jobIdsToPurge.txt

Please note that this script should be run just to clean the CREAM DB in case of problems (i.e. jobs reported in a non terminal status while this is not the case)

Please also note that this script purges jobs from the CREAM DB. The relevant job sandbox directories are also deleted.

• for SL5_x86_64: 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:

• for SL5_x86_64: yum install emi-torque-utils

TBC

0.0.0.1 Yaim Configuration

Set your siteinfo.def file, which is the input file used by yaim.

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.0.1 LSF

0.0.1.1 Requirements

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

0.0.1.2 Installation

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

• for sl5_x86_64: yum install emi-lsf-utils

0.0.1.3 Yaim Configuration

Set your siteinfo.def file, which is the input file used by yaim.

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.0.2 Grid Engine

0.0.2.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.

Before proceeding, please take note of the following remarks:

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).

0.0.2.2 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.

0.0.2.3 Installation

If you are running GE, install the emi-ge-utils metapackage:

• for sl5_x86_64: =yum install emi-ge-utils

0.0.2.4 Yaim 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

• CREAM CE: https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#cream_CE
• SGE / GE Utils: https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#SGE_GE_utils

1. BLPARSER_WITH_UPDATER_NOTIFIER= "true"
2. JOB_MANAGER= sge
3. CE_BATCH_SYS= sge
4. SGE_ROOT= <Path to your SGE installation>. Default: "/usr/local/sge/pro"
5. SGE_CELL= <Path to your SGE CELL>. Default: "default"
6. SGE_QMASTER= <SGE QMASTER PORT>. Default: "536"
7. SGE_EXECD= <SGE EXECD PORT>. Defaul: "537"
8. SGE_SPOOL_METH= "classic"
9. BATCH_SERVER= <FQDN of your QMASTER>
10. BATCH_LOG_DIR= <Path for the GE accounting file>
11. BATCH_BIN_DIR= <Path for the GE binaries>
12. BATCH_VERSION= <GE version>

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
• 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.2.5 Important notes

0.0.2.5.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
• The standard output and error files of the Cream job wrapper, that are copied from the WN to the CE when the job completes its execution.

1. Copy the sge_filestaging file to all your WNs (or to a shared directory mounted on your WNs)
2. Add <path>/sge_filestaging --stagein and <path>/sge_filestaging --stageout to your prolog and epilog defined in GE global configuration (use qconf -mconf), or alternatively, in each queue configuration (qconf -mq <QUEUE>).
3. If you do not share the CREAM sanbox area between the CREAM CE node and the Worker Node, the sge_filestaging file requires configuring the ssh trust between CE and WNs.
4. If you share the CREAM sanbox area between the CREAM CE node and the Worker Node, the sge_filestaging has to be changed according to:
   

# diff -Nua sge_filestaging.modified sge_filestaging.orig
--- sge_filestaging.modified    2010-03-25 19:38:11.000000000 +0000
+++ sge_filestaging.orig    2010-03-25 19:05:43.000000000 +0000

if ( $STAGEIN ) { - system( 'cp', $remotefile, $localfile ); + system( 'scp', "$remotemachine:$remotefile", $localfile ); } else { - system( 'cp', $localfile, $remotefile" ); + system( 'scp', $localfile, "$remotemachine:$remotefile" ); } }

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.

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

0.0.0.0.2 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
2. The GE QMASTER configuration should have the definition execd_params INHERIT_ENV=false (use qconf -mconf to set it up). This setting allows to propagate the environment of the submission machine (CREAM CE) into the execution machine (WN).

1 Postconfiguration

Have a look at the Known issue page to check if some postconfigurations are needed.

2 Operating the system

2.1 Tomcat configuration guidelines

In /etc/tomcat5/tomcat5.conf, there are some settings related to heap. They are in the JAVA_OPTS setting (see -Xms and -Xmx).

It is suggested to customize such settings taking into account how much physical memory is available, as indicated in the following table (which refers to 64bit architectures):

After having done the changes, it is necessary to restart tomcat

2.2 MySQL database configuration guidelines

Default values of some MySQL settings are likely to be suboptimal especially for large machines. In particular some parameters could improve the overall performance if carefully tuned.
In this context one relevant parameter to be set is the innodb_buffer_poll_size which specifies the size of the buffer pool (the default value is 8MB).

The benefits obtained by using a proper value for this parameter are principally: an appreciable performance improving and the reduced amount of disk I/O needed for accessing the data in the tables. The optimal value depends on the amount of physical memory and the CPU architecture available in the host machine.

The maximum value depends on the CPU architecture, 32-bit or 64-bit. For 32-bit systems, the CPU architecture and operating system sometimes impose a lower practical maximum size.
Larger this value is set, less disk I/O is needed to access data in tables. On a dedicated database server, it is possible to set this to up to 80% of the machine physical memory size.
Scale back this value whether one of the following issues occur:

• competition for physical memory might cause paging in the operating system;
• innoDB reserves additional memory for buffers and control structures, so that the total allocated space is approximately 10% greater than the specified size.

Example:

[mysqld]
innodb_buffer_pool_size=512MB

After that, it's necessary to restart the mysql service for applying the change:

/etc/init.d/mysqld restart

Finally, the following sql command (root rights are needed) could be used for checking if the new value was applied successfully:

SHOW VARIABLES like 'innodb_buffer_pool_size';

2.3 MySQL database: How to resize Innodb log files

If the following error occurs (see the mysql log file: /var/log/mysqld.log)

InnoDB: ERROR: the age of the last checkpoint is ,
InnoDB: which exceeds the log group capacity .
InnoDB: If you are using big BLOB or TEXT rows,you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.

then you must resize the innodb log files.

Follow these steps:

• check for the value of the innodb_log_file_size.

SHOW VARIABLES  like "innodb_log_file_size"; 

• Stop the MySQL server and make sure it shuts down without any errors. You can have a look at the error log to see if there are no errors.

service mysqld stop

• Once the server has stopped, edit the configuration file ( /etc/my.cnf) and insert or change the value of innodb_log_file_size to your desired value (64M should be a proper value). Example:

[mysqld]
innodb_log_file_size=64M

• Move the log file sizes ib_log* to some place out of the the directory where the log files reside. Example:

mv /var/lib/mysql/ib_logfile* /tmp

• Now restart the server.

service mysqld start

• Check for errors in /var/log/mysqld.log file

• Verify the correct size of the log files

ls -lrth /var/lib/mysql/ib_logfile*

2.4 How to start the CREAM service

For sl5_x86_64:

/etc/init.d/tomcat5 start

In case the new BLAH blparser is used, this will also start it (if not already running).

If for some reason it necessary to explicitly start the new BLAH blparser, the following command can be used:

/etc/init.d/glite-ce-blah-parser start

If instead the old BLAH blparser is used, before starting tomcat it is necessary to start it on the BLPARSER_HOST using the command:

/etc/init.d/glite-ce-blah-parser start

To stop the CREAM service, it is just necessary to stop the CREAM container.

For sl5_x86_64:

/etc/init.d/tomcat5 stop

2.5 Daemons

Information about daemons running in the CREAM CE is available in TBC

2.6 Init scripts

Information about init scripts in the CREAM CE is available in the TBC

2.7 Configuration files

Information about configuration files in the CREAM CE is available in TBC

2.8 Log files

Information about log files in the CREAM CE is available in TBC

2.9 Network ports

Information about ports used in the CREAM CE is available in TBC

2.10 Cron jobs

Information about cron jobs used in the CREAM CE is available in TBC

2.11 Security related operations

2.11.1 How to enable a certain VO for a certain CREAM CE in Argus

Let's consider that a certain CREAM CE has been configured to use ARGUS as authorization system.

Let's suppose that we chose http://pd.infn.it/cream-18 as the id of the CREAM CE (i.e. yaim variable CREAM_PEPC_RESOURCEID is http://pd.infn.it/cream-18).

On the ARGUS box (identified by the yaim variable ARGUS_PEPD_ENDPOINTS) to enable the VO XYZ, it is necessary to define the following policy:

resource "http://pd.infn.it/cream-18" {
    obligation "http://glite.org/xacml/obligation/local-environment-map" {}
    action ".*" {
        rule permit { vo = "XYZ" }
    }
}

2.11.2 Security recommendations

Security recommendations relevant for the CREAM CE is available in TBC

2.11.3 How to block/ban a user

Information about how to ban users is available in TBC

2.11.4 How to block/ban a VO

To ban a VO, it is suggested to reconfigure the service via yaim without that VO in the siteinfo.def

2.11.5 How to define a CREAM administrator

A CREAM administrator (aka super-user) can manage (e.g. cancel, check the status, etc.) also the jobs submitted by other people.

Moreover he/she can issue some privileged operations, in particular the ones to disable the new job submissions ( glite-ce-disable-submission) and then to re-enable them ( glite-ce-disable-submission)

To define a CREAM CE administrator for a specific CREAM CE, the DN of this person must be specified in the /etc/grid-security/admin-list of this CREAM CE node, e.g.:

"/C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto"

Please note that including the DN between " is important

2.12 Input and Output Sandbox files transfer between the CREAM CE and the WN

The input and output sandbox files (unless they have to be copied from/to remote servers) are copied between the CREAM CE node and the Worker Node.

These files transfers can be done in two possible ways:

• Using gridftp
• Using the staging capabilities of the batch system

• GSIFTP to use gridftp. This is the default value
• LRMS to use the staging capabilities of the batch system

2.13 Sharing of the CREAM sandbox area between the CREAM CE and the WN

Besides the input/output sandbox files 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:

• The CREAM job wrapper and the user proxies, that are staged from the CE node to the WN where the job will run
• The standard output and error files of the Cream job wrapper, that are copied from the WN to the CE when the job completes its execution.

• Use the staging capabilities of the batch system (e.g. for Torque this requires configuring the ssh trust between CE and WNs)
• Share the CREAM sanbox area between the CREAM CE node and the Worker Node and configure appropriately the batch system

• If you want to have several CREAM CEs sharing the same WNs, you need to mount each CE sandbox area to a different mount point on the WN, such as /cream_sandbox/ce_hostname.

• The CREAM sandbox directory name (default /var/cream_sandbox) can be changed using the yaim variable CREAM_SANDBOX_DIR

2.13.1 Sharing of the CREAM sandbox area between the CREAM CE and the WN for Torque

When Torque is used as batch system, to share the CREAM sandbox area between the CREAM CE node and the WNs:

• Mount the cream_sandbox directory also in the WNs. Let's assume that in the CE node the cream sandbox directory is called /var/cream_sandbox and on the WN is mounted as /cream_sandbox)
• On the WNs, add the following to the Torque client config file (generally /var/spool/pbs/mom_priv/config):

$usecp <CE node>://var/cream_sandbox /cream_sandbox

This $usecp line means that every time Torque will have to copy a file from/t the cream_sandbox directory on the CE (which is the case during the stage in/stage out phase), it will have to use a cp from /cream_sandbox instead.

2.14 Self-limiting CREAM behavior

CREAM is able to protect itself if the load, memory usage, etc. is too high. This happens disabling new job submissions, while the other commands are still allowed.

The whole stuff is implemented via a limiter script ( /usr/bin/glite_cream_load_monitor) very similar to the one used in the WMS.

Basically this limiter script check the values for some system and CREAM specific parameters, and compare them against some thresholds. If one or more threshold is exceeded, new job submissions get disabled. If a new submission is attempted when submissions are disabled, an error message is returned, e.g.:

TBC

2.15 How to drain a CREAM CE

The administrator of a CREAM CE can decide to drain a CREAM CE, that is disabling new job submissions while allowing the other commands. This can be useful for example because of scheduled shutdown of the CREAM CE.

This can be achieved via the glite-ce-disable-submission command (provided by the CREAM CLI package installed on the UI), that can be issued only by a CREAM CE administrator, that is the DN of this person must be listed in the /etc/grid-security/admin-list file of the CE.

If newer job submissions are attempted, users will get an error message such as:

TBC

2.16 How to trace a specific job

To trace a specific job, first of all get the CREAMjobid.

If the job was submitted through the WMS, you can get its CREAMjobdid in the following way:

glite-wms-job-logging-info -v 2 <gridjobdid> | grep "Dest jobid"

If the job is not yours and you are not LB admin, you can get the CREAMjobid of that gridjobid if you have access to the CREAM logs doing:

grep <gridjobid> /var/log/cream.glite-ce-cream.log*

Grep the "last part" of the CREAMjobid in the CREAM log file (e.g. if the CREAMjobid is https://cream-07.pd.infn.it:8443/CREAM383606450 considers CREAM383606450):

grep CREAM383606450 /var/log/cream/glite-ce-cream.log*

This will return all the information relevant for this job

2.17 How to check if you are using the old or the new blparser

If you want to quickly check if you are using the old or the new BLAH Blparser, do a grep registry blah.config. If you see something like:

# grep registry blah.config
job_registry=/var/blah/user_blah_job_registry.bjr

you are using the new BLAH blparser. Otherwise you are using the old one.

2.18 Job purging

Purging a CREAM job means removing it from the CREAM database and removing from the CREAM CE any information relevant for that job (e.g. the job sandbox area).

When a job has been purged, it is not possible to manage it anymore (e.g. it is not possible to check anymore its status).

A job can be purged:

• Explicitly by the user who submitted that job, using e.g. the glite-ce-job-purge command provided by the CREAM CLI

• Automatically by the automatic CREAM job purger, which is responsible to purge old - forgotten jobs, according to a policy specified in the CREAM configuration file ( /etc/glite-ce-cream/cream-config.xml).

For jobs submitted to a CREAM CE through the WMS, the purging is done by the ICE component of the WMS when it detects the job has reached a terminal status. The purging operation is not done if in the WMS conf file ( /etc/glite_wms.conf) the attribute purge_jobs in the ICE section is set to false.

2.18.1 Automatic job purging

The automatic CREAM job purger is responsible to purge old - forgotten jobs, according to a policy specified in the CREAM configuration file ( /etc/glite-ce-cream/cream-config.xml).

This policy is specified by the attribute JOB_PURGE_POLICY.

For example, if JOB_PURGE_POLICY is the following:

<parameter name="JOB_PURGE_POLICY" value="ABORTED 1 days; CANCELLED 2 days; DONE-OK 3 days; DONE-FAILED 4 days; REGISTERED 5 days;" />

then the job purger will purge jobs which are:

• in ABORTED status for more than 1 day
• in CANCELLED status for more than 2 days
• in DONE-OK status for more than 3 days
• in DONE-FAILED status more than 4 days
• in REGISTERED status for more than 5 days

2.18.2 Purging jobs in a non terminal status

JobAdminPurger allows to purge jobs based on their CREAM jobids and/or their status (considering how long the job is in that status).

TBC

2.19 Proxy purging

Expired delegation proxies are automatically purged:

• from the DelegationDB
• from the file system ( <cream-sandbox-dir>/<group>/<DN>/proxy)

If the value is changed, it is then necessary to restart tomcat.

Setting that value to -1 means disabling the proxy purger.

2.20 Job wrapper management

2.20.1 Customization points

The CREAM JobWrapper running on the WN execute some scripts (to be provided by the local administrators) if they exist. These are called customization points.

There are 3 customization points:

• ${GLITE_LOCAL_CUSTOMIZATION_DIR}/cp_1.sh. This is executed in the beginning of the CREAM job wrapper execution, before the creation of the temporary directory where the job is executed.

• ${GLITE_LOCAL_CUSTOMIZATION_DIR}/cp_2.sh. This is executed just after the execution of the user job, before executing the epilogue (if any)

• ${GLITE_LOCAL_CUSTOMIZATION_DIR}/cp_3.sh. This is executed just before the end of the JobWrapper execution.

2.20.2 Customization of the CREAM Job wrapper

To customize the CREAM job wrapper it is just necessary to edit as appropriate the template file /etc/glite-ce-cream/jobwrapper.tpl.

When done, tomcat must be restarted.

2.20.3 Customization of the Input/Output Sandbox file transfers

The CREAM job wrapper, besides running the user payload, is also responsible for other operations, such as the transfer of the input and output sandbox files from/to remote gridftp servers.

If in such transfers there is a failure, the operation is retried after a while. The sleep time between the first attempt and the second one is the “initial wait time” specified in the CREAM configuration file. In every next attempt the sleep time is doubled.

In the CREAM configuration file ( /etc/glite-ce-cream/cream-config.xml) it is possible to set:

• the maximum number of file transfers that should be tried
• the initial wait time (i.e. the wait time between the first attempt and the second one)

The relevant section in the CREAM configuration file is this one:

<parameter name="JOB_WRAPPER_COPY_RETRY_COUNT_ISB" value="2" />
<parameter name="JOB_WRAPPER_COPY_RETRY_FIRST_WAIT_ISB" value="60" /> <!-- sec. -->
<parameter name="JOB_WRAPPER_COPY_RETRY_COUNT_OSB" value="6" />
<parameter name="JOB_WRAPPER_COPY_RETRY_FIRST_WAIT_OSB" value="300" /> <!-- sec. -->

If one or more of these values are changed, it is then necessary to restart tomcat.

2.21 Managing the forwarding of requirements to the batch system

The CREAM CE allows to forward, via tha BLAH component, requirements to the batch system.

From a site administrator point of view, this requires creating and properly filling some scripts ( /usr/bin/xxx_local_submit_attributes.sh).

The relevant documentation is available at TBC

2.22 Querying the CREAM Database

2.22.1 Check how many jobs are stored in the CREAM database

The following mysql query can be used to check how many jobs (along with their status) are reported in the CREAM database:

mysql> select jstd.name, count(*) from job, job_status_type_description jstd, job_status AS status LEFT OUTER JOIN job_status AS latest  ON latest.jobId=status.jobId AND status.id < latest.id  WHERE latest.id IS null and job.id=status.jobId and jstd.type=status.type group by jstd.name;

Click here for information how to deploy the databases on a machine different wrt the CREAM-CE.

0.1 CREAM CE Installation

This section explains how to install:

• a CREAM CE in no cluster mode
• a CREAM CE in cluster mode
• a glite-CLUSTER node

0.1.1 Repositories

For a successful installation, you will need to configure your package manager to reference a number of repositories (in addition to your OS);

• the EPEL repository
• the EMI middleware repository
• the CA repository

and to REMOVE (!!!) or DEACTIVATE (!!!)

• the DAG repository

0.1.1.1 The EPEL repository

On sl5_x86_64, you can install the EPEL repository, issuing:

rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm

TBC

0.1.1.2 The EMI middleware repository

On sl5_x86_64 you can install the EMI-2 yum repository, issuing:

wget TBD
yum install ./TBD

TBC

0.1.1.3 The Certification Authority repository

The most up-to-date version of the list of trusted Certification Authorities (CA) is needed on your node. The relevant yum repo can be installed issuing:

wget http://repository.egi.eu/sw/production/cas/1/current/repo-files/EGI-trustanchors.repo -O /etc/yum.repos.d/EGI-trustanchors.repo

0.1.1.4 Important note on automatic updates

An update of an the packages not followed by configuration can cause problems. Therefore WE STRONGLY RECOMMEND NOT TO USE AUTOMATIC UPDATE PROCEDURE OF ANY KIND.

Running the script available at http://forge.cnaf.infn.it/frs/download.php/101/disable_yum.sh (implemented by Giuseppe Platania (INFN Catania) yum autoupdate will be disabled

0.1.2 Installation of a CREAM CE node in no cluster mode

On sl5_x86_64 first of all install the yum-protectbase rpm:

  yum install yum-protectbase.noarch 

Then proceed with the installation of the CA certificates.

TBC

0.1.2.1 Installation of the CA certificates

On sl5_x86_64, the CA certificate can be installed issuing:

yum install ca-policy-egi-core 

TBC

0.1.2.2 Installation of the CREAM CE software

On sl5_x86_64 first of all install xml-commons-apis:

yum install xml-commons-apis 

This is due to a dependency problem within the Tomcat distribution

Then install the CREAM-CE metapackage:

yum install emi-cream-ce

TBC

0.1.2.3 Installation of the batch system specific software

After the installation of the CREAM CE metapackage it is necessary to install the batch system specific metapackage(s):

On sl5_x86_64:

• If you are running Torque, and your CREAM CE node is the torque master, install the emi-torque-server and emi-torque-utils metapackages:

yum install emi-torque-server
yum install emi-torque-utils

• If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage:

yum install emi-torque-utils

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

yum install emi-lsf-utils

• If you are running GE, install the emi-ge-utils metapackage:

yum install emi-ge-utils

TBC

0.1.3 Installation of a CREAM CE node in cluster mode

On sl5_x86_64, first of all install the yum-protectbase rpm:

  yum install yum-protectbase.noarch 

Then proceed with the installation of the CA certificates.

0.1.3.1 Installation of the CA certificates

On sl5_86_64 the CA certificate can be installed issuing:

yum install ca-policy-egi-core 

0.1.3.2 Installation of the CREAM CE software

On sl5_x86_64, first of all install xml-commons-apis:

yum install xml-commons-apis 

This is due to a dependency problem within the Tomcat distribution

Then install the CREAM-CE metapackage:

yum install emi-cream-ce

0.1.3.3 Installation of the batch system specific software

After the installation of the CREAM CE metapackage it is necessary to install the batch system specific metapackage(s).

On sl5_x86_64:

• If you are running Torque, and your CREAM CE node is the torque master, install the emi-torque-server and emi-torque-utils metapackages:

yum install emi-torque-server
yum install emi-torque-utils

• If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage:

yum install emi-torque-utils

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

yum install emi-lsf-utils

* If you are running GE, install the emi-ge-utils metapackage:

yum install emi-ge-utils

TBC

0.1.3.4 Installation of the cluster metapackage

If the CREAM CE node has to host also the glite-cluster, install also the relevant metapackage.

On sl5_x86_64:

yum install emi-cluster 

TBC

0.1.4 Installation of a glite-cluster node

On sl5_x86_64, first of all install the yum-protectbase rpm:

  yum install yum-protectbase.noarch 

Then proceed with the installation of the CA certificates.

0.1.4.1 Installation of the CA certificates

On sl5_x86_64, the CA certificates can be installed issuing:

yum install ca-policy-egi-core 

0.1.4.2 Installation of the cluster metapackage

Install the glite-CLUSTER metapackage.

On sl5_x86_64:

yum install emi-cluster 

0.1.5 Installation of the BLAH BLparser

If the new BLAH Blparser must be used, there isn't anything to be installed for the BLAH Blparser (i.e. the installation of the CREAM-CE is enough).

This is also the case when the old BLAH Blparser must be used AND the BLPARSER_HOST is the CREAM-CE.

Only when the old BLAH Blparser must be used AND the BLPARSER_HOST is different than the CREAM-CE, it is necessary to install the BLParser software on this BLPARSER_HOST. This is done in the following way:

On sl5_x86_64:

yum install glite-ce-blahp 
yum install glite-yaim-cream-ce

TBC

0.1.6 Installation of the CREAM CLI

The CREAM CLI is part of the EMI-UI. To install it please refer to TBD.

0.2 CREAM CE configuration

0.2.1 Manual and automatic (yaim) configuration

The following sections describe the needed configuration steps for two following scenarios:

• Manual configuration
• Automatic configuration via yaim

For a detailed description on how to configure the middleware with YAIM, please check the YAIM guide.

The necessary YAIM modules needed to configure a certain node type are automatically installed with the middleware.

0.2.2 Configuration of a CREAM CE node in no cluster mode

0.2.2.1 Install host certificate

The CREAM CE node requires the host certificate/key files to be installed. Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.

Once you have obtained a valid certificate:

• hostcert.pem - containing the machine public key
• hostkey.pem - containing the machine private key

chown root.root /etc/grid-security/hostcert.pem
chown root.root /etc/grid-security/hostkey.pem
chmod 600 /etc/grid-security/hostcert.pem
chmod 400 /etc/grid-security/hostkey.pem

0.2.2.2 Manual configuration

TBD

0.2.2.3 Configuration via yaim

0.2.2.3.1 Configure the siteinfo.def file

Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for CREAM CE is available at TBD,

Be sure that CREAMCE_CLUSTER_MODE is set to no (or not set at all, since no is the default value).

0.2.2.3.2 Run yaim

After having filled the siteinfo.def file, run yaim:

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n <LRMSnode> 

Examples:

• Configuration of a CREAM CE in no cluster mode using Torque as batch system, with the CREAM CE being also Torque server

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils

• Configuration of a CREAM CE in no cluster mode using Torque as batch system, with the CREAM CE NOT being also Torque server

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_utils

• Configuration of a CREAM CE in no cluster mode using LSF as batch system

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n LSF_utils 

• Configuration of a CREAM CE in no cluster mode using GE as batch system

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils 

0.2.3 Configuration of a CREAM CE node in cluster mode

0.2.3.1 Install host certificate

The CREAM CE node requires the host certificate/key files to be installed. Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.

Once you have obtained a valid certificate:

• hostcert.pem - containing the machine public key
• hostkey.pem - containing the machine private key

chown root.root /etc/grid-security/hostcert.pem
chown root.root /etc/grid-security/hostkey.pem
chmod 600 /etc/grid-security/hostcert.pem
chmod 400 /etc/grid-security/hostkey.pem

0.2.3.2 Manual configuration

TBD

0.2.3.3 Configuration via yaim

0.2.3.3.1 Configure the siteinfo.def file

Set your siteinfo.def file, which is the input file used by yaim.

Variables which are required in cluster mode are described at TBD.

When the CREAM CE is configured in cluster mode it will stop publishing information about clusters and subclusters. That information should be published by the glite-CLUSTER node type instead. A specific set of yaim variables has been defined for configuring the information which is still required by the CREAM CE in cluster mode. The names of these variables follow this syntax:

• In general, variables based on hostnames, queues or VOViews containing '.' and '_' # should be transformed into '-'
• <host-name>: identifier that corresponds to the CE hostname in lower case. Example: ctb-generic-1.cern.ch -> ctb_generic_1_cern_ch
• <queue-name>: identifier that corresponds to the queue in upper case. Example: dteam -> DTEAM
• <voview-name>: identifier that corresponds to the VOView id in upper case. '/' and '=' should also be transformed into '_'. Example: /dteam/Role=admin -> DTEAM_ROLE_ADMIN

Be sure that CREAMCE_CLUSTER_MODE is set to yes

0.2.3.3.2 Run yaim

After having filled the siteinfo.def file, run yaim:

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n <LRMSnode> [-n glite-CLUSTER]

-n glite-CLUSTER must be specified only if the glite-CLUSTER is deployed in the same node of the CREAM-CE

Examples:

• Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on a different node) using LSF as batch system

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n LSF_utils

• Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on a different node) using GE as batch system

    /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils 

• Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on a different node) using Torque as batch system, with the CREAM CE being also Torque server

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils

• Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on a different node) using Torque as batch system, with the CREAM CE NOT being also Torque server

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n TORQUE_utils

• Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on the same node of the CREAM-CE) using LSF as batch system

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n LSF_utils -n glite-CLUSTER

* Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on the same node of the CREAM-CE) using GE as batch system

     /opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n SGE_utils -n glite-CLUSTER

• Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on the same node of the CREAM-CE) using Torque as batch system, with the 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

• Configuration of a CREAM CE in cluster mode (with glite-CLUSTER deployed on the same node of the CREAM-CE)) using Torque as batch system, with the 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.2.4 Configuration of a glite-CLUSTER node

0.2.4.1 Install host certificate

The glite-CLUSTER node requires the host certificate/key files to be installed. Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.

Once you have obtained a valid certificate:

• hostcert.pem - containing the machine public key
• hostkey.pem - containing the machine private key

chown root.root /etc/grid-security/hostcert.pem
chown root.root /etc/grid-security/hostkey.pem
chmod 600 /etc/grid-security/hostcert.pem
chmod 400 /etc/grid-security/hostkey.pem

0.2.4.2 Manual configuration

0.2.4.3 Configuration via yaim

0.2.4.3.1 Configure the siteinfo.def file

Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for glite-CLUSTER is available at TBD.

0.2.4.3.2 Run yaim

After having filled the siteinfo.def file, run yaim:

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n glite-CLUSTER

0.2.5 Configuration of the BLAH Blparser

If the new BLAH Blparser must be used, there isn't anything to be configured for the BLAH Blparser (i.e. the configuration of the CREAM-CE is enough).

If the old BLparser must be used, it is necessary to configure it on the BLPARSER_HOST (which, as said above, can be the CREAM-CE node or on a different host). This is done via yaim in the following way:

/opt/glite/yaim/bin/yaim -r -s <site-info.def> -n creamCE -f config_cream_blparser

In case of manual configuration, TBD

Then it is necessary to restart tomcat on the CREAM-CE node:

service tomcat5 restart

0.2.5.1 Configuration of the old BLAH Blparser to serve multiple CREAM CEs

The configuration instructions reported above explains how to configure a CREAM CE and the BLAH blparser (old model) considering the scenario where the BLAH blparser has to "serve" a single CREAM CE.

Considering that the blparser (old model) has to run where the batch system log files are available, let's consider a scenario where there are 2 CREAM CEs ( ce1.mydomain and ce2.mydomain) that must be configured. Let's suppose that the batch system log files are not available on these 2 CREAM CEs machine. Let's assume they are available in another machine ( blhost.mydomain), where the old blparser has to be installed.

The following summarizes what must be done:

• In the /services/glite-creamce for ce1.mydomain set:

BLPARSER_HOST=blhost.mydomain
BLAH_JOBID_PREFIX=cre01_
BLP_PORT=33333

and configure ce1.mydomain via yaim:

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n <LRMSnode> [-n glite-CLUSTER]

• In the /services/glite-creamce for ce2.mydomain set:

BLPARSER_HOST=blhost.mydomain
BLAH_JOBID_PREFIX=cre02_
BLP_PORT=33334

and configure ce2.mydomain via yaim:

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n creamCE -n <LRMSnode> [-n glite-CLUSTER]

• In the /services/glite-creamce for blhost.mydomain sets:

CREAM_PORT=56565

and configure blhost.mydomain via yaim:

/opt/glite/yaim/bin/yaim -r -s <site-info.def> -n creamCE -f config_cream_blparser

• In blhost.mydomain edit the file /etc/blparser.conf setting (considering the pbs/torque scenario):

GLITE_CE_BLPARSERPBS_NUM=2

# ce01.mydomain
GLITE_CE_BLPARSERPBS_PORT1=33333
GLITE_CE_BLPARSERPBS_CREAMPORT1=56565

# ce02.mydomain
GLITE_CE_BLPARSERPBS_PORT2=33334
GLITE_CE_BLPARSERPBS_CREAMPORT2=56566

• Restart the blparser on blhost.mydomain:

/etc/init.d/glite-ce-blparser restart

• Restart tomcat on ce01.mydomain and ce02.mydomain

0.2.5.2 Configuration of the new BLAH Blparser to to use cached batch system commands

The new BLAH blparser can be configured in order to not interact directly with the batch system, but through a program (to be implemented by the site admin) which can implement some caching functionality. This is the case for example of CommandProxyTools, implement at Cern

To enable this feature, add in /etc/blah.config (the example below is for lsf, with /usr/bin/runcmd.pl as name of the "caching" program):

lsf_batch_caching_enabled=yes
batch_command_caching_filter=/usr/bin/runcmd.pl

So the blparser, insead of issuing bjobs -u ...., will issue /usr/bin/runcmd.pl bjobs -u ..." </verbatim>

0.2.6 Configuration of the CREAM databases on a host different than the CREAM-CE (using yaim)

To configure the CREAM databases on a host different than the CREAM-CE:

• Set in the siteinfo.def file the variable CREAM_DB_HOST to the remote host (where mysql must be already installed)
• Set in the siteinfo.def file the variable MYSQL_PASSWORD considering the mysql password of the remote host
• On this remote host, grant appropriate privs to root@CE_HOST
• Configure via yaim

0.2.7 Configuration of the CREAM CLI

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.2.8 Configurations possible only manually

yaim allows to choose the most important parameters (via yaim variables) related to the CREAM-CE. It is then possible to tune some other attributes manually editing the relevant configuration files.

Please note that:

• After having manually modified a configuration file, it is then necessary to restart the service
• Manual changes done in the configuration files are scratched by following yaim reconfigurations

0.3 Batch system integration

0.3.1 Torque

0.3.1.1 Installation

System Administrator Guide for CREAM for EMI-2 release

1 Installation and Configuration

1.1 Prerequisites

1.1.1 Operating system

The following operating systems are supported:

• SL5 64 bit
• TBC

It is assumed that the operating system is already properly installed.

1.1.2 Node synchronization

A general requirement for the Grid nodes is that they are synchronized. This requirement may be fulfilled in several ways. One of the most common one is using the NTP protocol with a time server.

1.1.3 Cron and logrotate

Many components deployed on the CREAM CE rely on the presence of cron (including support for /etc/cron.* directories) and logrotate. You should make sure these utils are available on your system.

1.1.4 Batch system

If you plan to use Torque as batch system for your CREAM CE, it will be installed and configured along with the middleware (i.e. you don't have to install and configure it in advance)

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 batch system softwares is out of the scope of this activity.

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

1.2 Plan how to deploy the CREAM CE

1.2.1 CREAM CE and gLite-cluster

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).

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:

• publish a SubCluster with a representative/minimum hardware description (e.g. the minimum memory on any node)
• define separate batch queues for each hardware configuration, e.g. low/high memory queues, and attach the corresponding GlueCE objects to separate Cluster/SubCluster pairs. For attributes with discrete values, e.g. SL4 vs SL5, this second option is the only one which makes sense.

A second problem, addressed by gLite-cluster arises for larger sites which install multiple CE headnodes submitting to the same 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).

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:

• if in the site there are multiple CE head nodes, and/or
• if in the site there are multiple disjoint sets of worker nodes, each set having sufficiently homogeneous properties

When configuring a gLite-cluster, please consider that:

• There should be one cluster for each set of worker nodes having sufficiently homogeneous properties
• There should be one subcluster for each cluster
• Each batch system queue should refer to the WNs of a single subcluster

glite-CLUSTER can be deployed in the same host of a CREAM-CE or in a different one.

The following deployment models are possible for a CREAM-CE:

• CREAM-CE can be configured without worrying about the glite-CLUSTER node. This can be useful for small sites who don't want to worry about cluster/subcluster configurations because they have a very simple setup. In this case CREAM-CE will publish a single cluster/subcluster. This is called no cluster mode. This is done as described below by defining the yaim setting CREAMCE_CLUSTER_MODE=no (or by no defining at all that variable).
• CREAM-CE can work on cluster mode using the glite-CLUSTER node type. This is done as described below by defining the yaim setting CREAMCE_CLUSTER_MODE=yes. The CREAM-CE can be in the same host or in a different host wrt the glite-CLUSTER node.

More information about glite-CLUSTER can be found at https://twiki.cern.ch/twiki/bin/view/LCG/CLUSTER and in this note.

Information concerning glue2 publication is available here.

1.2.2 Define a DNS alias to refer to set of CREAM CEs

In order to distribute load for job submissions, it is possible to deploy multiple CREAM CEs head nodes referring to the same set of resources. As explained in the previous section, this should be implemented with:

• a gLite-CLUSTER node
• multiple CREAM CEs configured in cluster mode

The alias shouldn't be published in the information service, but should be simply communicated to the relevant users.

There are various techniques to change an alias entry in the DNS. The choice depends strongly on the way the network is set up and managed. For example at DESY a self-written service called POISE is used; using metrics (which take into account in particular the load and the sandbox size ) it decides the physical instance the alias should point to. Another possibility to define aliases is to use commercial network techniques such as F5.

It must be noted that, as observed by Desy sysadmins, the proliferation of the aliases (C-records) is not well defined among DNS'. Therefore changes of an alias sometimes can take hours to be propagated to other sites.

The use of alias for job submission is a good solution to improve load balancing and availability of the service (the unavailability of a physical CREAM CE would be hidden by the use of the alias). It must however be noted that:

• The list operation ( glite-ce-job-list command of the CREAM CLI) issued on a alias returns the identifiers of the jobs submitted to the physical instance currently pointed to the alias, and not the identifiers of all the jobs submitted to all CREAM CEs instances
• The operations to be done on all jobs (e.g. cancel all jobs, return the status of all jobs, etc.), i.e. the ones issued using the options -a -e of the CREAM CLI, issued on a alias, refer to just the CREAM physical instance currently pointed by the alias (and not to all CREAM CE instances).
• The use of alias is not supported for submissions through the gLite-WMS

1.2.3 Choose the authorization model

The CREAM CE can be configured to use as authorization system:

• the ARGUS authorization framework

• the grid Java Authorization Framework (gJAF)

To use ARGUS as authorization system, yaim variable USE_ARGUS must be set in the following way:

USE_ARGUS=yes

In this case it is also necessary to set the following yaim variables:

• ARGUS_PEPD_ENDPOINTS The endpoint of the ARGUS box (e.g."https://cream-43.pd.infn.it:8154/authz")
• CREAM_PEPC_RESOURCEID The id of the CREAM CE in the ARGUS box (e.g. "http://pd.infn.it/cream-18")

If instead gJAF should be used as authorization system, yaim variable USE_ARGUS must be set in the following way:

USE_ARGUS=no

1.2.4 Choose the BLAH BLparser deployment model

For LSF and PBS/Torque it is possible to configure the BLAH blparser in two possible ways:

• The new BLAH BLparser, which relies on the status/history batch system commands
• The old BLAH BLparser, which parses the batch system log files

For GE and Condor, only the configuration with the new BLAH blparser is possible

1.2.4.1 New BLAH Blparser

The new Blparser runs on the CREAM CE machine and it is automatically installed when installing the CREAM CE. The configuration of the new BLAH Blparser is done when configuring the CREAM CE (i.e. it is not necessary to configure the Blparser separately from the CREAM CE).

To use the new BLAH blparser, it is just necessary to set:

BLPARSER_WITH_UPDATER_NOTIFIER=true

in the siteinfo.def and then configure the CREAM CE. This is the default value.

The new BLParser doesn't parse the log files. However the bhist (for LSF) and tracejob (for Torque) commands (used by the new BLParser) require the batch system log files, which therefore must be available (in case e.g. via NFS in the CREAM CE node. Actually for Torque the blparser uses tracejob (which requires the log files) only when qstat can't find anymore the job. And this can happen if the job has been completed more than keep_completed seconds ago and the blparser was not able to detect before that the job completed/was cancelled/whatever. This can happen e.g. if keep_completed is too short or if the BLAH blparser for whatever reason didn't run for a while. If the log files are not available and the tracejob command is issued (for the reasons specified above), the BLAH blparser will not be able to find the job, which will considered "lost" (DONE-FAILED wrt CREAM).

The init script of the new Blparser is /etc/init.d/glite-ce-blah-parser. Please note that it is not needed to explicitly start the new blparser: when CREAM is started, it starts also this new BLAH Blparser if it is not already running.

When the new Blparser is running, you should see the following two processes on the CREAM CE node:

• /usr/bin/BUpdaterxxx
• /usr/bin/BNotifier

Please note that the user tomcat on the CREAM CE should be allowed to issue the relevant status/history commands (for Torque: qstat, tracejob, for LSF: bhist, bjobs). Some sites configure the batch system so that users can only see their own jobs (e.g. in torque:

set server query_other_jobs = False

). If this is done at the site, then the tomcat user will need a special privilege in order to be exempt from this setting (in torque:

set server operators += tomcat@creamce.yoursite.domain

).

1.2.4.2 Old BLAH Blparser

The old BLAH blparser must be installed on a machine where the batch system log files are available (let's call this host BLPARSER_HOST. So the BLPARSER_HOST can be the batch system master or a different machine where the log files are available (e.g. they have been exported via NFS). There are two possible layouts:

• The BLPARSER_HOST is the CREAM CE host
• The BLPARSER_HOST is different than the CREAM CE host

If the BLPARSER_HOST is the CREAM CE host, after having installed and configured the CREAM CE, it is necessary to configure the old BLAH Blparser (as explained below) and then to restart tomcat.

If the BLPARSER_HOST is different than the CREAM CE host, after having installed and configured the CREAM CE it is necessary:

• to install the old BLAH BLparser software on this BLPARSER_HOST as explained below
• to configure thie old BLAH BLparser
• to restart tomcat on the CREAM-CE

On the CREAM CE, to use the old BLAH blparser, it is necessary to set:

BLPARSER_WITH_UPDATER_NOTIFIER=false

in the siteinfo.def before configuring via yaim.

1.2.5 Deployment models for CREAM databases

-- MassimoSgaravatto - 2011-12-20