From 01c453454a7248e81321ae1049bf347f451473d9 Mon Sep 17 00:00:00 2001 From: OpenTelekomCloud Proposal Bot Date: Mon, 26 Feb 2024 08:37:16 +0000 Subject: [PATCH] Update content --- .../creating_a_cluster_instance.rst | 5 ----- .../creating_a_cluster_instance.rst | 5 ----- .../creating_a_replica_set_instance.rst | 5 ----- .../creating_a_replica_set_instance.rst | 5 ----- .../creating_a_single_node_instance.rst | 5 ----- .../creating_a_single_node_instance.rst | 5 ----- umn/source/introduction/what_is_dds.rst | 2 +- 7 files changed, 1 insertion(+), 31 deletions(-) diff --git a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst index 3bdf5a0..7cc7615 100644 --- a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst +++ b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst @@ -67,13 +67,8 @@ Procedure | | .. note:: | | | | | | - 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*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst index 9743d00..50eddbe 100644 --- a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst +++ b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst @@ -67,13 +67,8 @@ Procedure | | .. note:: | | | | | | - 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*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst index e408149..76d73c6 100644 --- a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst +++ b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst @@ -69,13 +69,8 @@ You can use your account to create up to 50 replica set instances. To create mor | | .. note:: | | | | | | - 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*. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst index 3ac95ff..a9a7839 100644 --- a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst +++ b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst @@ -69,13 +69,8 @@ You can use your account to create up to 50 replica set instances. To create mor | | .. note:: | | | | | | - 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*. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst b/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst index 606c3a7..ef32743 100644 --- a/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst +++ b/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst @@ -67,13 +67,8 @@ Procedure | | .. note:: | | | | | | - 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*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst b/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst index 1d06c09..f7d1f64 100644 --- a/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst +++ b/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst @@ -67,13 +67,8 @@ Procedure | | .. note:: | | | | | | - 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*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/introduction/what_is_dds.rst b/umn/source/introduction/what_is_dds.rst index b28a644..1d7ec49 100644 --- a/umn/source/introduction/what_is_dds.rst +++ b/umn/source/introduction/what_is_dds.rst @@ -5,7 +5,7 @@ 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: