|
META TOPICPARENT |
name="SystemAdministratorDocumentation" |
The CREAM configuration file for the EMI-2 release
|
|
- BLPARSER_RETRY_DELAY: the time interval (ms) between two attempts to contact the BLAH parser (default: "60000")
- LRMS_EVENT_LISTENER_PORT: the port used by CREAM to receive notifications about job status changes sent by the BLParser/JobWrapper (default: "49152")
- HOST_SMP_SIZE: the default value for the hostsmpsize attribute (default: "2")
|
|
< < |
- JOB_WRAPPER_DELEGATION_TIME_SLOT = "3600"
<-- sec. -->
- JOB_WRAPPER_COPY_PROXY_MIN_RETRY_WAIT = "60"
<-- sec. -->
- JOB_WRAPPER_COPY_RETRY_COUNT_ISB = "2"
- JOB_WRAPPER_COPY_RETRY_FIRST_WAIT_ISB = "60"
<-- sec. -->
- JOB_WRAPPER_COPY_RETRY_COUNT_OSB = "6"
- JOB_WRAPPER_COPY_RETRY_FIRST_WAIT_OSB = "300"
<-- sec. -->
|
> > |
- JOB_WRAPPER_DELEGATION_TIME_SLOT: "3600"
<-- sec. -->
- JOB_WRAPPER_COPY_PROXY_MIN_RETRY_WAIT: the minimum time interval expressed in seconds, between the first attempt and the second one for retrieving the user delegation proxy (default: "60")
- JOB_WRAPPER_COPY_RETRY_FIRST_WAIT_ISB: if during a input sandbox file transfer occurs a failure, the JW retries the operation after a while. The sleep time between the first attempt and the second one is the “initial wait time” (i.e. the wait time between the first attempt and the second one) expressed in seconds. In every next attempt the sleep time is doubled (default: "60")
- JOB_WRAPPER_COPY_RETRY_COUNT_ISB: the maximum number of ISB file transfers that should be tried (default: "2")
- JOB_WRAPPER_COPY_RETRY_FIRST_WAIT_OSB: if during a output sandbox file transfer occurs a failure, the JW retries the operation after a while. The sleep time between the first attempt and the second one is the “initial wait time” (i.e. the wait time between the first attempt and the second one) expressed in seconds. In every next attempt the sleep time is doubled (default: "300")
- JOB_WRAPPER_COPY_RETRY_COUNT_OSB: the maximum number of OSB file transfers that should be tried (default: "6")
|
|
- JOB_WRAPPER_TEMPLATE_PATH: the path where the JobWrapper template is placed (default: "/etc/glite-ce-cream/")
- JOBS_SCRATCH_DIR: the tmp directory used by CREAM (dafault: "/var/tmp")
|
|
< < |
- JOB_SUBMISSION_MANAGER_ENABLE: "true"
- JOB_SUBMISSION_MANAGER_SCRIPT_PATH: "/usr/bin/glite_cream_load_monitor /etc/glite-ce-cream-utils/glite_cream_load_monitor.conf"
|
> > |
- JOB_SUBMISSION_MANAGER_SCRIPT_PATH: CREAM is able to protect itself if the load (i.e. memory usage, etc) is too high. In this scenario it refuses new job submissions, while the other commands are still allowed. The whole stuff is implemented via a limiter script (i.e. /usr/bin/glite_cream_load_monitor) very similar to the one used in the WMS. Basically this limiter script checks the values for some system and CREAM specific parameters, and compare them against some thresholds defined in its configuration file (i.e. /etc/glite-ce-cream-utils/glite_cream_load_monitor.conf"). If one or more threshold is exceeded, new job submissions get not allowed and an error message is returned to the client. Moreover the limiter script is run every 10 (default: "/usr/bin/glite_cream_load_monitor /etc/glite-ce-cream-utils/glite_cream_load_monitor.conf")
- JOB_SUBMISSION_MANAGER_ENABLE: in order to disable the limiter, it is needed to set this parameter value to false and restart the service (default: "true")
|
|
- JOB_PURGE_POLICY: the policy concerning which jobs should be deleted by the automatic job purger and when. For example, if JOB_PURGE_POLICY is "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
|
|
- BLAH_NOTIFICATION_LISTENER_PORT: the port used by CREAM to receive notifications about job status changes sent by the BLParser/ActivityWrapper (default: "49155")
- BLAH_NOTIFIER_RETRY_COUNT: represents the number of attempts to contact the BLAH parser (if it is not reachable) before giving up. If -1 is specified, CREAM will never give up (default: "100")
- BLAH_NOTIFIER_RETRY_DELAY: the time interval (ms) between two attempts to contact the BLAH parser (default: "60000")
|
|
< < |
- COPY_PROXY_MIN_RETRY_WAIT: (default: "60" seconds)
- COPY_RETRY_COUNT_ISB: (default: "2")
- COPY_RETRY_FIRST_WAIT_ISB: (default: "60" seconds)
- COPY_RETRY_COUNT_OSB: (default: "6")
- COPY_RETRY_FIRST_WAIT_OSB: (default: "300" seconds)
|
> > |
- COPY_PROXY_MIN_RETRY_WAIT: the minimum time interval expressed in seconds, between the first attempt and the second one for retrieving the user delegation proxy (default: "60")
- COPY_RETRY_FIRST_WAIT_ISB: if during a input sandbox file transfer occurs a failure, the JW retries the operation after a while. The sleep time between the first attempt and the second one is the “initial wait time” (i.e. the wait time between the first attempt and the second one) expressed in seconds. In every next attempt the sleep time is doubled (default: "60")
- COPY_RETRY_COUNT_ISB: the maximum number of ISB file transfers that should be tried (default: "2")
- COPY_RETRY_FIRST_WAIT_OSB: if during a output sandbox file transfer occurs a failure, the JW retries the operation after a while. The sleep time between the first attempt and the second one is the “initial wait time” (i.e. the wait time between the first attempt and the second one) expressed in seconds. In every next attempt the sleep time is doubled (default: "300")
- COPY_RETRY_COUNT_OSB: the maximum number of OSB file transfers that should be tried (default: "6")
|
|
- CREATE_WRAPPER_BIN_PATH: (default: "/usr/bin/glite-ce-cream-create-wrapper")
- CREATE_SANDBOX_BIN_PATH: the path of the executable for creating the job sandbox (default: "/usr/bin/glite-cream-createsandboxdir")
- DEFAULT_LRMS_NAME: defines the default LRMS used by CREAM if not specified by the user
|
| />
|
|
< < | We suggest not to change the default values coming from the YAIM configuration. Moreover please check the section 1.5.5 of the System Administrator Guide (i.e. https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI2) if you want to configure the CREAM databases on a host different than the CREAM service (by using YAIM). |
> > | We suggest not to change the default values coming from the YAIM configuration phase. The parameters are all mandatory and their values well defined therefore there is no need to change them. Moreover please check the section 1.5.5 of the System Administrator Guide (i.e. https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI2) if you want to configure the CREAM databases on a host different than the CREAM service (by using YAIM). |
|
The security authorization layer configuration |
|
|
|
> > | We suggest not to change the default values coming from the YAIM configuration phase. The parameters are all mandatory and their values well defined therefore there is no need to change them. |
|
-- LisaZangrando - 2012-12-04
\ No newline at end of file |