After spending a few days playing with the NSX Advanced Load Balancer (NSX ALB) APIs, I am happy to share my latest automation lab deployment script for deploying vSphere with Tanzu using the new NSX ALB which was introduced with the latest vSphere 7.0 Update 2 release.
🙌 BOOM!!!
Fully Automated vSphere with @VMwareTanzu using the new @vmwarensx Advanced Load Balancer introduced in vSphere 7.0 Update 2 Lab Deployment in just 32 minutes! 🔥
Still need to clean up some things, but this beats clicking around the UI! My 🤲 thanks me pic.twitter.com/hN32Qk3oDc
— William Lam (@lamw) March 29, 2021
Lab Deployment Automation
You can find the new automation script along with all the details at the following Github Repo: https://github.com/lamw/vsphere-with-tanzu-nsx-advanced-lb-automated-lab-deployment#enable-workload-management
In my environment, it took about ~32 minutes for the deployment to finish, but YMMV based on the performance of your underlying hardware.
Workload Management Automation
In addition to the automated lab deployment script above, I have also updated my community VMware.WorkloadManagement module to add support for enabling Workload Management on a vSphere Cluster using NSX ALB. This is introduced as a new function creatively called New-WorkloadManagement3. You use the Get-Help cmdlet to get a list of supported arguments or you can take a look at this example.
Great work William!
Hi William,
I am getting an error when Creating subnet mapping for Service Engine Network and stopped with the below error messages.
Failed to create subnet mapping for DVPG-Supervisor-Management-Network
Write-Error: ({"detail": "Method 'PUT' not allowed."}.Exception.Message)
Any ideas what can cause this issue?
Same here... just trying today the automatic deployment and fails on same place.. Doing my investigation, but so far didn't find the reason yet.
I'm Having the same exact issue.
Failed to create subnet mapping for DVPG-Supervisor-Management-Network
Write-Error: ({"detail": "Method 'PUT' not allowed."}.Exception.Message)
I'm getting just this one error when deploying from your script.
"WARNING: Specifying a distributed port group name as network name is no longer supported. Use the -Portgroup parameter." I'm not great at powershell yet. Would you be able to Assist?
It Happens right after:
Adding vmnic2/vmnic3 for "Nested-Tanzu-Mgmt" and "Nested-Tanzu-Workload" to passthrough to Nested ESXi VMs ...
Hi Guys.
In the script, line 1012 (hardcoded username of nested vCenter), i change it for my "administrator@$VCSASSODomainName" and its working right now.
Sorry for delay 😀
Hi William.
I had to add the parameter "-Force" to the line 455 ($vm = Import-VApp -Source $NSXAdvLBOVA...) because I was not be able to deploy the NSX ALB version 30.1.1 with vCenter/ESXi 8.0.1a (I want to test new versions) because I was seeing always the error: "Import-VApp" The certificate used to sign the OVF package is not valid. (Untrusted).
I don't know if with your original versions was the same...
Regards.