Changes to mrs_umn from docs/doc-exports#861 (MRS UMN 20230907 version

1.Some c

Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: proposalbot <proposalbot@otc-service.com>
Co-committed-by: proposalbot <proposalbot@otc-service.com>

umn/source/configuring_a_cluster/installing_third-party_software_using_bootstrap_actions.rst

@@ -5,9 +5,7 @@
 Installing Third-Party Software Using Bootstrap Actions
 =======================================================
 
-This operation applies to MRS 3.\ *x* or earlier clusters.
+This operation applies to clusters earlier than MRS 3.x.
-
-In MRS 3.\ *x*, bootstrap actions cannot be added during cluster creation.
 
 Prerequisites
 -------------

umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24010_flume_certificate_file_is_invalid_or_damaged.rst

@@ -78,11 +78,19 @@ Procedure
 
 7. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
 
-   **sh geneJKS.sh -f** *sNetty12@* **-g** *cNetty12@*
+   **sh geneJKS.sh -f** *Custom certificate password of the Flume role on the server* **-g** *Custom certificate password of the Flume role on the client*
 
    -  If yes, go to :ref:`8 <alm-24010__li57811511185514>`.
    -  If no, go to :ref:`9 <alm-24010__li593632253716>`.
 
+      .. note::
+
+         The custom certificate passwords must meet the following complexity requirements:
+
+         -  Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
+         -  Contain 8 to 64 characters.
+         -  Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
+
 8. .. _alm-24010__li57811511185514:
 
    Check whether this alarm is generated again during periodic system check.

umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24011_flume_certificate_file_is_about_to_expire.rst

@@ -74,11 +74,19 @@ Procedure
 
    Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
 
-   **sh geneJKS.sh -f** *sNetty12@* **-g** *cNetty12@*
+   **sh geneJKS.sh -f** *Custom certificate password of the Flume role on the server* **-g** *Custom certificate password of the Flume role on the client*
 
    -  If yes, go to :ref:`9 <alm-24011__li127861713811>`.
    -  If no, go to :ref:`8 <alm-24011__li6673192244411>`.
 
+      .. note::
+
+         The custom certificate passwords must meet the following complexity requirements:
+
+         -  Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
+         -  Contain 8 to 64 characters.
+         -  Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
+
 8. .. _alm-24011__li6673192244411:
 
    Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`6 <alm-24011__li1778591515212>` to :ref:`7 <alm-24011__li1599711402218>`. Then, check whether the alarm is automatically cleared one hour later.

umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24012_flume_certificate_file_has_expired.rst

@@ -75,11 +75,19 @@ Procedure
 
    Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
 
-   **sh geneJKS.sh -f** *sNetty12@* **-g** *cNetty12@*
+   **sh geneJKS.sh -f** *Custom certificate password of the Flume role on the server* **-g** *Custom certificate password of the Flume role on the client*
 
    -  If yes, go to :ref:`8 <alm-24012__li1788491915716>`.
    -  If no, go to :ref:`7 <alm-24012__li172496117507>`.
 
+      .. note::
+
+         The custom certificate passwords must meet the following complexity requirements:
+
+         -  Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
+         -  Contain 8 to 64 characters.
+         -  Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
+
 7. .. _alm-24012__li172496117507:
 
    Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`5 <alm-24012__li161213411093>` to :ref:`6 <alm-24012__li084616591915>`. Then, check whether the alarm is automatically cleared one hour later.

umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24013_flume_monitorserver_certificate_file_is_invalid_or_damaged.rst

@@ -78,11 +78,19 @@ Procedure
 
 7. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
 
-   **sh geneJKS.sh -m** *sKitty12@* **-n** *cKitty12@*
+   **sh geneJKS.sh -m** *Custom password of the MonitorServer certificate on the server* **-n** *Custom password of the MonitorServer certificate on the client*
 
    -  If yes, go to :ref:`8 <alm-24013__li57811511185514>`.
    -  If no, go to :ref:`9 <alm-24013__li593632253716>`.
 
+      .. note::
+
+         The custom certificate passwords must meet the following complexity requirements:
+
+         -  Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
+         -  Contain 8 to 64 characters.
+         -  Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
+
 8. .. _alm-24013__li57811511185514:
 
    Check whether this alarm is generated again during periodic system check.

umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24014_flume_monitorserver_certificate_is_about_to_expire.rst

@@ -74,11 +74,19 @@ Procedure
 
    Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
 
-   **sh geneJKS.sh -m** *sKitty12@* **-n** *cKitty12@*
+   **sh geneJKS.sh -m** *Custom password of the MonitorServer certificate on the server* **-n** *Custom password of the MonitorServer certificate on the client*
 
    -  If yes, go to :ref:`9 <alm-24014__li127861713811>`.
    -  If no, go to :ref:`8 <alm-24014__li6673192244411>`.
 
+      .. note::
+
+         The custom certificate passwords must meet the following complexity requirements:
+
+         -  Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
+         -  Contain 8 to 64 characters.
+         -  Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
+
 8. .. _alm-24014__li6673192244411:
 
    Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`6 <alm-24014__li368813032118>` to :ref:`7 <alm-24014__li153512414216>`. Then, check whether the alarm is automatically cleared one hour later.

umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24015_flume_monitorserver_certificate_file_has_expired.rst

@@ -75,11 +75,19 @@ Procedure
 
    Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
 
-   **sh geneJKS.sh -m** *sKitty12@* **-n** *cKitty12@*
+   **sh geneJKS.sh -m** *Custom password of the MonitorServer certificate on the server* **-n** *Custom password of the MonitorServer certificate on the client*
 
    -  If yes, go to :ref:`8 <alm-24015__li1788491915716>`.
    -  If no, go to :ref:`7 <alm-24015__li172496117507>`.
 
+      .. note::
+
+         The custom certificate passwords must meet the following complexity requirements:
+
+         -  Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
+         -  Contain 8 to 64 characters.
+         -  Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
+
 7. .. _alm-24015__li172496117507:
 
    Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`5 <alm-24015__li160343112815>` to :ref:`6 <alm-24015__li68486146283>`. Then, check whether the alarm is automatically cleared one hour later.

umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/user_account_list.rst

@@ -50,6 +50,8 @@ System Users
 | Node OS user         | ommdba      | Random password       | User that creates the system database. This user is an OS user generated on the management node and does not require a unified password. This account cannot be used for remote login.                                                                                       | For details, see :ref:`Changing the Password for an OS User <admin_guide_000251>`. |
 +----------------------+-------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
 |                      | omm         | Bigdata123@           | Internal running user of the system. This user is an OS user generated on all nodes and does not require a unified password.                                                                                                                                                 |                                                                                    |
+|                      |             |                       |                                                                                                                                                                                                                                                                              |                                                                                    |
+|                      |             |                       | In MRS 3.2.0-LTS.2 or later, the password of user **omm** is randomly generated.                                                                                                                                                                                             |                                                                                    |
 +----------------------+-------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
 
 Internal System Users

umn/source/managing_clusters/bootstrap_actions/adding_a_bootstrap_action.rst

@@ -7,7 +7,7 @@ Adding a Bootstrap Action
 
 Add a bootstrap action.
 
-This operation applies to MRS 3.\ *x* or earlier clusters.
+This operation applies to clusters earlier than MRS 3.\ *x*.
 
 Procedure
 ---------