Update tox.ini && conf.py file

Performed-by: gitea/infra/otc-metadata/tools/generate_doc_confpy.py

umn/source/getting_started/step_4_log_in_to_the_ddm_schema.rst

@@ -39,6 +39,8 @@ For details about method 2, see :ref:`Using the MySQL CLI to Log In to a Schema
 
 For details about method 3, see :ref:`Using a JDBC Driver to Log In to a Schema <ddm_02_0005__section1690417388176>`.
 
+For details about method 4, see :ref:`Logging In to a DDM Instance on the DDM Console <ddm_02_0005__section144072633313>`.
+
 .. note::
 
    #. For security purposes, select an ECS in the same VPC as your DDM instance.
@@ -181,3 +183,24 @@ Using a JDBC Driver to Log In to a Schema
       -  **loadBalancePingTimeout**: indicates the time in milliseconds that the connection will wait for a response to a ping operation when you set **loadBalanceValidateConnectionOnSwapServer** to **true**.
       -  **retriesAllDown**: indicates the maximum number of connection attempts before an exception is thrown when a valid host is searched. SQLException will be returned if the threshold of retries is reached with no valid connections obtained.
       -  **connectTimeout**: indicates the maximum amount of time in milliseconds that the JDBC driver is willing to wait to set up a socket connection. **0** indicates that the connection does not time out. This parameter is available to JDK-1.4 or later versions. The default value is **0**.
+
+.. _ddm_02_0005__section144072633313:
+
+Logging In to a DDM Instance on the DDM Console
+-----------------------------------------------
+
+#. Log in to the DDM console.
+
+#. In the navigation pane, choose **Instances**.
+
+#. In the instance list, locate the required instance and click **Log In** in the **Operation** column.
+
+   On the displayed page, enter the required username and password.
+
+#. On the displayed page, enter username and password of the DDM account.
+
+#. Click **Test Connection**.
+
+#. (Optional) Enable **Collect Metadata Periodically** and **Show Executed SQL Statements**.
+
+#. Ensure that all settings are correct and click **Log In**.

umn/source/service_overview/usage_constraints/data_nodes.rst

@@ -17,4 +17,4 @@ Constraints on data nodes are as follows:
       -  If you are using MySQL 8.0, select **Case insensitive** for **Table Name** when you create a MySQL instance.
 
 -  Modifying configurations of a data node may result in an exception in using your DDM instance. After the modification, click **Synchronize Data Node Information** on the **Data Nodes** page to synchronize changes from the data node to DDM.
--  DDM data nodes do not support GBK character sets.
+-  Character set GBK is not allowed for data nodes.

zuul.yaml

@@ -1,3 +1,4 @@
+---
 - project:
     merge-mode: squash-merge
     default-branch: main