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 14:15] bbosak@man.poznan.pl |
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 Modules | | ||
| ==== The locations of VECMA directories on resources: ==== | ==== The locations of VECMA directories on resources: ==== | ||
| Line 19: | Line 12: | ||
| | Eagle | ''/home/plgrid-groups/plggvecma/'' | ''/home/plgrid-groups/plggvecma/.qcg-modules'' | | | Eagle | ''/home/plgrid-groups/plggvecma/'' | ''/home/plgrid-groups/plggvecma/.qcg-modules'' | | ||
| | SuperMuc NG | | | | | SuperMuc NG | | | | ||
| - | | Bull | | | | + | | Bull | |
| - | + | ||
| - | ===== Modules ===== | + | |
| - | + | ||
| - | The administrators should set up the top-level module for the VECMA project called ''vecma''. This module should configure the common settings for all VECMA participants. | + | |
| - | + | ||
| - | When loaded, the module should set up the $VECMA_DIR environment variable that points to the shared directory. | + | |
| - | + | ||
| - | The module files should be put into ''$VECMA_DIR/.qcg-modules'' directory. In this way QCG will automatically load them for the QCG jobs started by the VECMA's users. | + | |
| - | + | ||
| - | ==== 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 | | + | |
| + | ===== Software ===== | ||
| + | Each site should install QCG middleware on its resources. The users should be allowed to submit jobs via QCG using X509 certificates. | ||
admins.1542896136.txt.gz · Last modified: 2018/11/22 14:15 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
