Difference between revisions of "GLExec"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 3: | Line 3: | ||
== Deployment: Installation and setups == | == Deployment: Installation and setups == | ||
| − | * gLExec on the Worker Nodes | + | * gLExec on the Worker Nodes or Computing Element |
** [[Using generic per-node pool accounts or a shared map database]] | ** [[Using generic per-node pool accounts or a shared map database]] | ||
** [[Using the SCAS]] | ** [[Using the SCAS]] | ||
| + | ** [https://twiki.cern.ch/twiki/bin/view/EGEE/AuthZPEPgLExecInfo Using gLExec with Argus]] | ||
** [[Batch System Interoperability]] | ** [[Batch System Interoperability]] | ||
* [[Deployment Scenarios in EGEE and OSG]] | * [[Deployment Scenarios in EGEE and OSG]] | ||
Revision as of 16:15, 5 February 2010
gLExec is a program that acts as a light-weight 'gatekeeper'. gLExec takes Grid credentials as input. By taking the local site policy into account it authenticates and authorizes the credentials. For extra safety gLExec is capable of creating a new execution sandbox based on the Grid credentials. Besides the yes/no control point functionality in the logging-only mode it can create identity specific sandboxes in the identity-switching mode.
Deployment: Installation and setups
- gLExec on the Worker Nodes or Computing Element
- Deployment Scenarios in EGEE and OSG
- Secure installation considerations
- Debugging hints
How To's and FAQ
- To help you master gLExec's security:
- Need to Know's: Explains about the LD_LIBRARY_PATH in combo with setuid programs and other technical details.
- GLExec TransientPilotJobs describes how you may go about managing a target workload's transient area in Pilot Job Frameworks.
- GLExec Environment Wrap and Unwrap scripts describes how you can preserve the environment variables between the calling process of gLExec and the user switched side of gLExec. For example: to preserve the environment variables from a Pilot Job Framework, through gLExec and into Pilot Job Payload.
