Difference: CREAMConfigurationFile (1 vs. 11)

Revision 112013-03-26 - LisaZangrando

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

The CREAM configuration file for both EMI-2 and EMI-3 releases

Line: 9 to 9
 The default location of the CREAM configuration file is /opt/glite/etc/glite-ce-cream/cream-config.xml. It is a XML file composed of a set of elements basically of three different types:
  • commandexecutor which defines the specific capabilities (e.g. delegation, job management, activity management) provided by CREAM
  • JDBC dataSource used for setting up the access to CREAM DB (MySQL)
Changed:
<
<
  • argus-pep or authzchain which define the security authorization layer based on ARGUS service or gJAF
>
>
  • argus-pep or authzchain which defines the security authorization layer based on ARGUS service or gJAF
  The configuration file looks like the following schema:

Revision 102013-02-21 - LisaZangrando

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

The CREAM configuration file for the EMI-2 release

>
>

The CREAM configuration file for both EMI-2 and EMI-3 releases

 

Revision 92012-12-10 - LisaZangrando

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

The CREAM configuration file for the EMI-2 release

Line: 144 to 144
 
  • 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")
Changed:
<
<
  • 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")
Changed:
<
<
  • 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
Line: 188 to 188
 
  • 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")
Changed:
<
<
  • 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
Line: 228 to 228
  />
Changed:
<
<
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

Line: 274 to 274
 
Added:
>
>
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

Revision 82012-12-10 - LisaZangrando

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

The CREAM configuration file for the EMI-2 release

Line: 232 to 232
 

The security authorization layer configuration

Changed:
<
<
CREAM supports two different authorization systems based on the ARGUS authorization framework or the gJAF (grid Java Authorization Framework) system. The configuration depends on the authZ system selected. In case of ARGUS the XML section looks like this:
>
>
CREAM supports two different authorization systems based on the ARGUS service or the gJAF (grid Java Authorization Framework). Therefore the CREAM configuration depends on the authZ system selected. In case of ARGUS the XML section looks like:
 
<adminlist filename="/etc/grid-security/admin-list"/>
Line: 246 to 246
 </argus-pep>
Changed:
<
<
while the configuration of the gJAF system is:
>
>
while the configuration for the gJAF system is:
 
<authzchain name="chain-1">

Revision 72012-12-07 - LisaZangrando

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

The CREAM configuration file for the EMI-2 release

Line: 8 to 8
 

The CREAM configuration file structure

The default location of the CREAM configuration file is /opt/glite/etc/glite-ce-cream/cream-config.xml. It is a XML file composed of a set of elements basically of three different types:
  • commandexecutor which defines the specific capabilities (e.g. delegation, job management, activity management) provided by CREAM
Changed:
<
<
  • dataSource used for setting up the access to CREAM DB (MySQL)
  • authzchain which defines the security authorization layer based on ARGUS service or gJAF
>
>
  • JDBC dataSource used for setting up the access to CREAM DB (MySQL)
  • argus-pep or authzchain which define the security authorization layer based on ARGUS service or gJAF
  The configuration file looks like the following schema:
Line: 47 to 47
 
Changed:
<
<

The Command Executor

>
>

The Command Executor configuration

 The commandexecuctor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). At the current time CREAM provides three different commandexecuctors (BLAHExecutor, ActivityExecutor and DelegationExecutor) but new ones can be implemented and configured. The configuration of a commandexecutor is based on a well defined structure composed of a set of mandatory attributes and parameters which are specific for each executor:
Line: 72 to 72
 
  • category: the name of the category to which the commandexecutor belongs (e.g. DELEGATION_MANAGEMENT, JOB_MANAGEMENT, ACTIVITY_MANAGEMENT) (*)
  • commandqueuesize: the size of the in memory prefetched command queue (default: 500) (*)
  • commandqueueshared: must be set to false (default) if the command queue is used by a single CREAM; must be set to true if there are multiple CREAM services using a single command queue (i.e. multiple CREAM services managing a single farm) (*)
Changed:
<
<
  • commandworkerpoolsize: the number of threads getting and satisfying user requests stored in the CREAM command queue (default: 50) (*)
>
>
  • commandworkerpoolsize: defines the internal parallelism degree in terms of the number of commands (e.g. the user requests) processed simultaneously by a pool of threads (i.e. the command workers). Those commands are fetched from the the CREAM's command queue. Please note that the parameter value can influence the overall CREAM performance (default: 50) (*)
 
  • filename: the path of the jar implementing the commandexecutor (*)

* please DO NOT change the default value which comes from the YAIM configuration.

Line: 204 to 204
  * please DO NOT change the default value which comes from the YAIM configuration.
Added:
>
>

The JDBC datasource configuration

CREAM relies on an external relational database to store its internal state (e.g. jobs, activities, delegations, commands queue, etc). This improves fault tolerance as it guarantees that this information is preserved across restarts of CREAM. Moreover, the use of a SQL database improves responsiveness of the service while performing queries which are needed by the usual CREAM operations, such as getting the list of jobs associated with a specific user. The CREAM deployment provides MySQL as preferred database, but any SQL database accessible through JDBC should be well supported although we don't have yet experience on it. Note that the database server can be installed on a dedicated host, or can share the same machine hosting CREAM. The JDBC connection is configured by the following template:

