Difference between revisions of "EES"
(→Further reading: Updated link to design doc) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
* [[EES Service Reference Card]] | * [[EES Service Reference Card]] | ||
| − | * See also [ | + | * See also the links under [[EES#Further_reading|Further reading]] |
== Test plan == | == Test plan == | ||
| Line 18: | Line 18: | ||
== Further reading == | == Further reading == | ||
| − | * [https://edms.cern.ch/document/1018216/1 The EES design document] | + | * [https://edms.cern.ch/document/1018216/1.3 The EES design document] |
| + | |||
| + | * [https://twiki.cern.ch/twiki/bin/view/EGEE/ArgusEMIDeployment Argus installation instructions] | ||
Latest revision as of 20:10, 8 November 2015
The EES, the Execution Environment Service, is the site-local mapping component of the gLite Authorization Framework. It converts grid-wide or logical obligations into site-specific execution environments, supported by any attribute the job carries from the user or the VO. Examples may be the assignment of a site-local Unix uid out of a pool based on FQAN attributes given by the VO; or setting the primary Unix group based on the obligation to run a job in a particular logical share, or configuring a machine image to be executed in a virtual machine hosting environment on a worker node. Through the planned site-customizable scripts in perl, site managers can easily extend the functionality.
The role of the Execution Environment Service (EES) is to ensure that an appropriate site-specific execution environment is procured that allows an already-authorized task to be executed on a site-local resource. This environment must honour any obligations and characteristics specified by the effective Policy on which the positive Decision to authorize was based.
Sysadmin information
- See also the links under Further reading
