Difference between revisions of "Set up gLExec for Argus"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 6: Line 6:
  
 
For the installation of gLExec on the worker node, see [http://glite.web.cern.ch/glite/packages/R3.2/sl5_x86_64/deployment/glite-GLEXEC_wn/3.2.2-2.sl5/glite-GLEXEC_wn-3.2.2-2.sl5-update.html the release notes] and the [https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide320 installation manual].
 
For the installation of gLExec on the worker node, see [http://glite.web.cern.ch/glite/packages/R3.2/sl5_x86_64/deployment/glite-GLEXEC_wn/3.2.2-2.sl5/glite-GLEXEC_wn-3.2.2-2.sl5-update.html the release notes] and the [https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide320 installation manual].
 +
 +
Typical gLite installation is done with
 +
 +
wget -O /etc/yum.repos.d/glite-GLEXEC_wn.repo http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-GLEXEC_wn.repo
 +
yum install glite-GLEXEC_wn
  
 
== Configuration with YAIM ==
 
== Configuration with YAIM ==

Revision as of 15:11, 27 April 2010

Setting up gLExec on the worker node to query Argus for authorization decisions is preferably done through YAIM, but some set-ups require manual configuration.

Installation

For the installation and configuration of Argus, see the Argus documentation.

For the installation of gLExec on the worker node, see the release notes and the installation manual.

Typical gLite installation is done with

wget -O /etc/yum.repos.d/glite-GLEXEC_wn.repo http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-GLEXEC_wn.repo
yum install glite-GLEXEC_wn

Configuration with YAIM

Please see the YAIM guide for general instructions on using YAIM, and the list of variables that need to be set in site-info.def, or siteinfo/services/glexec-wn.

Noteworthy variables:

GLEXEC_WN_OPMODE=setuid
GLEXEC_WN_ARGUS_ENABLED=yes
ARGUS_PEPD_ENDPOINTS="https://argus1.example.com:8154/authz https://argus2.example.com:8145/authz"

In this example the site has two service endpoints; the quotes are necessary as this is interpreted shell code. Multiple endpoints may be defined for scale; the pep-c plug-in will randomly choose one endpoint to talk to, and automatically fail-over to the others. (?? Verify please)

Manual Configuration