<dataSource name="datasource_name"
    type="javax.sql.DataSource"
    factory="org.apache.commons.dbcp.BasicDataSourceFactory"
    driverClassName="org.gjt.mm.mysql.Driver"
    username="the user" password="the password"
    maxActive="200"
    maxIdle="30"
    maxWait="10000"
    url="jdbc:mysql://localhost:3306/DATABASE_NAME?autoReconnect=true"
    validationQuery="SELECT 1"
    testOnBorrow="true"
    testWhileIdle="true"
    timeBetweenEvictionRunsMillis="20000"
    minEvictableIdleTimeMillis="90000"
    logAbandoned="false"
    removeAbandoned="true"
    removeAbandonedTimeout="30"
  />

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

The security authorization layer configuration

CREAM supports two different authorization systems based on the ARGUS authorization framework or the gJAF (grid Java Authorization Framework) system. The configuration depends on the authZ system selected. In case of ARGUS the XML section looks like this:

<adminlist filename="/etc/grid-security/admin-list"/>
<argus-pep name="pep-client1"
    resource_id="CREAM_PEPC_RESOURCEID"
    cert="TOMCAT_HOSTCERT_LOCATION"
    key="TOMCAT_HOSTKEY_LOCATION"
    passwd=""
    mapping_class="org.glite.ce.cream.authz.argus.ActionMapping">
    <endpoint url="ARGUS_PEPD_ENDPOINTS" />
</argus-pep>

while the configuration of the gJAF system is:

<authzchain name="chain-1">
    <plugin name="localuserpip" classname="org.glite.ce.commonj.authz.gjaf.LocalUserPIP">
        <parameter name="glexec_bin_path" value="/usr/sbin/glexec" />
        <parameter name="glexec_probe_cmd" value="/usr/bin/id" />
        <parameter name="methods" value="JobRegister, putProxy, getProxyReq, renewProxyReq, getTerminationTime, destroy" />
    </plugin>

    <plugin name="bannerpdp" classname="org.glite.ce.commonj.authz.gjaf.BlackListServicePDP">
        <parameter name="blackListFile" value="/etc/lcas/ban_users.db" />
    </plugin>

    <plugin name="admincheckpip" classname="org.glite.ce.commonj.authz.gjaf.AdminCheckerPIP">
        <parameter name="adminList" value="/etc/grid-security/admin-list" />
    </plugin>

    <plugin name="gridmappdp" classname="org.glite.ce.commonj.authz.gjaf.GridMapServicePDP">
      <parameter name="gridMapFile" value="/etc/grid-security/grid-mapfile" />
    </plugin>

    <plugin name="vomspdp" classname="org.glite.ce.commonj.authz.gjaf.VomsServicePDP">
        <parameter name="gridMapFile" value="/etc/grid-security/grid-mapfile" />
    </plugin>
</authzchain>
  -- LisaZangrando - 2012-12-04

Revision 62012-12-06 - LisaZangrando

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

The CREAM configuration file

>
>

The CREAM configuration file for the EMI-2 release

 

Line: 48 to 48
 

The Command Executor

Changed:
<
<
The commandexeuctor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). More than one commandexecutor can be defined in the configuration file and its XML structure is as the following:
>
>
The commandexecuctor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). At the current time CREAM provides three different commandexecuctors (BLAHExecutor, ActivityExecutor and DelegationExecutor) but new ones can be implemented and configured. The configuration of a commandexecutor is based on a well defined structure composed of a set of mandatory attributes and parameters which are specific for each executor:
 
<commandexecutor
Line: 77 to 77
  * please DO NOT change the default value which comes from the YAIM configuration.
Added:
>
>

The Delegation Executor

The Delegation Executor implements delegation functionality (e.g. make a new delegation request, renew or destroy a delegation, etc). The list of attributes and parameters which define this executor, complete of their meaning and default values is:

