Skip to content

Commit 1bc175b

Browse files
GaOrtigaGabriel
andauthored
Add section about Domain VPCs (#410)
Co-authored-by: Gabriel <[email protected]>
1 parent 7f43c64 commit 1bc175b

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

source/adminguide/networking/virtual_private_cloud_config.rst

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1444,6 +1444,26 @@ Editing, Restarting, and Removing a Virtual Private Cloud
14441444
|restart-vpc.png|
14451445

14461446

1447+
Working with Domain VPCs
1448+
~~~~~~~~~~~~~~~~~~~~~~~~
1449+
1450+
The functionality of domain VPCs allows operators to aggregate multiple
1451+
Network Tiers from distinct users on the same VPC, reducing the number of virtual
1452+
routers necessary in the environment, and consequently, decreasing the
1453+
amount of public IP addresses consumed. All Network Tiers added to the VPC share
1454+
the same VR, but each one has their own broadcast domain and features
1455+
implemented by the VPC, such as DHCP, NAT, and so on.
1456+
1457+
In order to utilize this functionality, a new Network Tier must be included to an
1458+
existing VPC by inputing the respective data for the account and the VPC
1459+
on the **'createNetwork'** API. It is important to note that, in order
1460+
for a Network Tier of a different account to be created on the VPC, the account
1461+
that creates the Network Tier must have access to both the account that owns the
1462+
VPC and the account that owns the Network Tier. The owner of the VPC must also
1463+
have access to the account that owns the Network Tier, however, the opposite
1464+
is not required.
1465+
1466+
14471467
.. |add-vpc.png| image:: /_static/images/add-vpc.png
14481468
:alt: adding a vpc.
14491469
.. |add-tier.png| image:: /_static/images/add-tier.png

0 commit comments

Comments
 (0)