Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
The configuration file looks like the following schema: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | The CREAM configuration file for the EMI-2 release | |||||||
> > | The CREAM configuration file for both EMI-2 and EMI-3 releases | |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
The CREAM configuration file for the EMI-2 release | ||||||||
Line: 144 to 144 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 188 to 188 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
The CREAM configuration file for the EMI-2 release | ||||||||
Line: 8 to 8 | ||||||||
The CREAM configuration file structureThe 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:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
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 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 204 to 204 | ||||||||
* please DO NOT change the default value which comes from the YAIM configuration. | ||||||||
Added: | ||||||||
> > | The JDBC datasource configurationCREAM 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 configurationCREAM 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
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 ExecutorThe 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
<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
| ||||||||
Line: 91 to 126 | ||||||||
parameters
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 101 to 136 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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
| ||||||||
Line: 147 to 182 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 165 to 200 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
* please DO NOT change the default value which comes from the YAIM configuration. | ||||||||
Deleted: | ||||||||
< < | The Delegation ExecutorThis Delegation Executor implements delegation functionality. The accepted attributes and parameters are: attributes
| |||||||
-- LisaZangrando - 2012-12-04 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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:
| ||||||||
Line: 75 to 74 | ||||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
* 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 | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > | The Activity Executor (EMI-ES)This Activity Executor implements the EMI-ES functionality. The accepted attributes and parameters are: attributes
The Delegation ExecutorThis Delegation Executor implements delegation functionality. The accepted attributes and parameters are: attributes
| |||||||
-- LisaZangrando - 2012-12-04 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 structureThe 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: | |||||||
| ||||||||
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: | ||||||||
< < | | |||||||
> > | | |||||||
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: | |||||||
| ||||||||
Line: 110 to 77 | ||||||||
| ||||||||
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:
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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:
| |||||||
> > |
The configuration file structureThe structure of the CREAM configuration file (/opt/glite/etc/glite-ce-cream/cream-config.xml) is composed of three kinds of XML elements:
| |||||||
| ||||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
The CREAM configuration file | ||||||||
Line: 9 to 8 | ||||||||
| ||||||||
Added: | ||||||||
> > | ||||||||
The CommandExecutorThe 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: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
The CREAM configuration fileThe structure of the CREAM configuration file (/opt/glite/etc/glite-ce-cream/cream-config.xml) is composed of three kind of XML elements:
The CommandExecutorThe 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:
The BLAH ExecutorThis 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:
|