attributes

  • id: "DelegationExecutor"
  • category: "DELEGATION_MANAGEMENT" (*)
  • commandqueuesize: "0" (NB: the value MUST be "0" because the executor doesn't need the command queue) (*)
  • commandqueueshared: "false" (*)
  • commandworkerpoolsize: "0" (NB: the value MUST be "0" because the executor doesn't need the command queue) (*)
  • filename: "/usr/share/java/glite-ce-cream-delegationExecutor.jar"

parameters

  • CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH: the path of the script for copying the user delegation proxy into the specified job sandbox (default: "/usr/bin/glite-cream-copyProxyToSandboxDir.sh")
  • CREAM_PURGE_PROXY_FROM_SANDBOX_BIN_PATH: the path of the script for deleting the user delegation proxy from the specified job sandbox (default: "/usr/bin/glite-ce-cream-purge-proxy")
  • CREAM_SANDBOX_DIR: the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
  • DELEGATION_PURGE_RATE: specifies how often the delegation purger has to run (default "10" minutes)

* please DO NOT change the default value which comes from the YAIM configuration.

example

<commandexecutor id="DelegationExecutor"
    category="DELEGATION_MANAGEMENT"
    commandqueuesize="0"
    commandqueueshared="false"
    commandworkerpoolsize="0"
    filename="/usr/share/java/glite-ce-cream-delegationExecutor.jar">

    <parameter name="CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH" value="/usr/bin/glite-cream-copyProxyToSandboxDir.sh" />
    <parameter name="CREAM_PURGE_PROXY_FROM_SANDBOX_BIN_PATH" value="/usr/bin/glite-ce-cream-purge-proxy" />
    <parameter name="CREAM_SANDBOX_DIR" value="/var/cream_es_sandbox" />
    <parameter name="DELEGATION_PURGE_RATE" value="10" /> <!-- minutes -->
</commandexecutor>
 

The BLAH Executor

Changed:
<
<
This executor implements the CREAM's job management capabilities and it is based on the BLAH component. The attributes and parameters are accepted for well defining this commandexecutor are:
>
>
This executor implements the CREAM's job management capabilities (e.g. jobSubmit, jobCancel, jobInfo, etc). CREAM interacts with the BLAH component, an abstraction layer providing a unified interface to the underlying LRMS. At the time of writing CREAM supports through BLAH the following LRMS: LSF, PBS/Torque, SGE, Condor and SLURM. The list of attributes and parameters which define this executor, complete of their meaning and default values is:
  attributes
  • id: "BLAH executor"
Line: 91 to 126
  parameters
  • SANDBOX_TRANSFER_METHOD: sets the sandbox transfer method (GSIFTP/LRMS) (default: "GSIFTP")
Changed:
<
<
  • CREAM_SANDBOX_DIR: is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
>
>
  • CREAM_SANDBOX_DIR: the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
 
  • CREAM_CREATE_SANDBOX_BIN_PATH: the path of the executable for creating the job sandbox (default: "/usr/bin/glite-cream-createsandboxdir")
  • CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH: the path of the script for copying the user delegation proxy into the specified job sandbox (default: "/usr/bin/glite-cream-copyProxyToSandboxDir.sh")
  • CREAM_PURGE_SANDBOX_BIN_PATH: the path of the executable for purging the job sandbox (default: "/usr/bin/glite-ce-cream-purge-sandbox")
Line: 101 to 136
 
  • MAX_LEASE_TIME: the maximum allowed lease time (in second). I.e. if a client specifies a lease time too big, this value is used instead (dafault: "36000")
  • LEASE_EXECUTION_RATE: specifies how often the job purger has to run (default: "30" minutes)
  • GLEXEC_BIN_PATH: the path of the glexec executable (default: "/usr/sbin/glexec")
Changed:
<
<
  • GLEXEC_CAT_CMD_PATH: is the pathname of the "cat" command invoked by CREAM via glexec (default: "/bin/cat")
  • BLAHP_BIN_PATH: is the path of the blahpd executable (default: "/usr/bin/blahpd")
>
>
  • GLEXEC_CAT_CMD_PATH: the pathname of the "cat" command invoked by CREAM via glexec (default: "/bin/cat")
  • BLAHP_BIN_PATH: the path of the blahpd executable (default: "/usr/bin/blahpd")
 
  • BLAH_JOBID_PREFIX: represents a prefix for job names for BLAH. If the same BLAH parser serves multiple CREAM CEs, please choose a different value for each of these CREAM services. The value MUST be a string 6 characters long that starts with 'cr' and ends with '_' (default: "cream_")
  • BLAH_COMMAND_TIMEOUT: represents the maximum time interval accepted by CREAM for the execution of commands by BLAH (default: "300" seconds)
  • BLPARSER_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")
Changed:
<
<
  • BLPARSER_RETRY_DELAY: is the time interval (ms) between two attempts to contact the BLAH parser (default: "60000")
  • LRMS_EVENT_LISTENER_PORT: is the port used by CREAM to receive notifications about job status changes sent by the BLParser/JobWrapper (default: "49152")
>
>
  • 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. -->
Line: 131 to 166
 

The Activity Executor (EMI-ES)

Changed:
<
<
This Activity Executor implements the EMI-ES functionality. The accepted attributes and parameters are:
>
>
This Activity Executor implements the functionality (e.g. createActivity, getActivityInfo, etc) defined in the EMI-ES specification (v1.16). The list of attributes and parameters which define this executor, complete of their meaning and default values is:
  attributes
  • id: "ActivityExecutor"
Line: 147 to 182
 
  • ACTIVITY_WRAPPER_TEMPLATE_PATH: the path where the ActivityWrapper template is placed (default: "/etc/glite-ce-cream-es/")
  • BDII_URI: defines the BDII URI (e.g. _"ldap://cream.pd.infn.it:2170" _)
  • BDII_RATE: specifies how often CREAM has to get information from the BDII (default: "60" minutes)
Changed:
<
<
  • BLAH_BIN_PATH: is the path of the blahpd executable (default: "/usr/bin/blahpd")
>
>
  • BLAH_BIN_PATH: the path of the blahpd executable (default: "/usr/bin/blahpd")
 
  • BLAH_PREFIX: represents a prefix for job names for BLAH. If the same BLAH parser serves multiple CREAM CEs, please choose a different value for each of these CREAM services. The value MUST be a string 6 characters long that starts with 'cr' and ends with '_' (default: "cr-es_")
  • BLAH_COMMAND_TIMEOUT: represents the maximum time interval accepted by CREAM for the execution of commands by BLAH (default: "300" seconds)
Changed:
<
<
  • BLAH_NOTIFICATION_LISTENER_PORT: is the port used by CREAM to receive notifications about job status changes sent by the BLParser/ActivityWrapper (default: "49155")
>
>
  • 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")
Changed:
<
<
  • BLAH_NOTIFIER_RETRY_DELAY: is the time interval (ms) between two attempts to contact the BLAH parser (default: "60000")
>
>
  • 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)
Line: 165 to 200
 
  • DELEGATION_TIME_SLOT*: (default "3600" seconds)
  • LIMIT_FOR_LIST_ACTIVITIES: defines the maximum number of items contained into the response to be sent back to the client (default: "500")
  • PURGE_SANDBOX_BIN_PATH: the path of the executable for purging the job sandbox (default: "/usr/bin/glite-ce-cream-purge-sandbox")
Changed:
<
<
  • SANDBOX_DIR: is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream-es_sandbox")
>
>
  • SANDBOX_DIR: the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream-es_sandbox")
  * please DO NOT change the default value which comes from the YAIM configuration.
Deleted:
<
<

The Delegation Executor

This Delegation Executor implements delegation functionality. The accepted attributes and parameters are:

attributes

  • id: "DelegationExecutor"
  • category: "DELEGATION_MANAGEMENT" (*)
  • commandqueuesize: "0" (NB: the value MUST be "0" because the executor doesn't need the command queue) (*)
  • commandqueueshared: "false" (*)
  • commandworkerpoolsize: "0" (NB: the value MUST be "0" because the executor doesn't need the command queue) (*)
  • filename: "/usr/share/java/glite-ce-cream-delegationExecutor.jar"

parameters

  • CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH: the path of the script for copying the user delegation proxy into the specified job sandbox (default: "/usr/bin/glite-cream-copyProxyToSandboxDir.sh")
  • CREAM_PURGE_PROXY_FROM_SANDBOX_BIN_PATH: the path of the script for deleting the user delegation proxy from the specified job sandbox (default: "/usr/bin/glite-ce-cream-purge-proxy")
  • CREAM_SANDBOX_DIR: is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
  • DELEGATION_PURGE_RATE: specifies how often the delegation purger has to run (default "10" minutes)

* please DO NOT change the default value which comes from the YAIM configuration.

  -- LisaZangrando - 2012-12-04

Revision 52012-12-06 - LisaZangrando

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

The CREAM configuration file

Line: 48 to 48
 

The CommandExecutor

Changed:
<
<
The commandexeuctor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). More than one commandexecutor can be defined in the configuration file and its XML structure is as following:
>
>
The commandexeuctor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). More than one commandexecutor can be defined in the configuration file and its XML structure is as the following:
 
<commandexecutor
Line: 67 to 67
 
Deleted:
<
<
The above XML structure shows that a commandexeuctor is composed of a set of well defined attributes and a set of parameters which are strictly dependent on the specific commandexecutor.
 The following is the list of the mandatory attributes with their meaning:
  • id: the unique id (*)
  • category: the name of the category to which the commandexecutor belongs (e.g. DELEGATION_MANAGEMENT, JOB_MANAGEMENT, ACTIVITY_MANAGEMENT) (*)
Line: 75 to 74
 
  • commandqueueshared: must be set to false (default) if the command queue is used by a single CREAM; must be set to true if there are multiple CREAM services using a single command queue (i.e. multiple CREAM services managing a single farm) (*)
  • commandworkerpoolsize: the number of threads getting and satisfying user requests stored in the CREAM command queue (default: 50) (*)
  • filename: the path of the jar implementing the commandexecutor (*)
Deleted:
<
<
  • parameter: represents a name/value couple defined for the specific commandexecutor. The name is case-sensitive.
  * please DO NOT change the default value which comes from the YAIM configuration.

The BLAH Executor

Changed:
<
<
This executor implements the CREAM's job management capabilities and it is based on the BLAH component. The following attributes and parameters are accepted for well defining this commandexecutor:
>
>
This executor implements the CREAM's job management capabilities and it is based on the BLAH component. The attributes and parameters are accepted for well defining this commandexecutor are:

attributes

 
  • id: "BLAH executor"
Changed:
<
<
  • category: "JOB_MANAGEMENT"
>
>
  • category: "JOB_MANAGEMENT" (*)
 
  • commandqueuesize: "500"
  • commandqueueshared: "false"
  • commandworkerpoolsize: "50"
Changed:
<
<
  • filename: /usr/share/java/glite-ce-cream-blahExecutor.jar
  • BLAHP_BIN_PATH: parameter which defines the path of the blahpd executable (default: "/usr/bin/blahpd")
  • SANDBOX_TRANSFER_METHOD: sets the sandbox transfer method (GSIFTP/LRMS) (default: "GSIFTP")
  • CREAM_SANDBOX_DIR = is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
  • CREAM_CREATE_SANDBOX_BIN_PATH: the path of the executable for creating the job sandbox (default: "/usr/bin/glite-cream-createsandboxdir")
  • CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH: the path of the script for copying the user delegation proxy into the specified job sandbox (default: "/usr/bin/glite-cream-copyProxyToSandboxDir.sh")
  • CREAM_PURGE_SANDBOX_BIN_PATH: the path of the executable for purging the job sandbox (default: "/usr/bin/glite-ce-cream-purge-sandbox")
  • CREAM_PURGE_PROXY_FROM_SANDBOX_BIN_PATH: the path of the executable for purging the user delegation proxy from the job sandbox (default: "/usr/bin/glite-ce-cream-purge-proxy")
  • CREAM_JOB_SENSOR_HOST: enable this parameter (and set it to the hostname of the CREAM CE) if the CEMon job sensor plugin is installed (as needed for submissions via WMS/ICE) (default: parameter disabled)
  • CREAM_JOB_SENSOR_PORT: represents the port used by CREAM to get notifications from the CEMon job sensor plugin. Enable this parameter if the CEMon job sensor plugin is installed (as needed for submissions via WMS/ICE) (default: "49154")
  • MAX_LEASE_TIME: the maximum allowed lease time (in second). I.e. if a client specifies a lease time too big, this value is used instead (dafault: "36000")
  • LEASE_EXECUTION_RATE: specifies how often the job purger has to run. The value must be specified as minutes (default: "30")
  • GLEXEC_BIN_PATH: the path of the glexec executable (default: "/usr/sbin/glexec")
  • GLEXEC_CAT_CMD_PATH: is the pathname of the "cat" command invoked by CREAM via glexec (default: "/bin/cat")
  • BLAH_JOBID_PREFIX: represents a prefix for job names for BLAH. If the same BLAH parser serves multiple CREAM CEs, please choose a different value for each of these CREAM services. The value MUST be a string 6 characters long that starts with 'cr' and ends with '_' (default: "cream_")
  • BLAH_COMMAND_TIMEOUT: represents the maximum time interval (seconds) accepted by CREAM for the execution of commands by BLAH (default: "300")
  • BLPARSER_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")
  • BLPARSER_RETRY_DELAY: is the time interval (ms) between two attempts to contact the BLAH parser (default: "60000")
  • LRMS_EVENT_LISTENER_PORT: is 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")
>
>
  • filename: "/usr/share/java/glite-ce-cream-blahExecutor.jar"

parameters

  • SANDBOX_TRANSFER_METHOD: sets the sandbox transfer method (GSIFTP/LRMS) (default: "GSIFTP")
  • CREAM_SANDBOX_DIR: is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
  • CREAM_CREATE_SANDBOX_BIN_PATH: the path of the executable for creating the job sandbox (default: "/usr/bin/glite-cream-createsandboxdir")
  • CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH: the path of the script for copying the user delegation proxy into the specified job sandbox (default: "/usr/bin/glite-cream-copyProxyToSandboxDir.sh")
  • CREAM_PURGE_SANDBOX_BIN_PATH: the path of the executable for purging the job sandbox (default: "/usr/bin/glite-ce-cream-purge-sandbox")
  • CREAM_PURGE_PROXY_FROM_SANDBOX_BIN_PATH: the path of the executable for purging the user delegation proxy from the job sandbox (default: "/usr/bin/glite-ce-cream-purge-proxy")
  • CREAM_JOB_SENSOR_HOST: enable this parameter (and set it to the hostname of the CREAM CE) if the CEMon job sensor plugin is installed (as needed for submissions via WMS/ICE) (default: parameter disabled)
  • CREAM_JOB_SENSOR_PORT: represents the port used by CREAM to get notifications from the CEMon job sensor plugin. Enable this parameter if the CEMon job sensor plugin is installed (as needed for submissions via WMS/ICE) (default: "49154")
  • MAX_LEASE_TIME: the maximum allowed lease time (in second). I.e. if a client specifies a lease time too big, this value is used instead (dafault: "36000")
  • LEASE_EXECUTION_RATE: specifies how often the job purger has to run (default: "30" minutes)
  • GLEXEC_BIN_PATH: the path of the glexec executable (default: "/usr/sbin/glexec")
  • GLEXEC_CAT_CMD_PATH: is the pathname of the "cat" command invoked by CREAM via glexec (default: "/bin/cat")
  • BLAHP_BIN_PATH: is the path of the blahpd executable (default: "/usr/bin/blahpd")
  • BLAH_JOBID_PREFIX: represents a prefix for job names for BLAH. If the same BLAH parser serves multiple CREAM CEs, please choose a different value for each of these CREAM services. The value MUST be a string 6 characters long that starts with 'cr' and ends with '_' (default: "cream_")
  • BLAH_COMMAND_TIMEOUT: represents the maximum time interval accepted by CREAM for the execution of commands by BLAH (default: "300" seconds)
  • BLPARSER_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")
  • BLPARSER_RETRY_DELAY: is the time interval (ms) between two attempts to contact the BLAH parser (default: "60000")
  • LRMS_EVENT_LISTENER_PORT: is 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. -->
Changed:
<
<
  • 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_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:
>
>
  • 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_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
    • 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
Changed:
<
<
  • JOB_PURGE_RATE: specifies how often the job purger has to run. The value must be specified as minutes (default "300")
>
>
  • JOB_PURGE_RATE: specifies how often the job purger has to run (default "300" minutes)

* please DO NOT change the default value which comes from the YAIM configuration.

 
Added:
>
>

The Activity Executor (EMI-ES)

This Activity Executor implements the EMI-ES functionality. The accepted attributes and parameters are:

attributes

  • id: "ActivityExecutor"
  • category: "ACTIVITY_MANAGEMENT" (*)
  • commandqueuesize: "500"
  • commandqueueshared: "false"
  • commandworkerpoolsize: "50"
  • filename: "/usr/share/java/glite-ce-cream-activityExecutor.jar"

parameters

  • ACTIVITY_STATUS_MONITOR_AGE: defines how old should be a not terminated activity in order to ask its current status to the LRMS (default: "24" hours)
  • ACTIVITY_STATUS_MONITOR_RATE: specifies how often CREAM checks the status of the not terminated activities (default: "6" hours)
  • ACTIVITY_WRAPPER_TEMPLATE_PATH: the path where the ActivityWrapper template is placed (default: "/etc/glite-ce-cream-es/")
  • BDII_URI: defines the BDII URI (e.g. _"ldap://cream.pd.infn.it:2170" _)
  • BDII_RATE: specifies how often CREAM has to get information from the BDII (default: "60" minutes)
  • BLAH_BIN_PATH: is the path of the blahpd executable (default: "/usr/bin/blahpd")
  • BLAH_PREFIX: represents a prefix for job names for BLAH. If the same BLAH parser serves multiple CREAM CEs, please choose a different value for each of these CREAM services. The value MUST be a string 6 characters long that starts with 'cr' and ends with '_' (default: "cr-es_")
  • BLAH_COMMAND_TIMEOUT: represents the maximum time interval accepted by CREAM for the execution of commands by BLAH (default: "300" seconds)
  • BLAH_NOTIFICATION_LISTENER_PORT: is 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: is 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)
  • 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
  • DEFAULT_QUEUE_NAME: defines the default LRMS's queue used by CREAM if not specified by the user
  • DELEGATION_TIME_SLOT*: (default "3600" seconds)
  • LIMIT_FOR_LIST_ACTIVITIES: defines the maximum number of items contained into the response to be sent back to the client (default: "500")
  • PURGE_SANDBOX_BIN_PATH: the path of the executable for purging the job sandbox (default: "/usr/bin/glite-ce-cream-purge-sandbox")
  • SANDBOX_DIR: is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream-es_sandbox")

