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

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2024-01-31 07:23:37 +00:00
parent bab39dfb01
commit a0e2a4c2ae
9 changed files with 82 additions and 24 deletions
Show Stats Download Patch File Download Diff File 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

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

@ -60,15 +60,21 @@ Procedure
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 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. |
| | |
| | .. 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. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
| | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | |
| | - 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. |
| | |
| | If both disk encryption and backup data encryption are enabled, data cannot be restored. |
| | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications

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

@ -60,15 +60,21 @@ Procedure
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 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. |
| | |
| | .. 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. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
| | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | |
| | - 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. |
| | |
| | If both disk encryption and backup data encryption are enabled, data cannot be restored. |
| | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications

16
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,15 +62,21 @@ You can use your account to create up to 50 replica set instances. To create mor
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 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. |
| | |
| | .. 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. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
| | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | |
| | - 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. |
| | |
| | If both disk encryption and backup data encryption are enabled, data cannot be restored. |
| | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications

16
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,15 +62,21 @@ You can use your account to create up to 50 replica set instances. To create mor
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 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. |
| | |
| | .. 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. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
| | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | |
| | - 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. |
| | |
| | If both disk encryption and backup data encryption are enabled, data cannot be restored. |
| | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications

10
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,14 @@ Procedure
| | |
| | .. 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. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | |
| | - 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. |
| | |
| | If both disk encryption and backup data encryption are enabled, data cannot be restored. |
| | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

10
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,14 @@ Procedure
| | |
| | .. 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. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. |
| | |
| | - 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. |
| | |
| | If both disk encryption and backup data encryption are enabled, data cannot be restored. |
| | |
| | - 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:`Permissions Management <dds_01_0019>`
- :ref:`Related Services <dds_01_0016>`
- :ref:`Mapping Between DDS Versions and Community Versions <dds_01_0060>`
.. toctree::
:maxdepth: 1
@ -30,3 +31,4 @@ Introduction
user_permissions
permissions_management
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.