Update tox.ini && conf.py file

Reviewed-by: tischrei <tino.schreiber@t-systems.com>
Co-authored-by: Gode, Sebastian <sebastian.gode@t-systems.com>
Co-committed-by: Gode, Sebastian <sebastian.gode@t-systems.com>

doc/requirements.txt

@@ -8,3 +8,4 @@ reno>=3.1.0 # Apache-2.0
 otc-sphinx-directives>=0.1.0
 sphinx-minify>=0.0.1 # Apache-2.0
 git+https://gitea.eco.tsi-dev.otc-service.com/infra/otc-metadata.git#egg=otc_metadata
+setuptools

tox.ini

@@ -43,15 +43,19 @@ commands =
   {[testenv:json-umn]commands}
 
 [testenv:docs-pdf]
-deps = {[testenv:docs]deps}
+deps =
+  {[testenv:docs]deps}
+  {[testenv:bindeps]deps}
 allowlist_externals =
   rm
   mkdir
+  wget
   make
   bash
   cp
 commands =
   mkdir -p doc/build/pdf
+  {[testenv:bindeps]commands}
   {[testenv:api-ref-pdf-docs]commands}
   {[testenv:umn-pdf-docs]commands}
 
@@ -149,6 +153,21 @@ commands =
 
 
 
+[testenv:bindeps]
+deps =
+    bindep
+allowlist_externals =
+    wget
+    rm
+    bash
+commands =
+    rm -rf {toxinidir}/bindep.txt
+    rm -rf {toxinidir}/packages.txt
+    wget -O {toxinidir}/bindep.txt https://raw.githubusercontent.com/opentelekomcloud/otcdocstheme/main/bindep.txt
+    bash -c "bindep test -b -f {toxinidir}/bindep.txt > {toxinidir}/packages.txt || true"
+    bash -c 'if [ -s {toxinidir}/packages.txt ]; then if command -v apt &>/dev/null; then apt update && xargs apt install --no-install-recommends -y < {toxinidir}/packages.txt; fi; fi'
+    bash -c 'if [ -s {toxinidir}/packages.txt ]; then if command -v dnf &>/dev/null; then dnf install -y $(cat {toxinidir}/packages.txt); fi; fi'
+
 [doc8]
 ignore = D001
 extensions = .rst, .yaml

umn/source/getting_started/step_4_log_in_to_the_ddm_schema.rst

@@ -39,8 +39,6 @@ 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.
@@ -183,24 +181,3 @@ 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.
--  Character set GBK is not allowed for data nodes.
+-  DDM data nodes do not support GBK character sets.