This page is obsolete; please refer to the Runtime Environment Registry
:: Introduction :: Repository ::
For a complete description of the Resource Specification Language, Information System, User Interface and the Grid Manager, see the NorduGrid documentation.
Runtime environment as regarded by the ARC middleware is a set of software, complete with corresponding setup script (bash) which defines necessary UNIX environment variables, allowing execution of specific applications. Alternatively, the runtime environment can consist of a single (possibly empty) setup script, just to serve as a flag to indicate presence of a particular software, data or resource.
The setup scripts are executed (bash source) by the ARC gatekeeper (a.k.a. the Grid Manager) prior to and after job execution, so that the job will run in a proper environment, with pathes and variables set accordingly.
In order to make the runtime environment tag published in the information system, and hence to inform users and clients of the presence of the specific software, the setup script must be named after the environment, e.g., MYSOFT-v2.0, and placed in a dedicated directory, known to the gatekeeper.
Location of the directory holding the collection of runtime environments is arbitrary, and is pointed to by the configurable variable $RUNTIME_CONFIG_DIR.
Runtime environments are typically required by large research groups, dealing with a common set of software. It is important to note that such software must not include servers and daemons, or any other services. It is always up to local system administrators to take a decision whether to enable a particular runtime environment or not.
Individual users may request installation of their specific sets of software as a runtime environment; however, it is not perceived as feasible, and such a request can be satisfied only in exceptional cases.
In order to request a specific runtime environment, users have to define it in the job description xRSL file, by adding the following:
(runTimeEnvironment=ENV1)
Here "ENV1" is an example of a string specifying the environment name. The site to process the job will then be chosen by the User Interface among those advertising specified runtime environment. Before starting the job, the Grid Manager will set up UNIX environment variables according to the request, by executing a local script with the name identical to that of the runtime environment.
To request several environments, the attribute strings in xRSL should be simply concatenated:
(runTimeEnvironment=ENV1)(runTimeEnvironment=ENV2)
In general, boolean expressions can be used; for example, to make a disjunct-request, use:
(|(runTimeEnvironment=env1)(runTimeEnvironment=env2))
Environment string interpretation is case-insensitive. Substring specification is possible: in such a case, a partial match will be substituted with a full advertised in the MDS value and only then submitted to the Grid Manager.
Scripts available from this repository must be modified according to local installations
The scripts have to be placed by the system administrator in the pre-defined location RUNTIME_CONFIG_DIR, visible by the Grid Manager
| Environment | Description | Requirements | Defined/modified variables |
| ATLAS-3.2.1 | ATLAS Software release 3.2.1 | Required external packages: ROOT, CERNLIB. |
ATLAS_ROOT ROOTSYS GCC_ROOT GCC_EXEC_PREFIX CPLUS_INCLUDE_PATH PATH LD_LIBRARY_PATH |
| ATLAS-4.0.1 | ATLAS Software release 4.0.1 | Required external packages: ROOT, Java SDK, Geant4, CERNLIB. |
ATLAS_ROOT ROOTSYS GCC_ROOT G4INSTALL G4SYSTEM CMTVERSION CMTROOT JAVA_ROOT CERNLIB CERNBIN GCC_EXEC_PREFIX CPLUS_INCLUDE_PATH PATH LD_LIBRARY_PATH |
| ATLAS-5.3.0 | ATLAS Software release 5.3.0 | Required external packages: ROOT, Java SDK, Geant4, CERNLIB. |
ATLAS_ROOT ROOTSYS GCC_ROOT G4INSTALL G4SYSTEM CMTVERSION CMTROOT JAVA_ROOT GCC_EXEC_PREFIX CPLUS_INCLUDE_PATH PATH LD_LIBRARY_PATH |
| ATLAS-6.0.0 | ATLAS Software release 6.0.0 | Required external packages: ROOT, Java SDK, Geant4, CERNLIB. |
ATLAS_ROOT ROOTSYS GCC_ROOT G4INSTALL G4SYSTEM CMTVERSION CMTROOT JAVA_ROOT GCC_EXEC_PREFIX CPLUS_INCLUDE_PATH PATH LD_LIBRARY_PATH |
| ATLFASTJAPAN | |||
| CERNLIB-2001 | CERNLIB release 2001 |
CERN CERN_LEVEL PATH |
|
| DALTON | Dummy test environment | ||
| DC1-ATLAS-3.2.1 | ATLAS Software release 3.2.1 and Dataset 002000 generated events. | Required external packages: ROOT, CERNLIB. |
ATLAS_ROOT ROOTSYS GCC_ROOT DC1INPUT GCC_EXEC_PREFIX CPLUS_INCLUDE_PATH PATH LD_LIBRARY_PATH |
| DS2003 | Dummy environment to indicate presence of ATLAS Dataset 002003 generated events. | ||
| ECHOENV | Environment for the ngtest test suite, used e.g., for site or middleware validation | ECHOBIN | |
| LOCALDISK | Environment to indicate presence of a local disk at computer nodes. The available disk space can be retrieved from the information system. | LOCALDISK | |
| MD5SUMENV | Environment for the ngtest test suite, used e.g., for site or middleware validation | MD5SUMBIN | |
| MPICH-1.2.4 | Setup for an MPICH parallel processing environment | mpirun | PATH |
| MPICH-1.2.5 | |||
| ROOT-3.01.06 | ROOT release 3.01.06 |
ROOTSYS PATH LD_LIBRARY_PATH |
|
| ROOT-3.03.09 | ROOT release 3.03.09 |
ROOTSYS PATH LD_LIBRARY_PATH |
|
| TEST-ATLAS-4.0.1 | |||
| TEST-ATLAS-5.3.0 | |||
| TEST-ATLAS-JAPAN-4.0.1 | |||
| TEST-MPICH | Test setup for an MPICH parallel processing environment. | ||
| par_test | Test setup for an MPICH parallel processing environment. |