You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/AdministratorGuide/Systems/WorkloadManagement/Pilots/index.rst
+13-15Lines changed: 13 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ DIRAC pilots
8
8
:keywords: Pilots3, Pilot3, Pilot
9
9
10
10
This page describes what are DIRAC pilots, and how they work.
11
-
To know how to develop DIRAC pilots, please refer to the Developers documentation
11
+
To know how to develop DIRAC pilots, please refer to the Developers documentation.
12
12
13
13
Pilot development is done in https://github.com/DIRACGrid/Pilot
14
14
@@ -29,16 +29,18 @@ or IAAC (Infrastructure as a Client) provided that these machines are properly c
29
29
30
30
A pilot has, at a minimum, to:
31
31
32
-
- install DIRAC
32
+
- install or setup DIRAC, or an extension of it
33
33
- configure DIRAC
34
34
- run the JobAgent
35
35
36
-
A pilot has to run on each and every computing resource type, provided that:
36
+
where:
37
37
38
-
- Python 2.6+ on the WN
39
-
- It is an OS onto which we can install a DIRAC client.
40
-
- if that's not possible, we plan to add support for singularity
38
+
- install means installing DIRAC like described in :ref:`dirac_install`
39
+
- setup means that DIRAC code can already be found in the current file system, and it is only a matter of invoking a rc file that would add DIRAC paths
40
+
- configure means adding dirac specific configuration files (which, at a minimum, should include the location of a DIRAC configuration service)
41
41
42
+
43
+
A pilot has to run on each and every computing resource type, provided that Python 2.6+ is on the WN.
42
44
The same pilot script can be used everywhere.
43
45
44
46
.. image:: Pilots2.png
@@ -72,18 +74,20 @@ Administration
72
74
73
75
The following CS section is used for administering the DIRAC pilots::
74
76
75
-
Operations/<Setup>/Pilot
77
+
Operations/Defaults/Pilot
76
78
77
79
These parameters will be interpreted by the WorkloadManagementSystem/SiteDirector agents, and by the WorkloadManagementSystem/Matcher.
78
80
They can also be accessed by other services/agents, e.g. for syncing purposes.
79
81
80
82
Inside this section, you should define the following options, and give them a meaningful value (here, an example is given)::
81
83
82
-
# Needed by the SiteDirector:
83
-
Version = v7r2p1 # DIRAC version(s)
84
+
# For the SiteDirector:
85
+
Version = 8.0.32 # DIRAC version(s) -- a comma-separated list can be provided
84
86
Project = myVO # Your project name: this will end up in the /LocalSite/ReleaseProject option of the pilot cfg, and will be used at matching time
85
87
Extensions = myVO # The DIRAC extension (if any)
86
88
Installation = mycfg.cfg # For an optional configuration file, used by the installation script.
89
+
PreInstalledEnv = /cvmfs/some/where/specific/bashrc # A specific rc file to source for setting up DIRAC
90
+
PreInstalledEnvPrefix = /cvmfs/some/where/ # Location where DIRAC installations can be found. The Pilot will then try and find the following: /cvmfs/some/where/{Version/}{platform}/diracosrc
87
91
# For the Matcher
88
92
CheckVersion = False # True by default, if false any version would be accepted at matching level (this is a check done by the WorkloadManagementSystem/Matcher service).
89
93
@@ -242,19 +246,13 @@ A simple example using the LHCbPilot extension follows::
0 commit comments