* please DO NOT change the default value which comes from the YAIM configuration.

The Delegation Executor

This Delegation Executor implements delegation functionality. The accepted attributes and parameters are:

attributes

  • id: "DelegationExecutor"
  • category: "DELEGATION_MANAGEMENT" (*)
  • commandqueuesize: "0" (NB: the value MUST be "0" because the executor doesn't need the command queue) (*)
  • commandqueueshared: "false" (*)
  • commandworkerpoolsize: "0" (NB: the value MUST be "0" because the executor doesn't need the command queue) (*)
  • filename: "/usr/share/java/glite-ce-cream-delegationExecutor.jar"

parameters

  • CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH: the path of the script for copying the user delegation proxy into the specified job sandbox (default: "/usr/bin/glite-cream-copyProxyToSandboxDir.sh")
  • CREAM_PURGE_PROXY_FROM_SANDBOX_BIN_PATH: the path of the script for deleting the user delegation proxy from the specified job sandbox (default: "/usr/bin/glite-ce-cream-purge-proxy")
  • CREAM_SANDBOX_DIR: is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
  • DELEGATION_PURGE_RATE: specifies how often the delegation purger has to run (default "10" minutes)

* please DO NOT change the default value which comes from the YAIM configuration.

  -- LisaZangrando - 2012-12-04

Revision 42012-12-06 - LisaZangrando

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

The CREAM configuration file

Changed:
<
<

The configuration file structure

>
>
 
Changed:
<
<
The structure of the CREAM configuration file (/opt/glite/etc/glite-ce-cream/cream-config.xml) is composed of three kinds of XML elements:
>
>

The CREAM configuration file structure

The default location of the CREAM configuration file is /opt/glite/etc/glite-ce-cream/cream-config.xml. It is a XML file composed of a set of elements basically of three different types:
 
  • commandexecutor which defines the specific capabilities (e.g. delegation, job management, activity management) provided by CREAM
  • dataSource used for setting up the access to CREAM DB (MySQL)
  • authzchain which defines the security authorization layer based on ARGUS service or gJAF
Changed:
<
<
The CREAM configuration file looks like the following schema:
>
>
The configuration file looks like the following schema:
 
<service id="CREAM service (core2)">
Line: 18 to 19
  <commandexecutor id="the id" category="the category"
Changed:
<
<
commandqueuesize="500" commandqueueshared="false" commandworkerpoolsize="50" filename="/usr/share/java/EXECUTOR_NAME.jar">
>
>
...
  ...
Changed:
<
<
<dataSource name="datasource_creamdb"
>
>
<dataSource name="datasource_name"
  type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory"
Changed:
<
<
driverClassName="org.gjt.mm.mysql.Driver" username="lisa" password="lisa" maxActive="200" maxIdle="30" maxWait="10000" url="jdbc:mysql://localhost:3306/creamdb?autoReconnect=true" validationQuery="SELECT 1" testOnBorrow="true" testWhileIdle="true" timeBetweenEvictionRunsMillis="20000" minEvictableIdleTimeMillis="90000" logAbandoned="false" removeAbandoned="true" removeAbandonedTimeout="30"
>
>
...
  />

Changed:
<
<
<parameter name="blackListFile" value="/etc/lcas/ban_users.db" /> <plugin name="admincheckpip" classname="org.glite.ce.commonj.authz.gjaf.AdminCheckerPIP"> <parameter name="adminList" value="/etc/grid-security/admin-list" />

<plugin name="gridmappdp" classname="org.glite.ce.commonj.authz.gjaf.GridMapServicePDP"> <parameter name="gridMapFile" value="/etc/grid-security/grid-mapfile" />

<plugin name="vomspdp" classname="org.glite.ce.commonj.authz.gjaf.VomsServicePDP"> <parameter name="gridMapFile" value="/etc/grid-security/grid-mapfile" />

>
>
...
 
Changed:
<
<
>
>
...
 

Deleted:
<
<
 

The CommandExecutor

Changed:
<
<
The commandexecutor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). Its XML structure is as following:
>
>
The commandexeuctor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). More than one commandexecutor can be defined in the configuration file and its XML structure is as following:
 
<commandexecutor
Line: 99 to 64
  ...
Added:
>
>
 
Changed:
<
<
The list the commandexecutor attributes and elements with their meaning:
>
>
The above XML structure shows that a commandexeuctor is composed of a set of well defined attributes and a set of parameters which are strictly dependent on the specific commandexecutor. The following is the list of the mandatory attributes with their meaning:
 
  • id: the unique id (*)
  • category: the name of the category to which the commandexecutor belongs (e.g. DELEGATION_MANAGEMENT, JOB_MANAGEMENT, ACTIVITY_MANAGEMENT) (*)
  • commandqueuesize: the size of the in memory prefetched command queue (default: 500) (*)
Line: 110 to 77
 
  • filename: the path of the jar implementing the commandexecutor (*)
  • parameter: represents a name/value couple defined for the specific commandexecutor. The name is case-sensitive.
Changed:
<
<
* you shouldn't need to change the proposed default.
>
>
* please DO NOT change the default value which comes from the YAIM configuration.
 
Changed:
<
<

The BLAH Executor

>
>

The BLAH Executor

 This executor implements the CREAM's job management capabilities and it is based on the BLAH component. The following attributes and parameters are accepted for well defining this commandexecutor:
  • id: "BLAH executor"
  • category: "JOB_MANAGEMENT"

