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/Resources/storage.rst
+29-2Lines changed: 29 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ DIRAC provides an abstraction of a SE interface that allows to access different
20
20
# The name of the DIRAC Plugin module to be used for implementation
21
21
# of the access protocol
22
22
PluginName = SRM2
23
-
# Flag specifying the access type (local/remote)
23
+
# Flag specifying the access type (local/remote/remoteonly)
24
24
Access = remote
25
25
# Protocol name
26
26
Protocol = srm
@@ -50,6 +50,7 @@ Configuration options are:
50
50
* ``UseCatalogURL``: default ``False``. If ``True``, use the url stored in the catalog instead of regenerating it
51
51
* ``ChecksumType``: default ``ADLER32``. NOT ACTIVE !
52
52
* ``Alias``: when set to the name of another storage element, it instanciates the other SE instead.
53
+
* ``Access``: Can be ``local``, ``remote`` or ``remoteonly``. Options specify that the protocol can be used in local (e.g. upload from a WN to local SE), remote+local or remote context.
53
54
* ``ReadAccess``: default ``True``. Allowed for Read if no RSS enabled (:ref:`activateRSS`)
54
55
* ``WriteAccess``: default ``True``. Allowed for Write if no RSS enabled
55
56
* ``CheckAccess``: default ``True``. Allowed for Check if no RSS enabled
@@ -221,7 +222,7 @@ There are also a set of plugins based on the `gfal2 libraries <https://dmc-docs.
221
222
222
223
Default plugin options:
223
224
224
-
* ``Access``: ``Remote``or ``Local``. If ``Local``, then this protocol can be used only if we are running at the site to which the SE is associated. Typically, if a site mounts the storage as NFS, the ``file`` protocol can be used.
225
+
* ``Access``: ``Remote``, ``Local`` or ``RemoteOnly``. If ``Local``, then this protocol can be used only if we are running at the site to which the SE is associated. Typically, if a site mounts the storage as NFS, the ``file`` protocol can be used. If ``RemoteOnly``, this protocol is not used when running at the site. For example, if you need to use a different hostname within the site than from outside.
225
226
* InputProtocols/OutputProtocols: a given plugin normally contain a hard coded list of protocol it is able to generate or accept as input. There are however seldom cases (like SRM) where the site configuration may change these lists. These options are here to accomodate for that case.
226
227
227
228
GRIDFTP Optimisation
@@ -317,6 +318,32 @@ You need to define a protocol section with SRM, specifying that a ``file`` URL c
317
318
}
318
319
319
320
321
+
RemoteOnly protocol definition
322
+
------------------------------
323
+
324
+
Some sites may want you to have a different endpoint when running on the worker node than when transfering files via FTS. Or they recommend a protocol remotely only. This is possible with the ``RemoteOnly`` only option::
0 commit comments