Birmingham CAGE Test Bench
A description of Cream ce /Argus/Glexec_wn/lcg-cE (
CAGE) test installation at Birmingham.
Context
ALICE have requested Birmingham install a
CreamCE, which should be able to submit jobs to all WNs supporting the ALICE VO. ATLAS does not support
CreamCE submission yet, so the same WNs also need to accept jobs from a conventional lcg-CE.
ATLAS does support multi-user pilot jobs though, so the WNs must be able to execute glexec. Other
GridPP? sites have tested this functionality in the context of an SCAS server. This test bench makes use of ARGUS to decide on authentication requests.
Installation
Installation of all test nodes is managed by the cfengine server on epgmo1. Below are instructions for completing the installation manually.
GLEXEC_wn
ARGUS
- Setup the glite-ARGUS and lcg-CA yum repos.
- Install the following:
yum -y install lcg-CA
yum -y install jpackage-utils
yum -y install glite-ARGUS
- The node is configured with the yaim command
/opt/glite/yaim/bin/yaim -c -s /root/yaim-conf/site-info.def -n ARGUS_server
. The relevant yaim variables can be found here.
- In order for dteam to use glexec, the appropriate policies have to be defined. Full details can be found here. A simple policy could be:
resource "http://authz-interop.org/xacml/resource/resource-type/wn" {
action "http://authz-interop.org/xacml/action/action-type/execute-now" {
rule permit { vo = dteam }
}
}
which, if stored in the file dteam_policy
, can be loaded using the command pap-admin apf dteam_policy
.
- The ARGUS server should be able to communicate with itself (ie localhost) on ports 8150-8153 (INPUT only), and any node requesting authentication services on 8154 (INPUT only).
Cream CE
lcg-CE
Testing
Dteam Job Submission
ATLAS Job Submission
GLExec Functionality
Renaming pool accounts
--
ChristopherCurtis - 24 Mar 2010
Topic revision: r3 - 25 Mar 2010
- _47C_61UK_47O_61eScience_47OU_61Birmingham_47L_61ParticlePhysics_47CN_61christopher_32curtis?