sgode/virtual-private-cloud
1
0
Fork 0
forked from docs/virtual-private-cloud
Code Pull Requests Activity

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2023-04-24 08:56:52 +00:00 committed by Hajba, László Antal
parent a2d343d0cf
commit 85a0439792
73 changed files with 85 additions and 89 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
umn/source/change_history.rst
View File

@ -8,6 +8,13 @@ Change History
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Released On | Description | | Released On | Description |
+===================================+====================================================================================================================================================================================================================================================================================================================================+ +===================================+====================================================================================================================================================================================================================================================================================================================================+
| 2023-04-20 | This release incorporates the following changes: |
| | |
| | Updated the following content: |
| | |
| | - Added description that BMS user-defined network is available only in eu-de. |
| | - Added the step for viewing NIC details to :ref:`Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) <vpc_vip_0008>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-02-15 | This release incorporates the following changes: | | 2023-02-15 | This release incorporates the following changes: |
| | | | | |
| | Updated the following content: | | | Updated the following content: |
@ -283,7 +290,7 @@ Change History
| | | | | |
| | Deleted the following content: | | | Deleted the following content: |
| | | | | |
| | - Deleted "What Is a Security Group?", "Which Protocols Does a Security Group Support?", "What Are the Functions of the Default Security Group Rule?", and "How Can I Configure Security Group Rules?" in :ref:`FAQs <vpc_faq_0000>`. | | | - Deleted "What Is a Security Group?", "Which Protocols Does a Security Group Support?", "What Are the Functions of the Default Security Group Rule?", and "How Can I Configure Security Group Rules?" in :ref:`FAQ <vpc_faq_0000>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2019-04-17 | Accepted in OTC-4.0/Agile-04.2019. | | 2019-04-17 | Accepted in OTC-4.0/Agile-04.2019. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@ -307,7 +314,7 @@ Change History
| | Deleted the following content: | | | Deleted the following content: |
| | | | | |
| | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts <vpc_concepts_0001>`. | | | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts <vpc_concepts_0001>`. |
| | - Deleted the FAQs related to VPN in :ref:`FAQs <vpc_faq_0000>`. | | | - Deleted the FAQs related to VPN in :ref:`FAQ <vpc_faq_0000>`. |
| | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started <vpc_qs_0000>`. | | | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started <vpc_qs_0000>`. |
| | | | | |
| | Modified the following content: | | | Modified the following content: |
@ -345,7 +352,7 @@ Change History
| | Deleted the following content: | | | Deleted the following content: |
| | | | | |
| | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts <vpc_concepts_0001>`. | | | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts <vpc_concepts_0001>`. |
| | - Deleted the FAQs related to VPN in :ref:`FAQs <vpc_faq_0000>`. | | | - Deleted the FAQs related to VPN in :ref:`FAQ <vpc_faq_0000>`. |
| | | | | |
| | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started <vpc_qs_0000>`. | | | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started <vpc_qs_0000>`. |
| | | | | |

5
umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst
View File

@ -14,12 +14,13 @@ You can assign an EIP and bind it to an ECS so that the ECS can access the Inter
Note the following when you use EIPs of the Dedicated Load Balancer (**5_gray**) type: Note the following when you use EIPs of the Dedicated Load Balancer (**5_gray**) type:
- In **eu-de**, EIPs of the Dedicated Load Balancer (5_gray) type cannot be created anymore. - In **eu-de**, EIPs of the Dedicated Load Balancer (**5_gray**) type cannot be assigned anymore. You can assign EIPs of the BGP (**5_bgp**) type.
- Existing EIPs of the Dedicated Load Balancer (**5_gray**) type can be bound to dedicated or shared load balancers. - Existing EIPs of the Dedicated Load Balancer (**5_gray**) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers. - The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see "Binding an EIP" and "Unbinding an EIP" in "API V3" section in the *Elastic IP API Reference*. - You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see `Binding an EIP <https://docs.otc.t-systems.com/elastic-ip/api-ref/api_v3/elastic_ip/binding_an_eip.html>`__ and `Unbinding an EIP <https://docs.otc.t-systems.com/elastic-ip/api-ref/api_v3/elastic_ip/unbinding_an_eip.html>`__.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs. - EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- Do not add EIPs of the dedicated load balancer type (**5_gray**) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect. - Do not add EIPs of the dedicated load balancer type (**5_gray**) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.

5
umn/source/elastic_ip/unbinding_an_eip_from_an_ecs_and_releasing_the_eip.rst
View File

@ -13,12 +13,13 @@ If you no longer need an EIP, unbind it from the ECS and release the EIP to avoi
Notes and Constraints Notes and Constraints
--------------------- ---------------------
- In **eu-de**, EIPs of the Dedicated Load Balancer (5_gray) type cannot be created anymore. - In **eu-de**, EIPs of the Dedicated Load Balancer (**5_gray**) type cannot be assigned anymore. You can assign EIPs of the BGP (**5_bgp**) type.
- Existing EIPs of the Dedicated Load Balancer (**5_gray**) type can be bound to dedicated or shared load balancers. - Existing EIPs of the Dedicated Load Balancer (**5_gray**) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers. - The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see "Binding an EIP" and "Unbinding an EIP" in "API V3" section in the *Elastic IP API Reference*. - You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see `Binding an EIP <https://docs.otc.t-systems.com/elastic-ip/api-ref/api_v3/elastic_ip/binding_an_eip.html>`__ and `Unbinding an EIP <https://docs.otc.t-systems.com/elastic-ip/api-ref/api_v3/elastic_ip/unbinding_an_eip.html>`__.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs. - EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- EIP assigned together with your load balancers will also be displayed in the EIP list. - EIP assigned together with your load balancers will also be displayed in the EIP list.
- You can only release EIPs that are not bound to any resources. - You can only release EIPs that are not bound to any resources.

0
umn/source/faqs/bandwidth/index.rst → umn/source/faq/bandwidth/index.rst
View File

0
umn/source/faqs/bandwidth/what_are_the_differences_between_a_dedicated_bandwidth_and_a_shared_bandwidth_can_a_dedicated_bandwidth_be_changed_to_a_shared_bandwidth_or_the_other_way_around.rst → umn/source/faq/bandwidth/what_are_the_differences_between_a_dedicated_bandwidth_and_a_shared_bandwidth_can_a_dedicated_bandwidth_be_changed_to_a_shared_bandwidth_or_the_other_way_around.rst
View File

0
umn/source/faqs/bandwidth/what_bandwidth_types_are_available.rst → umn/source/faq/bandwidth/what_bandwidth_types_are_available.rst
View File

0
umn/source/faqs/bandwidth/what_is_the_bandwidth_size_range.rst → umn/source/faq/bandwidth/what_is_the_bandwidth_size_range.rst
View File

0
umn/source/faqs/connectivity/does_a_vpn_allow_communication_between_two_vpcs.rst → umn/source/faq/connectivity/does_a_vpn_allow_communication_between_two_vpcs.rst
View File

0
umn/source/faqs/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst → umn/source/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst
View File

0
umn/source/faqs/connectivity/index.rst → umn/source/faq/connectivity/index.rst
View File

0
umn/source/faqs/connectivity/what_are_the_priorities_of_the_custom_route_and_eip_if_both_are_configured_for_an_ecs_to_enable_the_ecs_to_access_the_internet.rst → umn/source/faq/connectivity/what_are_the_priorities_of_the_custom_route_and_eip_if_both_are_configured_for_an_ecs_to_enable_the_ecs_to_access_the_internet.rst
View File

0
umn/source/faqs/connectivity/what_are_the_priorities_of_the_shared_snat_and_custom_route_if_both_are_configured_for_an_ecs_to_enable_the_ecs_to_access_the_internet.rst → umn/source/faq/connectivity/what_are_the_priorities_of_the_shared_snat_and_custom_route_if_both_are_configured_for_an_ecs_to_enable_the_ecs_to_access_the_internet.rst
View File

0
umn/source/faqs/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst → umn/source/faq/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst
View File

0
umn/source/faqs/eips/can_i_bind_an_eip_to_a_cloud_resource_in_another_region.rst → umn/source/faq/eips/can_i_bind_an_eip_to_a_cloud_resource_in_another_region.rst
View File

0
umn/source/faqs/eips/can_i_bind_an_eip_to_multiple_ecss.rst → umn/source/faq/eips/can_i_bind_an_eip_to_multiple_ecss.rst
View File

0
umn/source/faqs/eips/can_i_change_the_region_of_my_eip.rst → umn/source/faq/eips/can_i_change_the_region_of_my_eip.rst
View File

0
umn/source/faqs/eips/how_do_i_access_an_ecs_with_an_eip_bound_from_the_internet.rst → umn/source/faq/eips/how_do_i_access_an_ecs_with_an_eip_bound_from_the_internet.rst
View File

0
umn/source/faqs/eips/index.rst → umn/source/faq/eips/index.rst
View File

0
umn/source/faqs/eips/what_is_an_eip.rst → umn/source/faq/eips/what_is_an_eip.rst
View File

0
umn/source/faqs/general_questions/index.rst → umn/source/faq/general_questions/index.rst
View File

0
umn/source/faqs/general_questions/what_is_a_quota.rst → umn/source/faq/general_questions/what_is_a_quota.rst
View File

4
umn/source/faqs/index.rst → umn/source/faq/index.rst
View File

@ -2,8 +2,8 @@
.. _vpc_faq_0000: .. _vpc_faq_0000:
FAQs FAQ
==== ===
- :ref:`General Questions <faq_common>` - :ref:`General Questions <faq_common>`
- :ref:`VPCs and Subnets <faq_vpc>` - :ref:`VPCs and Subnets <faq_vpc>`

0
umn/source/faqs/routing/are_there_any_restrictions_on_using_a_route_table.rst → umn/source/faq/routing/are_there_any_restrictions_on_using_a_route_table.rst
View File

0
umn/source/faqs/routing/are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc.rst → umn/source/faq/routing/are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc.rst
View File

0
umn/source/faqs/routing/do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc.rst → umn/source/faq/routing/do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc.rst
View File

0
umn/source/faqs/routing/how_many_routes_can_a_route_table_contain.rst → umn/source/faq/routing/how_many_routes_can_a_route_table_contain.rst
View File

0
umn/source/faqs/routing/index.rst → umn/source/faq/routing/index.rst
View File

0
umn/source/faqs/security/can_i_change_the_security_group_of_an_ecs.rst → umn/source/faq/security/can_i_change_the_security_group_of_an_ecs.rst
View File

0
umn/source/faqs/security/does_a_security_group_rule_or_a_firewall_rule_immediately_take_effect_for_existing_connections_after_it_is_modified.rst → umn/source/faq/security/does_a_security_group_rule_or_a_firewall_rule_immediately_take_effect_for_existing_connections_after_it_is_modified.rst
View File

0
umn/source/faqs/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst → umn/source/faq/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst
View File

0
umn/source/faqs/security/how_many_firewalls_can_i_create.rst → umn/source/faq/security/how_many_firewalls_can_i_create.rst
View File

0
umn/source/faqs/security/how_many_security_groups_can_i_create.rst → umn/source/faq/security/how_many_security_groups_can_i_create.rst
View File

0
umn/source/faqs/security/index.rst → umn/source/faq/security/index.rst
View File

0
umn/source/faqs/security/which_security_group_rule_has_priority_when_multiple_security_group_rules_conflict.rst → umn/source/faq/security/which_security_group_rule_has_priority_when_multiple_security_group_rules_conflict.rst
View File

0
umn/source/faqs/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst → umn/source/faq/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst
View File

0
umn/source/faqs/vpc_peering_connections/how_many_vpc_peering_connections_can_i_create_in_an_account.rst → umn/source/faq/vpc_peering_connections/how_many_vpc_peering_connections_can_i_create_in_an_account.rst
View File

0
umn/source/faqs/vpc_peering_connections/index.rst → umn/source/faq/vpc_peering_connections/index.rst
View File

0
umn/source/faqs/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst → umn/source/faq/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst
View File

0
umn/source/faqs/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst → umn/source/faq/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst
View File

0
umn/source/faqs/vpcs_and_subnets/how_many_subnets_can_i_create.rst → umn/source/faq/vpcs_and_subnets/how_many_subnets_can_i_create.rst
View File

0
umn/source/faqs/vpcs_and_subnets/index.rst → umn/source/faq/vpcs_and_subnets/index.rst
View File

0
umn/source/faqs/vpcs_and_subnets/what_are_the_differences_between_the_network_id_and_subnet_id_of_a_subnet.rst → umn/source/faq/vpcs_and_subnets/what_are_the_differences_between_the_network_id_and_subnet_id_of_a_subnet.rst
View File

0
umn/source/faqs/vpcs_and_subnets/what_is_virtual_private_cloud.rst → umn/source/faq/vpcs_and_subnets/what_is_virtual_private_cloud.rst
View File

0
umn/source/faqs/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst → umn/source/faq/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst
View File

0
umn/source/faqs/vpcs_and_subnets/which_cidr_blocks_are_available_for_the_vpc_service.rst → umn/source/faq/vpcs_and_subnets/which_cidr_blocks_are_available_for_the_vpc_service.rst
View File

0
umn/source/faqs/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst → umn/source/faq/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst
View File

5
umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_3_assign_an_eip_and_bind_it_to_an_ecs.rst
View File

@ -14,12 +14,13 @@ You can assign an EIP and bind it to an ECS so that the ECS can access the Inter
Note the following when you use EIPs of the Dedicated Load Balancer (**5_gray**) type: Note the following when you use EIPs of the Dedicated Load Balancer (**5_gray**) type:
- In **eu-de**, EIPs of the Dedicated Load Balancer (5_gray) type cannot be created anymore. - In **eu-de**, EIPs of the Dedicated Load Balancer (**5_gray**) type cannot be assigned anymore. You can assign EIPs of the BGP (**5_bgp**) type.
- Existing EIPs of the Dedicated Load Balancer (**5_gray**) type can be bound to dedicated or shared load balancers. - Existing EIPs of the Dedicated Load Balancer (**5_gray**) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers. - The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see "Binding an EIP" and "Unbinding an EIP" in "API V3" section in the *Elastic IP API Reference*. - You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see `Binding an EIP <https://docs.otc.t-systems.com/elastic-ip/api-ref/api_v3/elastic_ip/binding_an_eip.html>`__ and `Unbinding an EIP <https://docs.otc.t-systems.com/elastic-ip/api-ref/api_v3/elastic_ip/unbinding_an_eip.html>`__.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs. - EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- Do not add EIPs of the dedicated load balancer type (**5_gray**) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect. - Do not add EIPs of the dedicated load balancer type (**5_gray**) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.

2
umn/source/index.rst
View File

@ -18,6 +18,6 @@ Virtual Private Cloud - User Guide
virtual_ip_address/index virtual_ip_address/index
monitoring/index monitoring/index
permissions_management/index permissions_management/index
faqs/index faq/index
change_history change_history
glossary glossary

2
umn/source/route_tables/configuring_an_snat_server.rst
View File

@ -34,7 +34,7 @@ Procedure
#. In the displayed area showing the NIC IP address details, disable **Source/Destination Check**. #. In the displayed area showing the NIC IP address details, disable **Source/Destination Check**.
By default, the source/destination check is enabled. When this check is enabled, the system checks whether source IP addresses contained in the packets sent by ECSs are correct. If the IP addresses are incorrect, the system does not allow the ECSs to send the packets. This mechanism prevents packet spoofing, thereby improving system security. If the SNAT function is used, the SNAT server needs to forward packets. This mechanism prevents the packet sender from receiving returned packets. Therefore, you need to disable the source/destination check for SNAT servers. This prevents packet spoofing and improves system security. If SNAT is used, the SNAT server needs to forward packets. This mechanism prevents the packet sender from receiving returned packets. To change this behavior, you can disable the source/destination check for SNAT servers.
#. Bind an EIP. #. Bind an EIP.

4
umn/source/route_tables/deleting_a_route_table.rst
View File

@ -15,9 +15,9 @@ Notes and Constraints
- The default route table cannot be deleted. - The default route table cannot be deleted.
- A custom route table cannot be deleted if it is associated with a subnet. - A custom route table with a subnet associated cannot be deleted directly.
You associate the subnet with another route table by referring to :ref:`Changing the Route Table Associated with a Subnet <vpc_route01_0008>` and then delete the route table. If you want to delete such a route table, you can associate the subnet with another route table first by referring to :ref:`Changing the Route Table Associated with a Subnet <vpc_route01_0008>`.
Procedure Procedure
--------- ---------

Some files were not shown because too many files have changed in this diff Show More