docs: removed deprecated options

Author: fstagni

docs/source/AdministratorGuide/Configuration/ConfReference/Operations/Pilots/index.rst

@@ -9,9 +9,6 @@ Parameter           Description                                               De
 ==================  ========================================================  ===============================================================================================
 Version             What project version will be used                         Version with which the component that submits pilot jobs is installed
 ------------------  --------------------------------------------------------  -----------------------------------------------------------------------------------------------
-DIRACOS             If set, it will use the --dirac-os options to install     False
-                    DIRAC within the pilot
-------------------  --------------------------------------------------------  -----------------------------------------------------------------------------------------------
 Project             What installation project will be used when submitting    DIRAC
                     pilot jobs to the resources
 ------------------  --------------------------------------------------------  -----------------------------------------------------------------------------------------------

docs/source/AdministratorGuide/Configuration/ConfReference/Tips/Authorization/index.rst

@@ -13,8 +13,6 @@ are showed in the next table:
 +----------------------------+------------------------------------------------------------------+-------------+
 | *AlarmsManagement*         | Allow to set notifications and manage alarms                     |             |
 +----------------------------+------------------------------------------------------------------+-------------+
-| *BookkeepingManagement*    | Allow Bookkeeping Management                                     |             |
-+----------------------------+------------------------------------------------------------------+-------------+
 | *CSAdministrator*          | CS Administrator - possibility to edit the Configuration Service |             |
 +----------------------------+------------------------------------------------------------------+-------------+
 | *FileCatalogManagement*    | Allow FC Management                                              |             |
@@ -41,8 +39,6 @@ are showed in the next table:
 +----------------------------+------------------------------------------------------------------+-------------+
 | *ProxyManagement*          | Allow managing proxies                                           |             |
 +----------------------------+------------------------------------------------------------------+-------------+
-| *PPGAuthority*             | Allow production request approval on behalf of PPG               |             |
-+----------------------------+------------------------------------------------------------------+-------------+
 | *ServiceAdministrator*     | DIRAC Service Administrator                                      |             |
 +----------------------------+------------------------------------------------------------------+-------------+
 | *SiteManager*              | Site Manager                                                     |             |

docs/source/AdministratorGuide/ExternalsSupport/index.rst

@@ -4,14 +4,17 @@
 Supported environments and packages
 ===================================
 
-OS:
----
+OS
+--
 
-DIRAC *server* installation is supported for most x86_64 Linux installations using `DIRACOS2 <https://github.com/DIRACGrid/DIRACOS2/releases>`_. Other architectures and platforms may work as a server installation, however this is on a best effort basis and is not regularly tested.
-DIRACOS includes all dependencies except for glibc, including Python and Grid middleware.
+DIRAC needs `DIRACOS <https://github.com/DIRACGrid/DIRACOS2/releases>`_ for its dependencies. DIRACOS includes all dependencies (except for glibc), including Python and Grid middleware.
 
-MySQL versions:
----------------
+DIRAC *client* installation is supported for all x86_64 Linux installations using `DIRACOS <https://github.com/DIRACGrid/DIRACOS2/releases>`_. This includes installations made by the pilots.
+
+DIRAC *server* installation is supported for *most* x86_64 Linux installations using `DIRACOS <https://github.com/DIRACGrid/DIRACOS2/releases>`_. Other architectures and platforms may work as a server installation, however this is on a best effort basis and is not regularly tested.
+
+MySQL versions
+--------------
 
 MySQL is a hard dependency for all DIRAC servers installations. Supported versions:
 
@@ -36,8 +39,8 @@ generic connection details can be applied in CS location below (the shown values
    }
 
 
-ElasticSearch versions:
------------------------
+ElasticSearch versions
+----------------------
 
 ElasticSearch is an optional dependency for DIRAC servers installations. Supported versions:
 
@@ -48,15 +51,15 @@ ElasticSearch server is not shipped with DIRAC. You are responsible of its admin
 
 You can run your ES cluster without authentication, or using User name and password, or using certificates. You may add the following parameters:
 
-  - ``User`` (default:'')
-  - ``Password`` (default:'')
-  - ``Host`` (default:localhost)
-  - ``Port`` (default:9201)
-  - ``SSL`` (default:True)
-  - ``CRT`` (default:True)
-  - ``ca_certs`` (default:None)
-  - ``client_key`` (default:None)
-  - ``client_cert`` (default:None)
+  - ``User`` (default:``''``)
+  - ``Password`` (default:``''``)
+  - ``Host`` (default:``localhost``)
+  - ``Port`` (default:``9201``)
+  - ``SSL`` (default:``True``)
+  - ``CRT`` (default:``True``)
+  - ``ca_certs`` (default:``None``)
+  - ``client_key`` (default:``None``)
+  - ``client_cert`` (default:``None``)
 
 
 to the location::

docs/source/AdministratorGuide/Systems/Framework/ComponentMonitoring/index.rst

@@ -6,27 +6,27 @@
 Static Component Monitoring
 ===========================
 
-.. versionadded:: v6r13
+.. highlight:: none
 
-As of v6r13, DIRAC includes a Component Monitoring system that logs information about what components are being installed
+DIRAC includes a Component Monitoring system that logs information about what components are being installed
 and uninstalled on which machines, when and by whom. Running this service is mandatory!
 
 This information is accessible from both the system administration CLI and the Component History page in the Web Portal.
 
 
 Installation
-============
+------------
 
 The service constitutes of one database (InstalledComponentsDB) and one service (Framework/ComponentMonitoring).
 These service and DB may have been installed already when DIRAC was installed the first time.
 
-The script **dirac-populate-component-db** should then be used to populate the DB tables with the necessary information.
+The script ``dirac-populate-component-db`` should then be used to populate the DB tables with the necessary information.
 
 
 Interacting with the static component monitoring
-================================================
+------------------------------------------------
 
-Using the CLI (dirac-admin-sysadmin-cli), it is possible to check the information about installations
+Using the CLI (``dirac-admin-sysadmin-cli``), it is possible to check the information about installations
 by using the 'show installations' command. This command accepts the following parameters:
 
 - list: Changes the display mode of the results
@@ -46,17 +46,17 @@ The app allows to set a number of filters for the query. It is possible to filte
 
 - Name: Actual name which the component/s whose information should be retrieved was installed with
 - Host: Machine/s in which to look for installations
-- System: System/s to which the components should belong. e.g: Framework, Bookkeeping ...
-- Module: Module/s of the components. e.g: SystemAdministrator, BookkeepingManager, ...
+- System: System/s to which the components should belong. e.g: Framework, WorkloadManagement ...
+- Module: Module/s of the components. e.g: SystemAdministrator, JobManager, ...
 - Type: Service, agent, executor, ...
 - Date and time: It is possible to select a timespan during which the components should have been installed ( it is possible to fill just one of the two available fields )
 
 By pressing the 'Submit' button, a list with all the matching results will be shown ( or all the possible results if no filters were specified ).
 
 Dynamic Component Monitoring
-============================
+----------------------------
 
-It shows information about running DIRAC components such as CPU, Memory, Running threads etc. The information can be accessed from the 'dirac-admin-sysadmin-cli' using
+It shows information about running DIRAC components such as CPU, Memory, Running threads etc. The information can be accessed from the ``dirac-admin-sysadmin-cli`` using
 'show profile'. The following parameters can be used::
 
  - <system>: The name of the system for example: DataManagementSystem