admins
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admins [2018/11/22 12:23] bbosak@man.poznan.pl [The VECMA directory structure] |
admins [2018/11/22 21:41] (current) bbosak@man.poznan.pl [Software] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Information for Resource Providers and Administrators ====== | ====== 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. | + | This page provides basic requirements and conventions of VECMA project that should be addressed by resource providers and administrators. |
| + | |||
| + | ===== Accounts ===== | ||
| + | Each site should create accounts for VECMA users. The accounts should be granted to submit jobs into the queuing system. | ||
| ===== Common directory for VECMA ===== | ===== 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. | 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: ==== | ==== The locations of VECMA directories on resources: ==== | ||
| ^ Resource ^ Location ^ MODULEPATH ^ | ^ Resource ^ Location ^ MODULEPATH ^ | ||
| - | | Eagle | ''/home/plgrid-groups/plggvecma/'' | ''/home/plgrid-groups/plggvecma/Modules'' | | + | | Eagle | ''/home/plgrid-groups/plggvecma/'' | ''/home/plgrid-groups/plggvecma/.qcg-modules'' | |
| | SuperMuc NG | | | | | SuperMuc NG | | | | ||
| - | | Bull | | | | + | | Bull | |
| - | ===== Module naming conventions ===== | + | ===== Software ===== |
| - | The modules created for the VECMA project on all resources should follow the following scheme: | + | Each site should install QCG middleware on its resources. The users should be allowed to submit jobs via QCG using X509 certificates. |
| - | ^ 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
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
