VCF Networking (NSX) Home Page

Virtual Private Clouds (VPCs) in vCenter

As covered in the blog Self-service networking with Virtual Private Clouds, VCF 9.0 empowers vCenter Administrators to independently manage the application networks with Virtual Private Clouds (VPCs) directly from vCenter UI/API.

And that’s what this blog section focuses on:
How vCenter Administrators now manage the networks of their applications straight from their vCenter-VPC

At the deployment of new VCF Workload Domains, Network Connectivity is configured with IP Blocks for future VPCs.

Note: The Network Connectivity can be configured as Distributed (as detailed in the blog VPCs without NSX edge VMs) or as Centralized (as detailed in the blog Simple NSX edge VMs deployment for VPCs).

And so just after the VCF Workload Domains deployment, vCenter Administrators can create VPCs for each application and deploy their applications autonomously: compute + storage + now network.

An important point to note: vCenter Administrators do not select the IP subnets for their VPC-Public and VPC-Private-TGW networks. These subnets are allocated from IP Blocks predefined by the Network Administrator during VCF deployment. This ensures that the Network Administrator retains full control over data center IP addressing.

The only subnets managed by vCenter Administrators are those used in VPC-Private, as these IPs remain entirely within the VPC.

Demo : vCenter-VPC Creation

In the demo below, you will see a step-by-step creation of VPCs from vCenter UI (click-click-click) and vCenter-Automation (PowerCLI)


Annex

PowerShell script for vCenter-VPC creation

PowerShell script “VPC-Marketing.ps1”