Revision 32012-12-05 - LisaZangrando

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

The CREAM configuration file

Changed:
<
<
The structure of the CREAM configuration file (/opt/glite/etc/glite-ce-cream/cream-config.xml) is composed of three kind of XML elements:
  • commandexecutor which defines the specific capabilities provided by the CREAM instance
>
>

The configuration file structure

The structure of the CREAM configuration file (/opt/glite/etc/glite-ce-cream/cream-config.xml) is composed of three kinds of XML elements:

  • commandexecutor which defines the specific capabilities (e.g. delegation, job management, activity management) provided by CREAM
 
  • dataSource used for setting up the access to CREAM DB (MySQL)
  • authzchain which defines the security authorization layer based on ARGUS service or gJAF
Added:
>
>
The CREAM configuration file looks like the following schema:

<service id="CREAM service (core2)">

    <commandexecutor
          id="the id"
          category="the category"
          commandqueuesize="500"
          commandqueueshared="false"
          commandworkerpoolsize="50"
          filename="/usr/share/java/EXECUTOR_NAME.jar">
          <parameter name="name_1" value="value_1" />
          <parameter name="name_2" value="value_2" />
          ...
          <parameter name="name_x" value="value_x" />
    </commandexecutor>

    <dataSource name="datasource_creamdb"
              type="javax.sql.DataSource"
              factory="org.apache.commons.dbcp.BasicDataSourceFactory"
              driverClassName="org.gjt.mm.mysql.Driver"
              username="lisa" password="lisa"
              maxActive="200"
              maxIdle="30"
              maxWait="10000"
              url="jdbc:mysql://localhost:3306/creamdb?autoReconnect=true"
              validationQuery="SELECT 1"
              testOnBorrow="true"
              testWhileIdle="true"
              timeBetweenEvictionRunsMillis="20000"
              minEvictableIdleTimeMillis="90000"
              logAbandoned="false"
              removeAbandoned="true"
              removeAbandonedTimeout="30"
    />

    <authzchain name="chain-1">
        <plugin name="localuserpip" classname="org.glite.ce.commonj.authz.gjaf.LocalUserPIP">
             <parameter name="glexec_bin_path" value="/usr/sbin/glexec" />
             <parameter name="glexec_probe_cmd" value="/usr/bin/id" />
             <parameter name="methods" value="JobRegister, putProxy, getProxyReq, renewProxyReq, getTerminationTime, destroy" />
        </plugin>
        <plugin name="bannerpdp" classname="org.glite.ce.commonj.authz.gjaf.BlackListServicePDP">
      <parameter name="blackListFile"
                 value="/etc/lcas/ban_users.db" />
    </plugin>
    <plugin name="admincheckpip"
            classname="org.glite.ce.commonj.authz.gjaf.AdminCheckerPIP">
      <parameter name="adminList"
                 value="/etc/grid-security/admin-list" />
    </plugin>

    <plugin name="gridmappdp"
            classname="org.glite.ce.commonj.authz.gjaf.GridMapServicePDP">
      <parameter name="gridMapFile"
                 value="/etc/grid-security/grid-mapfile" />
    </plugin>

    <plugin name="vomspdp"
            classname="org.glite.ce.commonj.authz.gjaf.VomsServicePDP">
      <parameter name="gridMapFile"
                 value="/etc/grid-security/grid-mapfile" />
    </plugin>

  </authzchain>

