Automating VCF - Create Workload Domain

In this part of the series, we take a look at how to initiate the workload domain deployment in SDDC Manager.

VMware Cloud Builder APIs Used

  • POST /v1/domains
  • POST /v1/domains/validations
  • GET /v1/hosts
  • GET /v1/tasks/{id}

PowerVCF Cmdlets

  • New-VCFWorkloadDomain
  • Get-VCFHost
  • Get-VCFTask

PowerShell Scripts

Procedure

Step 1 – Download and populate the Planning and Preparation Workbook for your target platform.

Step 2 – To generate the JSON spec using inputs from the Planning and Preparation Workbook run the following command:

.\createWorkloadDomainSpec.ps1 E:\pnpWorkbook.xlsx E:\MyLab\sfo\sfo-workloadDomain.json -vCenterPassword VMw@re1! -nsxtPassword VMw@re1!VMw@re1!

The createWorkloadDomainSpec.ps1 script will open the supplied Planning and Preparation Workbook, read the ‘Workload Domain’ tab into a variable and then proceed to generate the JSON spec required by the Public API.

You will notice that we are passing in a couple of additional values relating to passwords for vCenter and NSX-T, this is because the Planning and Preparation Workbook does not store any passwords.

Step 3 – Authenticate to the SDDC Manager appliance by running the following command:

Connect-VCFManager -fqdn sfo-vcf01.sfo.rainpole.io -username administrator@vsphere.local -password VMw@re1!

Step 4 – Obtain details about the ESXi host from SDDC Manager by running the following command

$host01 = Get-VCFHost -Status UNASSIGNED_USEABLE | select fqdn,id | Where {$_.fqdn -eq “sfo01-w01-esx01.sfo.rainpole.io"}

In this step we use the Get-VCFHost cmdlet to retrieve into the variable $host01 details about the ESXi host stored in the SDDC Manager inventory with a status of UNASSIGNED_USEABLE, we only need the unique ID really but I’m using the Select command to limit the details to fqdn and id. We will use the variable in the next step.

Step – Update the HOST-1 value in the JSON spec with the unique ID of the first ESXi host by running the following command:

(Get-Content E:\MyLab\sfo\sfo-workloadDomain.json) | Foreach-Object {$_ -replace ‘HOST-1', $($host01.id)} | Set-Content E:\MyLab\sfo\sfo-workloadDomain.json

In this procedure we are performing a search and replace in the sfo-workloadDomain.json where we replace HOST-1 with the unique id of the ESXi host contained in the $host01.id element of the variable from step 4.

Step 6 – Repeat Step 4 and 5 for the remaining three ESXi hosts by running the following commands:

$host02 = Get-VCFHost -Status UNASSIGNED_USEABLE | select fqdn,id | Where {$_.fqdn -eq “sfo01-w01-esx02.sfo.rainpole.io"}

 

(Get-Content E:\MyLab\sfo\sfo-workloadDomain.json) | Foreach-Object {$_ -replace ‘HOST-2', $($host02.id)} | Set-Content E:\MyLab\sfo\sfo-workloadDomain.json

 

$host03 = Get-VCFHost -Status UNASSIGNED_USEABLE | select fqdn,id | Where {$_.fqdn -eq “sfo01-w01-esx03.sfo.rainpole.io"}

 

(Get-Content E:\MyLab\sfo\sfo-workloadDomain.json) | Foreach-Object {$_ -replace ‘HOST-3', $($host03.id)} | Set-Content E:\MyLab\sfo\sfo-workloadDomain.json

 

$host04 = Get-VCFHost -Status UNASSIGNED_USEABLE | select fqdn,id | Where {$_.fqdn -eq “sfo01-w01-esx04.sfo.rainpole.io"}

 

(Get-Content E:\MyLab\sfo\sfo-workloadDomain.json) | Foreach-Object {$_ -replace ‘HOST-4', $($host04.id)} | Set-Content E:\MyLab\sfo\sfo-workloadDomain.json

Step 7 – Start the workload domain deployment workflow by running the following command:

$workloadDeployment = New-VCFWorkloadDomain -json E:\MyLab\sfo\sfo-workloadDomain.json

Using the New-VCFWorkloadDomain cmdlet, we trigger the workload domain deployment workflow, here I’m capturing the output of the command into a variable to be used in the next step.

As part of the New-VCFWorkloadDomain cmdlet we also execute the validation API to check the JSON spec prior to actually triggering the workload domain deployment workflow, if an error exists the process will abort allowing you fix things up before trying again.

Step 8 – Poll the status of the workload domain deployment workflow, by running the following command:

Do { $status = Get-VCFTask -id $workloadDeployment.id } While ($status.status -eq “In Progress")

Here we are polling the status of the workflow, using the unique ID from the New-VCFWorkloadDomain cmdlet which we retrieve from the variable $workloadDeployment.id and pass to the Get-VCFTask cmdlet. We perform a Do / While loop where we are looking for status of “In Progress”, once the state changes from “In Progress” we break from the loop.

That completes the process of generating a workload domain JSON spec used by the public API and running the workload domain deployment workflow in SDDC Manager .

 

About the Author:
Gary Blake is a Staff II Solutions Architect at VMware, focusing on VMware Cloud Foundation and VMware Validated Designs and is a lead contributor for PowerVCF. You can find Gary blogging at https://my-cloudy-world.com/ or on social media @GaryJBlake.

This article has been re-posted with permission from the author, and was originally posted at https://my-cloudy-world.com/.

Filter Tags

Automation Cloud Foundation VCF Operational Guidance