Resources / Computing¶
In this section options for ComputingElements can be set
Location for Parameters¶
Options for computing elements can be set at different levels, from lowest to highest prority
/Resources/Computing/OSCompatibility
This section is used to define a compatibility matrix between dirac platforms (dirac-platform) and OS versions.
An example of this session is the following:
OSCompatibility
{
Linux_x86_64_glibc-2.5 = x86_64_CentOS_Carbon_6.6
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Carbon_6.7
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Core_7.4
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Core_7.5
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Final_6.4
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Final_6.7
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Final_6.9
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Final_7.4
Linux_x86_64_glibc-2.5 += x86_64_CentOS_Final_7.5
Linux_x86_64_glibc-2.5 += x86_64_RedHatEnterpriseLinuxServer_6.7_Santiago
Linux_x86_64_glibc-2.5 += x86_64_RedHatEnterpriseLinuxServer_7.2_Maipo
Linux_x86_64_glibc-2.5 += x86_64_Scientific_6_6.9
Linux_x86_64_glibc-2.5 += x86_64_Scientific_Carbon_6.8
Linux_x86_64_glibc-2.5 += x86_64_Scientific_Carbon_6.9
Linux_x86_64_glibc-2.5 += x86_64_ScientificCERNSLC_Boron_6.5
Linux_x86_64_glibc-2.5 += x86_64_ScientificCERNSLC_Carbon_6.3
Linux_x86_64_glibc-2.5 += x86_64_ScientificCERNSLC_Carbon_6.4
Linux_x86_64_glibc-2.5 += x86_64_ScientificCERNSLC_Carbon_6.5
Linux_x86_64_glibc-2.5 += x86_64_ScientificCERNSLC_Carbon_6.6
Linux_x86_64_glibc-2.5 += x86_64_ScientificCERNSLC_Carbon_6.7
Linux_x86_64_glibc-2.5 += x86_64_ScientificCERNSLC_Carbon_6.9
Linux_x86_64_glibc-2.5 += x86_64_ScientificLinux-6.9_0_0
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Boron_6.4
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.10
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.3
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.4
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.5
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.6
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.7
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.8
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.9
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6x
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Carbon_6.x
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_Nitrogen_7.4
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_SL_6.4
Linux_x86_64_glibc-2.5 += x86_64_ScientificSL_SL_6.5
Linux_x86_64_glibc-2.5 += x86_64_SL_Nitrogen_7.2
}
What’s on the left is an example of a dirac platform as determined the dirac-platform script (dirac-platform). This platform is declared to be compatible with a list of “OS” strings. These strings are identifying the architectures of computing elements. This list of strings can be constructed from the “Architecture” + “OS” fields that can be found in the CEs description in the CS (Resources / Sites - Subsections).
This compatibility is, by default, used by the SiteDirector when deciding if to send a pilot or not to a certain CE: the SiteDirector matches “TaskQueues” to Computing Element capabilities.
Other subsections are instead used to describe specific types of computing elements:
/Resources/Computing/CEDefaults for all computing elements
/Resources/Computing/<CEType> for CEs of a given type, e.g., HTCondorCE or ARC
/Resources/Sites/<grid>/<site>/CEs for all CEs at a given site
/Resources/Sites/<grid>/<site>/CEs/<CEName> for a specific CE
Values are overwritten by the most specialized option.
General Parameters¶
These parameters are valid for all types of computing elements
Name |
Description |
Example |
GridEnv |
Default environment file sourced before calling grid commands, without extension ‘.sh’. |
/opt/dirac/gridenv (when the file is gridenv.sh) |
SharedArea |
Will be added to the pilot configuration as /LocalSite/SharedArea |
/cvmfs/lhcb.cern.ch/lib |
ExtraPilotOptions |
For adding some generic pilot options. (only for pilots submitted by SiteDirectors) |
–userEnvVariables DIRACSYSCONFIG:::pilot.cfg will add the environment variable DIRACSYSCONFIG (see Environment Variables to Configure DIRAC Behaviour) |
GLUE2ComputingShareMaxSlotsPerJob_limit |
The upper limit for the NumberOfProcessors queue
parameter set by the
|
8 |
ARC CE Parameters¶
Name |
Description |
Example |
XRSLExtraString |
Default additional string for ARC submit files |
|
XRSLMPExtraString |
Default additional string for ARC submit files for multi-processor jobs. |
|
Host |
The host for the ARC CE, used to overwrite the ce name |
|
WorkingDirectory |
Directory where the pilot log files are stored locally. |
/opt/dirac/pro/runit/WorkloadManagement/SiteDirectorArc |
Singularity CE Parameters¶
Name |
Description |
Example |
ContainerRoot |
The root image location for the container to use. |
/cvmfs/cernvm-prod.cern.ch/cvm4 (Default: /cvmfs/cernvm-prod.cern.ch/cvm3) |
ContainerBin |
The binary to start the container |
/opt/extras/bin/singularity (default: singularity) |
ContainerBind |
List of directories to bind |
/etc/grid-security,someDir:::BoundHere |
ContainerOptions |
Extra options for starting the container |
–cleanenv |
InstallDIRACInContainer |
Flag for re-installing, or not, DIRAC in the container |
False (default: True) |
ContainerExtraOpts |
Extra options for dirac-install within the container. |
|
KeepWorkArea |
If set to True container work area won’t be deleted at end of job |
True (Default: False) |
HTCondorCE Parameters¶
For the options for the HTCondorCEs see HTCondorCEComputingElement
CREAM CE Parameters¶
Name |
Description |
Example |
ExtraJDLParameters |
Additional JDL parameters to submit pilot jobs to CREAm CE. Separate entries with “;”. |
ExtraJDLParameters = GPUNumber=1; OneMore=”value” |