Experiment Requirements

Short description of the behavior that the experiments expect:

• All software for the experiment is installed relative to a path. The path is accessible through an environment variable.
  

  
  

  Example: VO_ALICE_SW_DIR

  
  

• No root access is required to install experiment software.
• A subset of the experiments users can write into this area. This can be done by creating special users (we refer to these users as the Experiment Software Managers (ESM)). An ESM should be able to add/remove software at any time without communication with the site managers
• The software has to be accessible on the WN through POSIX calls.
• The ESM should be able to install software on a per site base.
• The ESM should be able to verify the installation in separate steps. Different kind of validation procedures can be run by the ESM at different moments
• The experiment software manager must have the possibility to publish as TAGs all installed versions in order to direct jobs to the sites. It is the ESM's responsibility to run certification tests before publishing the availability of the software on a site. Publishing of the TAG for a given release of the software installed can happen in separate steps with respect to the installation step.
• It is understood that the experiment software depends on certain software. The experiments agree that they will manage the dependencies. In this context this means that they have to install missing packages together with their software.