</service>
 

The CommandExecutor

Changed:
<
<
The commandexecutor represent the implementation of specific functionality provided by CREAM (e.g. delegation, job management, EMI-ES activity management). Its XML structure is as following:
>
>
The commandexecutor represents the implementation of specific functionality provided by CREAM (e.g. delegation, job management, activity management). Its XML structure is as following:
 
<commandexecutor

Revision 22012-12-04 - LisaZangrando

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

The CREAM configuration file

Line: 9 to 8
 
  • authzchain which defines the security authorization layer based on ARGUS service or gJAF
Added:
>
>
 

The CommandExecutor

The commandexecutor represent the implementation of specific functionality provided by CREAM (e.g. delegation, job management, EMI-ES activity management). Its XML structure is as following:

Revision 12012-12-04 - LisaZangrando

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

The CREAM configuration file

The structure of the CREAM configuration file (/opt/glite/etc/glite-ce-cream/cream-config.xml) is composed of three kind of XML elements:

  • commandexecutor which defines the specific capabilities provided by the CREAM instance
  • dataSource used for setting up the access to CREAM DB (MySQL)
  • authzchain which defines the security authorization layer based on ARGUS service or gJAF

The CommandExecutor

The commandexecutor represent the implementation of specific functionality provided by CREAM (e.g. delegation, job management, EMI-ES activity management). Its XML structure is as following:

