Configure VCF Automation in VCF 9: Initial Setup

HOMELAB JOURNAL

Configure VCF Automation in VCF 9: Initial Setup

Walk through VCF Automation initial configuration in VCF 9, including regions, organizations, IP spaces, provider gateways and regional networking.

Overview

This VCF Automation initial configuration guide starts after the appliance is deployed. I walk through creating a region, organization, IP space and provider gateway, then configuring regional networking in my VCF 9 lab; appliance deployment and SSO are separate tasks.

Prerequisite and workflow boundaries

StageReady condition
Appliance deploymentAutomation is installed, reachable by its FQDN and healthy; protected administrator credentials are available. This post does not deploy the appliance.
IdentityLocal system-organization administration works. External SSO and its component role mappings are a separate configuration; retain local recovery access.
VCF networkingThe intended vCenter, NSX, centralized gateway, Edge cluster and VPC networking are present and healthy.
SupervisorThe intended Supervisor and zone are available; VM classes and storage policies exist for the organization.
Address planningReserve nonoverlapping IP blocks and external reachability ranges; document provider-gateway routing, DNS/NTP and quotas before assignment.

Create the region first, then assign the organization and its compute/storage choices. Next define the IP space and provider gateway, synchronize the Edge inventory and create the organization’s regional networking. Do not assume that successful appliance deployment has completed these provider tasks.

  • Open the organization portal as its intended administrator and verify the assigned region, zone, VM classes and storage class.
  • Check that the selected provider gateway and IP space are the intended ones and that no address range overlaps another allocation.
  • Use a small authorized test deployment to validate provisioning and connectivity before broad access is granted. This post does not claim a newly executed workload test.

Before you begin

Up until now I have not even logged into the VCF automation gui, it has just been a VM that was deployed with VCF and running in the background. Prior to us setting this up, you will need to the following requirements to be met in order to complete this configuration.

  • VCF 9.0 environment deployed
  • NSX VPC configured with Centralized Transit Gateway
  • vSphere supervisor configured with VPC networking

Open VCF Automation

Open a web browser and navigate to the VCF automation gui.

The default organization name is system. Click Continue.

The default login is admin and the password you provide during deployment. Click Log In.

When logging in for the first time you will have two options to complete the configuration, I am clicking Get Started under Manual Setup.

Create a region

We now see that there are five steps to complete the setup process. Click Start next to create region.

Enter the required information for the region and click Submit

Create a Region associates the named region with an NSX Local Manager, a Supervisor, and the selected RAID1 storage class.

The region creation will begin and once it is ready click Infrastructure Overview.

The newly created region appears in the Regions table with status Ready.

Create an organization

Click Start next to create organization.

Enter an organization name and click Create and Continue.

Click the drop downs to select the region we just created and the supervisor for that region. Then click Add under Zones.

Click the drop down to select the zone assigned to that region and set any limits or reservations for compute. Click Save.

The zone quota example sets a 1 GHz CPU limit and 1 GB memory limit, with CPU and memory reservations set to zero.

Click Assign and Continue.

Click the checkboxes next to the VM classes you want to be available and the storage class for those VMs, click Assign and Continue.

Selected VM classes include best-effort-large with 4 CPUs and 16 GB RAM and best-effort-medium with 2 CPUs and 8 GB RAM; the RAID1 storage class has a 102400 MB limit.

At the Add First User section, this is where we will create and organization administrator, we can add additional users later. Enter in the required information and the role for this first user and click Add User and Finish.

Now that the organization is created click on Infrastructure Overview.

The Organizations table shows the new organization enabled and its creation status Ready.

Create an IP space

Click Start next to create IP space.

Provide a name for the IP space and click the drop down to select the region, click Next.

Provide an IP block space and external reachability space for this IP space, I am using the same external IPs as I did for the VPC connectivity. click Next to continue.

The Quota settings are optional, I am leaving the defaults and clicking Next.

Default IP quotas allow one single IP and one CIDR, with maximum subnet size set to /24 and unlimited options unchecked.

Click Create to finish.

After the IP space is created, click Infrastructure Overview

The new IP space appears with Normal status and its configured IP block and external reachability ranges.

Create a provider gateway

Click Start next to create provider gateway.

Provide a name and select the region in the dropdown for the provider gateway. Click Next.

Select the Tier0 gateway for that region and click Next.

Click the checkbox next to the IP space we created previously and click Next.

Click Create.

The provider gateway review links the gateway name and region to the selected Tier-0 gateway and the previously created IP space.

With the gateway created, click on Edge Clusters.

Click Sync if you don’t see the Edge Clusters listed below.

This is to ensure that our automation appliance has connected to NSX and pulled the information needed for region network settings. Now click on Infrastructure Overview.

The Edge Clusters table lists two healthy clusters, each with two nodes, alongside CPU and memory utilization.

Configure regional networking

Our last step is to click Start under region networking settings.

Click on the organization we created previously.

Click Configure under region network configurations.

The organization overview warns that networking is not configured and shows one region quota but zero of one region network configurations.

Click Edit under general as you notice there is a warning to setup a log name for the organization.

Provide a unique identifier for the organization, you are limited in length of the name so ensure it is easily recognizable. Click Save.

Click New under Regional Networking.

Select the region in the drop down and click Next.

Click the radio button next to the provider gateway we want to use and click Next.

Click Next at the edge cluster selection, if you have multiple clusters on a single Tier 0 gateway you can specify a specific edge cluster as well.

Regional networking is set to use the edge cluster of the Tier-0 provider gateway, with an alternative option to select a specific edge cluster.

Click Create to finish.

Once that has completed, click Infrastructure Overview.

The organization's regional networking entry lists its provider gateway and edge cluster with status Normal.

Open the organization portal

We have completed the setup process for VCF Automation with that organization.

We can now click on Organizations.

Click the organization we created.

Click Launch Organization Portal.

Our organization is up and running,

The organization portal opens with one project, no namespaces or policies, one user, and a prompt to connect an identity provider.

In future posts we will explore this organization setup further, in the meantime feel free to begin exploring.

Follow along with my VCF 9 Lab journey.

Related lab guides

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.