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-1004
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

1 Commits
main ... propose-dd

Author SHA1 Message Date
OpenTelekomCloud Proposal Bot
7471987d01 Update content 2024-01-04 12:58:26 +00:00
6 changed files with 72 additions and 24 deletions
Show Stats Expand all files Collapse all files

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

@ -60,14 +60,22 @@ 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. Disk encryption will not encrypt backup data stored in OBS. |
| | - 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. |
| | |
| | If disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups <dds_03_0042>`. |
| | |
| | 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*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

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

@ -60,14 +60,22 @@ 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. Disk encryption will not encrypt backup data stored in OBS. |
| | - 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. |
| | |
| | If disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups <dds_03_0042>`. |
| | |
| | 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*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

14
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,22 @@ 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. Disk encryption will not encrypt backup data stored in OBS. |
| | - 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. |
| | |
| | If disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups <dds_03_0043>`. |
| | |
| | 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*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

14
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,22 @@ 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. Disk encryption will not encrypt backup data stored in OBS. |
| | - 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. |
| | |
| | If disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups <dds_03_0043>`. |
| | |
| | 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*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

12
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,16 @@ 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. Disk encryption will not encrypt backup data stored in OBS. |
| | - 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. |
| | |
| | If disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups <dds_03_0042>`. |
| | |
| | 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*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

12
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,16 @@ 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. Disk encryption will not encrypt backup data stored in OBS. |
| | - 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. |
| | |
| | If disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups <dds_03_0042>`. |
| | |
| | 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*. | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+