admins
This is an old revision of the document!
Table of Contents
Information for Resource Providers and Administrators
This page provides basic requirements and conventions of VECMA project that should be addressed by resource providers and administrators when deploying VECMA software.
Common directory for VECMA
It is required that on each resource a common directory for the VECMA project will be created and made accessible to all VECMA participants.
The VECMA directory structure
It is advised that on each resource the shared directory will have the same, following structure:
| Path | Description |
|---|---|
$VECMA_DIR/Apps | The directory for use by application providers |
$VECMA_DIR/Apps/App1 | The directory for application App1 |
$VECMA_DIR/Apps/AppN | The directory for application AppN … |
$VECMA_DIR/Common | Common stuff, possibly useful for more than one team |
$VECMA_DIR/.qcg-modules | The directory for VECMA Environment Modulesuu |
The locations of VECMA directories on resources:
| Resource | Location | MODULEPATH |
|---|---|---|
| Eagle | /home/plgrid-groups/plggvecma/ | /home/plgrid-groups/plggvecma/Modules |
| SuperMuc NG | ||
| Bull |
Module naming conventions
The modules created for the VECMA project on all resources should follow the following scheme:
| Module | Description |
|---|---|
vecma | The main module for the VECMA project. Will load basic settings |
vecma/apps/App1 | The module for a single application (e.g. App1) |
vecma/common/Item1 | The module for a common software item (e.g. Item1), possibly useful for many teams |
admins.1542889426.txt.gz · Last modified: 2018/11/22 12:23 by bbosak@man.poznan.pl
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
