Difference: SystemAdministratorGuideForEMI2 (9 vs. 10)

Revision 102012-04-17 - MassimoSgaravatto

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

System Administrator Guide for CREAM for EMI-2 release

Line: 36 to 36
  The support of the batch system softwares is out of the scope of this activity.
Changed:
<
<
More information abut batch system integration is available in the relevant section.
>
>
More information abut batch system integration is available in the relevant section.
 

0.1 Plan how to deploy the CREAM CE

Line: 195 to 195
  The databases used by CREAM can be deployed in the CREAM CE host (which is the default scenario) or on a different machine.
Changed:
<
<
Click here for information how to deploy the databases on a machine different wrt the CREAM-CE.
>
>
Click here for information how to deploy the databases on a machine different wrt the CREAM-CE.
 

0.1 CREAM CE Installation

Line: 474 to 474
 

0.0.1 Installation of the CREAM CLI

Changed:
<
<
The CREAM CLI is part of the EMI-UI. To install it please refer to TBD.
>
>
The CREAM CLI is part of the EMI-UI. To install it please refer to the relevant guide.
 

0.1 CREAM CE configuration

Line: 511 to 511
 
0.0.0.0.1 Configure the siteinfo.def file
Changed:
<
<
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,
>
>
Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for CREAM CE is available at https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#cream_CE.
  Be sure that CREAMCE_CLUSTER_MODE is set to no (or not set at all, since no is the default value).
Line: 575 to 575
  Set your siteinfo.def file, which is the input file used by yaim.
Changed:
<
<
Variables which are required in cluster mode are described at TBD.
>
>
Variables which are required in cluster mode are described at https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#cream_CE.
  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:
Line: 665 to 665
 
0.0.0.0.1 Configure the siteinfo.def file
Changed:
<
<
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.
>
>
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.
 
0.0.0.0.1 Run yaim
Line: 1073 to 1073
 

0.1 Daemons

Changed:
<
<
Information about daemons running in the CREAM CE is available in TBC
>
>
Information about daemons running in the CREAM CE is available in https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#Daemons_running.
 

0.1 Init scripts

Changed:
<
<
Information about init scripts in the CREAM CE is available in the TBC
>
>
Information about init scripts in the CREAM CE is available in the https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#Init_scripts_and_options_start_s.
 

0.1 Configuration files

Changed:
<
<
Information about configuration files in the CREAM CE is available in TBC
>
>
Information about configuration files in the CREAM CE is available in https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#Configuration_files_location.
 

0.1 Log files

Changed:
<
<
Information about log files in the CREAM CE is available in TBC
>
>
Information about log files in the CREAM CE is available in https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#Logfile_locations_and_management.
 

0.1 Network ports

Changed:
<
<
Information about ports used in the CREAM CE is available in TBC
>
>
Information about ports used in the CREAM CE is available in https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#Open_ports.
 

0.1 Cron jobs

Changed:
<
<
Information about cron jobs used in the CREAM CE is available in TBC
>
>
Information about cron jobs used in the CREAM CE is available in https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#Cron_jobs.
 

0.1 Security related operations

Line: 1115 to 1115
 

0.0.1 Security recommendations

Changed:
<
<
Security recommendations relevant for the CREAM CE is available in TBC
>
>
Security recommendations relevant for the CREAM CE is available in https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#Security_recommendations.
 

0.0.1 How to block/ban a user

Changed:
<
<
Information about how to ban users is available in TBC
>
>
Information about how to ban users is available in https://wiki.italiangrid.it/twiki/bin/view/CREAM/ServiceReferenceCardEMI2#How_to_block_ban_a_user.
 

0.0.1 How to block/ban a VO

Line: 1188 to 1188
  The whole stuff is implemented via a limiter script ( /usr/bin/glite_cream_load_monitor) very similar to the one used in the WMS.
Changed:
<
<
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.:
>
>
Basically this limiter script check the values for some system and CREAM specific parameters, and compare them against some thresholds, defined in a configuration file (/etc/glite-ce-cream-utils/glite_cream_load_monitor.conf). 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.

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:

Value Default threshold
Load average (1 min) 40
Load average (5 min) 40
Load average (15 min) 20
Memory usage 95 %
Swap usage 95 %
Free file descriptors 500
File descriptors used by tomcat 800
Number of FTP connections 30
Number of active jobs no limit
Number of pending commands (commands still to be executed) no limit

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.

 
Deleted:
<
<
TBC
 

0.1 How to drain a CREAM CE

Line: 1198 to 1222
  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.
Changed:
<
<
If newer job submissions are attempted, users will get an error message such as:
>
>
If newer job submissions are attempted, users will get an error message.
 
Deleted:
<
<
TBC
 
Added:
>
>
It is possible to then resume new job submissions calling the glite-ce-enable-submission command.

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
 

0.1 How to trace a specific job

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

Line: 1387 to 1431
  From a site administrator point of view, this requires creating and properly filling some scripts ( /usr/bin/xxx_local_submit_attributes.sh).
Changed:
<
<
The relevant documentation is available at TBC
>
>
The relevant documentation is available at https://wiki.italiangrid.it/twiki/bin/view/CREAM/UserGuideEMI2#Forward_of_requirements_to_the_b.
 

0.1 Querying the CREAM Database

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