Automation

Phase: Post-Deployment (Day 2+)

This guide captures the lab-specific workflow for VCF Automation (auto.pgnet.io) after bring-up: initial access, identity, certificates, and verification.

9.1 Initial Setup Automation

1. Quick start

   

   

   Organization
   
   pgnet-it with a default project will be created
   
   Infrastructure Capacity
   
   pgnet-brisbane will be created
   
   pgnet-brisbane will be assigned to pgnet-it
   
   pg-storagepol-bulk, pg-storagepol-vmfs, pg-storeagepol-vsan will be assigned to pgnet-it
   
   Networking
   
   External connectivity will be established using the networking parameters from the workload domain setup
   
   Users assigned to this organization can get started right away

1. Target in this lab

• Appliance FQDN: auto.pgnet.io
• Notes: Deployed during bring-up; Day 2 tasks are identity, certificates, and validation.

2. Prerequisites

• Part 4 completed (Identity Broker + CA integration/cert workflows where applicable).
• DNS/NTP stable across the environment.

3. SSO enablement (recommended)

Enable Single Sign-On for the Automation appliance using the same embedded Identity Broker domain used for Operations.

• In the VCF UI: under VCF Management, select the automation appliance and enable Single Sign-On.
• Select the existing identity broker domain used for ops.pgnet.io.

4. Certificates (recommended)

If you are standardizing certificates across the stack, generate/import certificates for Automation using your CA.

• Use the same CA integration approach as Part 4.
• Verify browser trust from an admin workstation (import the root/intermediate CA if needed).

5. Basic validation

• Confirm UI access and login works (local admin and/or SSO).
• Confirm Automation can reach vCenter and NSX endpoints in the management domain.

6. Notes / TODO

• Add the exact tenancy/VPC provisioning steps once finalized for this lab.