Difference between revisions of "HOWTO set up gLExec on the worker node"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 21: | Line 21: | ||
;my site makes use of third party plug-ins for [[LCMAPS]] | ;my site makes use of third party plug-ins for [[LCMAPS]] | ||
| − | : You could still try to [[set up gLExec for Argus]], and use the plug-in from gLExec. If the plug-in should be run centrally, [[gLExec with | + | : You could still try to [[set up gLExec for Argus]], and use the plug-in from gLExec. If the plug-in should be run centrally, [[set up gLExec with SCAS]] instead. |
;My site uses the LDAP enforcement plug-in for [[LCMAPS]] | ;My site uses the LDAP enforcement plug-in for [[LCMAPS]] | ||
| − | : Set up | + | : [[Set up gLExec with SCAS]], and configure [[SCAS]] to use the [[LCMAPS#Enforcement plug-ins|ldap_enf plug-in]]. |
;Users are authorised through secondary group mappings | ;Users are authorised through secondary group mappings | ||
| − | :As Argus doesn't support secondary group mappings, | + | :As Argus doesn't support secondary group mappings, [[set up gLExec with SCAS]] instead. |
;I need a site-wide centralized authorization service, for the CEs as well as the WNs | ;I need a site-wide centralized authorization service, for the CEs as well as the WNs | ||
:The tested option in this case is [[SCAS]], but [https://twiki.cern.ch/twiki/bin/view/EGEE/AuthorizationFramework Argus] ''should'' work as well; [[configure CREAM for use with SCAS]]. | :The tested option in this case is [[SCAS]], but [https://twiki.cern.ch/twiki/bin/view/EGEE/AuthorizationFramework Argus] ''should'' work as well; [[configure CREAM for use with SCAS]]. | ||
;I've tried Argus and I found a problem | ;I've tried Argus and I found a problem | ||
:[http://www.ggus.org/ Report a bug] on Argus; if the problem is a show stopper, try [[SCAS]] as a (temporary) alternative. | :[http://www.ggus.org/ Report a bug] on Argus; if the problem is a show stopper, try [[SCAS]] as a (temporary) alternative. | ||
Revision as of 14:04, 26 April 2010
This guide will help you make a choice in deployment and configuration for gLExec on the worker node on your site.
Prerequisites
Prerequisite is that you already have a Grid site, including a Compute Element (LCG-CE and/or CREAM-CE) and worker nodes. For more general guidelines for site setup and configuration, see the gLite documentation.
See also the gLite release notes and the Installation Guide.
Central authorization service
It is recommended to set up a central authorization service, either
- Set up gLExec for Argus, which is the recommended solution (but see the checklist below), or
- Set up gLExec with SCAS, in some special cases
Both options are fully supported, YAIM configurable and offer similar functionality. See Argus, SCAS.
Special cases
Check if any of the following apply.
- my site makes use of third party plug-ins for LCMAPS
- You could still try to set up gLExec for Argus, and use the plug-in from gLExec. If the plug-in should be run centrally, set up gLExec with SCAS instead.
- My site uses the LDAP enforcement plug-in for LCMAPS
- Set up gLExec with SCAS, and configure SCAS to use the ldap_enf plug-in.
- Users are authorised through secondary group mappings
- As Argus doesn't support secondary group mappings, set up gLExec with SCAS instead.
- I need a site-wide centralized authorization service, for the CEs as well as the WNs
- The tested option in this case is SCAS, but Argus should work as well; configure CREAM for use with SCAS.
- I've tried Argus and I found a problem
- Report a bug on Argus; if the problem is a show stopper, try SCAS as a (temporary) alternative.