<commandexecutor
      id="the id"
      category="the category"
      commandqueuesize="500"
      commandqueueshared="false"
      commandworkerpoolsize="50"
      filename="/usr/share/java/EXECUTOR_NAME.jar">
      <parameter name="name_1" value="value_1" />
      <parameter name="name_2" value="value_2" />
      ...
      <parameter name="name_x" value="value_x" />
</commandexecutor>

The list the commandexecutor attributes and elements with their meaning:

  • id: the unique id (*)
  • category: the name of the category to which the commandexecutor belongs (e.g. DELEGATION_MANAGEMENT, JOB_MANAGEMENT, ACTIVITY_MANAGEMENT) (*)
  • commandqueuesize: the size of the in memory prefetched command queue (default: 500) (*)
  • commandqueueshared: must be set to false (default) if the command queue is used by a single CREAM; must be set to true if there are multiple CREAM services using a single command queue (i.e. multiple CREAM services managing a single farm) (*)
  • commandworkerpoolsize: the number of threads getting and satisfying user requests stored in the CREAM command queue (default: 50) (*)
  • filename: the path of the jar implementing the commandexecutor (*)
  • parameter: represents a name/value couple defined for the specific commandexecutor. The name is case-sensitive.

* you shouldn't need to change the proposed default.

The BLAH Executor

This executor implements the CREAM's job management capabilities and it is based on the BLAH component. The following attributes and parameters are accepted for well defining this commandexecutor:
  • id: "BLAH executor"
  • category: "JOB_MANAGEMENT"
  • commandqueuesize: "500"
  • commandqueueshared: "false"
  • commandworkerpoolsize: "50"
  • filename: /usr/share/java/glite-ce-cream-blahExecutor.jar
  • BLAHP_BIN_PATH: parameter which defines the path of the blahpd executable (default: "/usr/bin/blahpd")
  • SANDBOX_TRANSFER_METHOD: sets the sandbox transfer method (GSIFTP/LRMS) (default: "GSIFTP")
  • CREAM_SANDBOX_DIR = is the directory where the sandbox files are staged on the CREAM CE node (default: "/var/cream_sandbox")
  • CREAM_CREATE_SANDBOX_BIN_PATH: the path of the executable for creating the job sandbox (default: "/usr/bin/glite-cream-createsandboxdir")
  • CREAM_COPY_PROXY_TO_SANDBOX_BIN_PATH: the path of the script for copying the user delegation proxy into the specified job sandbox (default: "/usr/bin/glite-cream-copyProxyToSandboxDir.sh")
  • CREAM_PURGE_SANDBOX_BIN_PATH: the path of the executable for purging the job sandbox (default: "/usr/bin/glite-ce-cream-purge-sandbox")
  • CREAM_PURGE_PROXY_FROM_SANDBOX_BIN_PATH: the path of the executable for purging the user delegation proxy from the job sandbox (default: "/usr/bin/glite-ce-cream-purge-proxy")
  • CREAM_JOB_SENSOR_HOST: enable this parameter (and set it to the hostname of the CREAM CE) if the CEMon job sensor plugin is installed (as needed for submissions via WMS/ICE) (default: parameter disabled)
  • CREAM_JOB_SENSOR_PORT: represents the port used by CREAM to get notifications from the CEMon job sensor plugin. Enable this parameter if the CEMon job sensor plugin is installed (as needed for submissions via WMS/ICE) (default: "49154")
  • MAX_LEASE_TIME: the maximum allowed lease time (in second). I.e. if a client specifies a lease time too big, this value is used instead (dafault: "36000")
  • LEASE_EXECUTION_RATE: specifies how often the job purger has to run. The value must be specified as minutes (default: "30")
  • GLEXEC_BIN_PATH: the path of the glexec executable (default: "/usr/sbin/glexec")
  • GLEXEC_CAT_CMD_PATH: is the pathname of the "cat" command invoked by CREAM via glexec (default: "/bin/cat")
  • BLAH_JOBID_PREFIX: represents a prefix for job names for BLAH. If the same BLAH parser serves multiple CREAM CEs, please choose a different value for each of these CREAM services. The value MUST be a string 6 characters long that starts with 'cr' and ends with '_' (default: "cream_")
  • BLAH_COMMAND_TIMEOUT: represents the maximum time interval (seconds) accepted by CREAM for the execution of commands by BLAH (default: "300")
  • BLPARSER_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")
  • BLPARSER_RETRY_DELAY: is the time interval (ms) between two attempts to contact the BLAH parser (default: "60000")
  • LRMS_EVENT_LISTENER_PORT: is 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_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_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
    • 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
  • JOB_PURGE_RATE: specifies how often the job purger has to run. The value must be specified as minutes (default "300")

-- LisaZangrando - 2012-12-04

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