Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[9.0] docs updates #8007

Open
wants to merge 5 commits into
base: integration
Choose a base branch
from
Open

[9.0] docs updates #8007

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c80f0ee
docs: removed outdated tutorial
fstagni Jan 23, 2025
c1eba94
docs: removed outdated technology previews page
fstagni Jan 23, 2025
6da5aac
docs: removed some old update notices
fstagni Jan 23, 2025
4108686
docs: minor update for proxes upload
fstagni Jan 23, 2025
b76ef47
docs: fix versioning (9.0 instead of 8.1)
fstagni Jan 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/source/AdministratorGuide/Resources/storage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -354,9 +354,7 @@ Multi Protocol with FTS
External services like FTS requires pair of URLs to perform third party copy.
This is implemented using the same logic as described above. There is however an extra step: once the common protocols between 2 SEs have been filtered, an extra loop filter is done to make sure that the selected protocol can be used as read from the source and as write to the destination. Finally, the URLs which are returned are not necessarily the url of the common protocol, but are the native urls of the plugin that can accept/generate the common protocol. For example, if the common protocol is gsiftp but one of the SE has only an SRM plugin, then you will get an srm URL (which is compatible with gsiftp).


.. versionadded:: v7r1p37
The FTS3Agent can now use plugins to influence the list of TPC protocols used. See :ref:`fts3`
The FTS3Agent can use plugins to influence the list of TPC protocols used. See :ref:`fts3`


MultiHop support
Expand Down
2 changes: 1 addition & 1 deletion ...e/AdministratorGuide/ServerInstallations/environment_variable_configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ DIRAC_NO_CFG
If set to anything, cfg files on the command line must be passed to the command using the --cfg option.

DIRAC_USE_JSON_ENCODE
Controls the transition to JSON serialization. See the information in :ref:`jsonSerialization` page (default=Yes since 8.1)
Controls the transition to JSON serialization (default=Yes since 9.0)

DIRAC_ROOT_PATH
If set, overwrites the value of DIRAC.rootPath.
Expand Down
8 changes: 0 additions & 8 deletions docs/source/AdministratorGuide/Systems/DataManagement/fts3.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,6 @@
FTS3 support in DIRAC
---------------------

.. versionadded:: v6r20

.. contents:: Table of contents
:depth: 2

Expand Down Expand Up @@ -148,10 +146,6 @@ The FTS3Operation goes to ``Processed`` when all the files are in a final state,
FTS3 Plugins
------------

.. versionadded:: v7r1p37
The ``FTS3Plugin`` option


The ``FTS3Plugin`` option allows one to specify a plugin to alter some default choices made by the FTS3 system. These choices concern:

* the list of third party protocols used
Expand All @@ -165,8 +159,6 @@ This can be useful if you want to implement a matrix-like selection of protocols
MultiHop support
----------------

.. versionadded:: v7r3p21

.. |trade| unicode:: U+2122

.. warning::
Expand Down
2 changes: 0 additions & 2 deletions docs/source/AdministratorGuide/Systems/DataManagement/s3.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,6 @@
S3 support in DIRAC
-------------------

.. versionadded:: v7r0p19

.. contents:: Table of contents
:depth: 2

Expand Down
8 changes: 1 addition & 7 deletions docs/source/AdministratorGuide/Systems/Transformation/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,10 +46,7 @@ Within the TS a user can (for example):

Disadvantages:

- For very large installations, the submission may be perceived as slow, since there is no use (not yet) of Parametric jobs.

.. versionadded:: v6r20p3
Bulk submission of jobs is working for the transformations, so job submission can be sped up considerably.
- For very large installations, the submission may be perceived as slow, since there is no use (not yet) of Parametric jobs. Bulk submission of jobs is working for the transformations, so job submission can be sped up considerably.

Several improvements have been made in the TS to handle scalability, and extensibility issues.
While the system structure remains intact, "tricks" like threading and caching have been extensively applied.
Expand Down Expand Up @@ -691,9 +688,6 @@ Multi VO Configuration
----------------------



.. versionadded:: v6r20p5

There are two possibilities to configure the agents of the transformation system for the use in a multi VO installation.

- Use the same WorkflowTaskAgent and RequestTaskAgents for multiple VOs, no
Expand Down
Loading
Loading