lboka/document-database-service
1
0
Fork 0
forked from docs/document-database-service
Code Pull Requests Activity

Compare commits

merge into: lboka:main
Branches Tags
lboka:main
lboka:DDS-compatibility-fix
lboka:propose-dds_umn-1042
lboka:propose-dds_api-ref-1036
lboka:propose-dds_api-ref-1032
lboka:propose-dds_api-ref-1027
lboka:zuul-tox-update
lboka:update_config_pdf
lboka:propose-dds_umn-1004
lboka:propose-dds_api-ref-1003
lboka:propose-dds_api-ref-997
lboka:minify_sphinx_gitea
lboka:minify_sphinx_internal
lboka:propose-dds_api-ref-936
lboka:propose-dds_best-practice-920
lboka:confpy
lboka:propose-dds_best-practice-928
lboka:propose-dds_api-ref-858
lboka:propose-dds_umn-859
lboka:propose-dds_umn-834
lboka:propose-dds_api-ref-834
lboka:propose-dds_umn-833
lboka:propose-dds_api-ref-833
lboka:constraints
lboka:propose-dds_api-ref-698
lboka:propose-dds_umn-769
lboka:propose-dds_api-ref-769
lboka:propose-dds_umn-773
lboka:propose-dds_api-ref-773
lboka:service_based_view
lboka:propose-dds_umn-731
lboka:propose-dds_api-ref-502
...
pull from: lboka:propose-dds_umn-1042
Branches Tags
lboka:DDS-compatibility-fix
lboka:propose-dds_umn-1042
lboka:main
lboka:propose-dds_api-ref-1036
lboka:propose-dds_api-ref-1032
lboka:propose-dds_api-ref-1027
lboka:zuul-tox-update
lboka:update_config_pdf
lboka:propose-dds_umn-1004
lboka:propose-dds_api-ref-1003
lboka:propose-dds_api-ref-997
lboka:minify_sphinx_gitea
lboka:minify_sphinx_internal
lboka:propose-dds_api-ref-936
lboka:propose-dds_best-practice-920
lboka:confpy
lboka:propose-dds_best-practice-928
lboka:propose-dds_api-ref-858
lboka:propose-dds_umn-859
lboka:propose-dds_umn-834
lboka:propose-dds_api-ref-834
lboka:propose-dds_umn-833
lboka:propose-dds_api-ref-833
lboka:constraints
lboka:propose-dds_api-ref-698
lboka:propose-dds_umn-769
lboka:propose-dds_api-ref-769
lboka:propose-dds_umn-773
lboka:propose-dds_api-ref-773
lboka:service_based_view
lboka:propose-dds_umn-731
lboka:propose-dds_api-ref-502

2 Commits
main ... propose-dd

Author SHA1 Message Date
OpenTelekomCloud Proposal Bot
01c453454a Update content 2024-02-26 08:37:16 +00:00
OpenTelekomCloud Proposal Bot
a0e2a4c2ae Update content 2024-01-31 07:23:37 +00:00
10 changed files with 53 additions and 25 deletions
Show Stats Expand all files Collapse all files

BIN
umn/source/_static/images/en-us_image_0000001835388741.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 14 KiB

7
umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst
View File

@ -60,14 +60,15 @@ Procedure
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Disk Encryption | - **Disabled**: Disable the encryption function. | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. |
| | | | | |
| | **Key Name**: Select or create a private key, which is the tenant key. | | | **Key Name**: Select or create a private key, which is the tenant key. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. |
| | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

7
umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst
View File

@ -60,14 +60,15 @@ Procedure
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Disk Encryption | - **Disabled**: Disable the encryption function. | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. |
| | | | | |
| | **Key Name**: Select or create a private key, which is the tenant key. | | | **Key Name**: Select or create a private key, which is the tenant key. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. |
| | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

7
umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst
View File

@ -62,14 +62,15 @@ You can use your account to create up to 50 replica set instances. To create mor
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Disk Encryption | - **Disabled**: Disable the encryption function. | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. |
| | | | | |
| | **Key Name**: Select or create a private key, which is the tenant key. | | | **Key Name**: Select or create a private key, which is the tenant key. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. |
| | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

7
umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst
View File

@ -62,14 +62,15 @@ You can use your account to create up to 50 replica set instances. To create mor
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Disk Encryption | - **Disabled**: Disable the encryption function. | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. |
| | | | | |
| | **Key Name**: Select or create a private key, which is the tenant key. | | | **Key Name**: Select or create a private key, which is the tenant key. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. |
| | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

5
umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst
View File

@ -66,8 +66,9 @@ Procedure
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. |
| | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

5
umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst
View File

@ -66,8 +66,9 @@ Procedure
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. |
| | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/introduction/index.rst
View File

@ -15,6 +15,7 @@ Introduction
- :ref:`User Permissions <dds_01_0017>` - :ref:`User Permissions <dds_01_0017>`
- :ref:`Permissions Management <dds_01_0019>` - :ref:`Permissions Management <dds_01_0019>`
- :ref:`Related Services <dds_01_0016>` - :ref:`Related Services <dds_01_0016>`
- :ref:`Mapping Between DDS Versions and Community Versions <dds_01_0060>`
.. toctree:: .. toctree::
:maxdepth: 1 :maxdepth: 1
@ -30,3 +31,4 @@ Introduction
user_permissions user_permissions
permissions_management permissions_management
related_services related_services
mapping_between_dds_versions_and_community_versions

20
umn/source/introduction/mapping_between_dds_versions_and_community_versions.rst Normal file
View File

@ -0,0 +1,20 @@
:original_name: dds_01_0060.html
.. _dds_01_0060:
Mapping Between DDS Versions and Community Versions
===================================================
Document Database Service (DDS) is a cloud database service compatible with MongoDB. DDS major versions select community versions that have not reached EOL and have new major functions as candidate versions for compatibility. The DDS version does not correspond to the community version. To help you understand the mapping between DDS versions and community versions, DDS uses compatible community versions. For details, see :ref:`Figure 1 <dds_01_0060__fig12011574199>`.
.. _dds_01_0060__fig12011574199:
.. figure:: /_static/images/en-us_image_0000001835388741.png
:alt: **Figure 1** Mapping between DDS versions and community versions
**Figure 1** Mapping between DDS versions and community versions
- DDS 3.4 and 4.0 are developed based on the corresponding community versions. The implementation of the same interface is consistent with that in the community. Compared with a community version, DDS has higher security and more O&M functions. DDS can better meet commercial application requirements.
- After October 16, 2018, DDS 4.0 uses the community version 4.0.3 as the baseline version. New features are independently developed and evolved.
- DDS 4.2 and later versions use the community version 4.0.3 as the baseline version. New features are independently developed and evolved. The storage engine is switched to RocksDB to provide better user experience.
- DDS source code has been opened in the GitHub community. For details, see https://github.com/hwCloudDBSDDS/dds.

2
umn/source/introduction/what_is_dds.rst
View File

@ -5,7 +5,7 @@
What Is DDS? What Is DDS?
============ ============
Document Database Service (DDS) is a high availability DBaaS, which provides a secure, reliable and scalable solution, compatible with MongoDB. It provides functions such as one-click deployment, elastic capacity expansion, disaster recovery, backup, restoration, monitoring, and alarm reporting. Document Database Service (DDS) is a high availability DBaaS, which provides a secure, reliable and scalable solution, compatible with MongoDB community version 4.0.3 as baseline version.It provides functions such as one-click deployment, elastic capacity expansion, disaster recovery, backup, restoration, monitoring, and alarm reporting.
DDS has the following features: DDS has the following features: