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 2024-04-18 08:59:09 +00:00
parent 5570dc109b
commit ee3f9ca081
6 changed files with 39 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
umn/source/_static/images/en-us_image_0000001818983182.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 8.5 KiB

BIN
umn/source/_static/images/en-us_image_0000001865663137.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 8.5 KiB

5
umn/source/change_history.rst
View File

@ -8,6 +8,11 @@ Change History
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Released On | Description |
+===================================+=================================================================================================================================================================================================================================================================================================================================================+
| 2024-04-16 | This release incorporates the following changes: |
| | |
| | - Modified the procedure for changing the CIDR block of a VPC in :ref:`Modifying a VPC <en-us_topic_0030969462>`. |
| | - Updated the Table 1 application scenarios of IPv4/IPv6 dual stack in :ref:`IPv4 and IPv6 Dual-Stack Network <vpc_0002>`. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2024-03-27 | This release incorporates the following changes: |
| | |
| | - Changed **VPCReadOnlyAccess** and **VPCFullAccess** into **VPC ReadOnlyAccess** and **VPC FullAccess**. |

4
umn/source/service_overview/basic_concepts/virtual_ip_address.rst
View File

@ -5,7 +5,7 @@
Virtual IP Address
==================
A virtual IP address can be shared among multiple ECSs. An ECS can have a private and a virtual IP address, which allows your users to access the ECS through either IP address. You can use either IP address to enable layer 2 and layer 3 communications in a VPC, access a different VPC using peering connections, and access cloud servers through EIPs, Direct Connect connections, and VPN connections.
You can use either IP address to enable layer 2 and layer 3 communications in a VPC, access a different VPC using peering connections, and access cloud servers through EIPs, Direct Connect connections, and VPN connections.
You can bind a virtual IP address to ECSs deployed in the active/standby pair, and then bind an EIP to the virtual IP address. Virtual IP addresses can work together with Keepalived to ensure high availability and disaster recovery. If the active ECS is faulty, the standby ECS automatically takes over services from the active one.
@ -53,4 +53,4 @@ Application Scenarios
- Using a VPN, Direct Connect, or VPC peering connection to access a virtual IP address
To ensure high availability and access to the Internet, use VPN for security and Direct Connect for stable connectivity. The VPC peering connection is needed so that the VPCs in the same region can communicate with each other.
To ensure high availability and access to the Internet, use a VPN for security and Direct Connect for a stable connection. A VPC peering connection is needed so that two VPCs in the same region can communicate with each other.

41
umn/source/vpc_and_subnet/ipv4_and_ipv6_dual-stack_network.rst
View File

@ -41,17 +41,36 @@ If your ECS supports IPv6, you can use the IPv4/IPv6 dual-stack network. :ref:`T
.. table:: **Table 1** Application scenarios of IPv4/IPv6 dual stack
+--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+
| Application Scenario | Description | Subnet | ECS |
+============================================+=========================================================================================================================================================+====================+===========================================================================+
| Private communication using IPv6 addresses | Your applications deployed on ECSs need to communicate with other systems (such as databases) through private networks using IPv6 addresses. | - IPv4 CIDR block | - Private IPv4 address: used for private communication |
| | | - IPv6 CIDR block | - IPv6 address: used for private communication. |
+--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+
| Public communication using IPv6 addresses | Your applications deployed on ECSs need to provide services accessible from the Internet using IPv6 addresses. | - IPv4 CIDR block | - Private IPv4 address + IPv4 EIP: used for public network communication |
| | | - IPv6 CIDR block | - IPv6 address + shared bandwidth: used for public network communication |
+--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+
| | Your applications deployed on ECSs need to both provide services accessible from the Internet and analyze the access request data using IPv6 addresses. | | |
+--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+
+----------------------------+-------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+
| Application Scenario | Description | Requirement | IPv4 or IPv6 Subnet | ECS |
+============================+=====================================================================================================================================+=============================================================+=====================+==================================================================================================================================================+
| Private IPv4 communication | Your applications on ECSs need to communicate with other systems (such as databases) through private networks using IPv4 addresses. | - IPv6 is not enabled for the VPC subnet. | IPv4 CIDR Block | **Private IPv4 address**: used for private IPv4 communication. |
| | | - No EIPs have been bound to the ECSs. | | |
+----------------------------+-------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+
| Public IPv4 communication | Your applications on ECSs need to communicate with other systems (such as databases) through public IPv4 addresses. | - IPv6 is not enabled for the VPC subnet. | IPv4 CIDR Block | - **Private IPv4 address**: used for private IPv4 communication. |
| | | - EIPs have been bound to the ECSs. | | - **Public IPv4 address**: used for public IPv4 communication. |
+----------------------------+-------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+
| Private IPv6 communication | Your applications on ECSs need to communicate with other systems (such as databases) through private IPv6 addresses. | - IPv6 has been enabled for the VPC subnet. | - IPv4 CIDR Block | - **Private IPv4 address + IPv4 EIP**: Bind an IPv4 EIP to the instance to allow public IPv4 communication. |
| | | - The network has been configured for the ECSs as follows: | - IPv6 CIDR block | - **Private IPv4 address**: Do not bind any IPv4 EIP to the instance and use only the private IPv4 address to allow private IPv4 communication. |
| | | | | - **IPv6 address**: Do not configure shared bandwidth for the IPv6 address to allow private IPv6 communication. |
| | | - **VPC and Subnet**: IPv6-enabled subnet and VPC. | | |
| | | - **Shared Bandwidth**: Selected **Do not configure**. | | |
+----------------------------+-------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+
| Public IPv6 communication | An IPv6 network is required for the ECS to access the IPv6 service on the Internet. | - IPv6 has been enabled for the VPC subnet. | - IPv4 CIDR Block | - **Private IPv4 address + IPv4 EIP**: Bind an IPv4 EIP to the instance to allow public IPv4 communication. |
| | | - The network has been configured for the ECSs as follows: | - IPv6 CIDR block | - **Private IPv4 address**: Do not bind any IPv4 EIP to the instance and use only the private IPv4 address to allow private IPv4 communication. |
| | | | | |
| | | - **VPC and Subnet**: IPv6-enabled subnet and VPC. | | - **IPv6 address + shared bandwidth**: Allow both private IPv6 communication and public IPv6 communication. |
| | | - **Shared Bandwidth**: Selected a shared bandwidth. | | |
+----------------------------+-------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Application scenarios of IPv6 EIPs
+-------------------------------------------+----------------------------------------------------------------------------------------------------------------+-----------------+--------------------------------------------------------------------------------------------------+
| Application Scenario | Description | Subnet | ECS |
+===========================================+================================================================================================================+=================+==================================================================================================+
| Public communication using IPv6 addresses | Your applications deployed on ECSs need to provide services accessible from the Internet using IPv6 addresses. | IPv4 CIDR block | - Private IPv4 address |
| | | | - IPv4 EIP (with IPv6 function enabled): used for public communication using IPv4 and IPv6 EIPs |
+-------------------------------------------+----------------------------------------------------------------------------------------------------------------+-----------------+--------------------------------------------------------------------------------------------------+
Basic Operations
----------------

24
umn/source/vpc_and_subnet/vpc/modifying_a_vpc.rst
View File

@ -62,29 +62,9 @@ Modifying the CIDR Block of a VPC
The **Edit CIDR Block** dialog box is displayed.
5. Modify the VPC CIDR block as prompted.
5. Click **Add Secondary IPv4 CIDR Block**.
.. important::
A VPC CIDR block must be from 10.0.0.0/8-24, 172.16.0.0/12-24, or 192.168.0.0/16-24.
- If a VPC has no subnets, you can change both its network address and subnet mask.
.. figure:: /_static/images/en-us_image_0000001818983182.png
:alt: **Figure 1** Modifying network address and subnet mask
**Figure 1** Modifying network address and subnet mask
- If a VPC has subnets, you only can change its subnet mask.
.. figure:: /_static/images/en-us_image_0000001865663137.png
:alt: **Figure 2** Modifying subnet mask
**Figure 2** Modifying subnet mask
6. Click **OK**.
6. Enter the secondary CIDR block and click **OK**.
.. |image1| image:: /_static/images/en-us_image_0000001818982734.png
.. |image2| image:: /_static/images/en-us_image_0000001818823402.png