WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / Automation / Automated Lab Deployment Script for vSphere with Tanzu using NSX Advanced Load Balancer (NSX ALB)

Automated Lab Deployment Script for vSphere with Tanzu using NSX Advanced Load Balancer (NSX ALB)

04.05.2021 by William Lam // 7 Comments

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.

More from my site

  • Automated enablement of vSphere with Tanzu using vSphere Zones in vSphere 8
  • Quick Tip - How to deploy NSX Advanced Load Balancer (NSX-ALB) with a single Service Engine
  • Disabling vSphere with Tanzu does not delete NSX Advanced Load Balancer (NSX ALB) Service Engine (SE) VMs
  • Automating HAProxy VM deployment with 3-NIC configuration using PowerCLI
  • Automating Workload Management on vSphere with Tanzu

Categories // Automation, Kubernetes, PowerCLI, VMware Tanzu, vSphere 7.0 Tags // NSX Advanced Load Balancer, PowerCLI, vSphere 7.0 Update 2, vSphere with Tanzu

Comments

  1. Steve Ballmer says

    04/05/2021 at 12:08 pm

    Great work William!

    Reply
  2. jk kim says

    04/11/2021 at 4:21 pm

    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?

    Reply
    • @vra4u @JoseCavalheri says

      06/04/2021 at 6:03 am

      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.

      Reply
    • Joseph Larkin says

      06/30/2021 at 8:34 am

      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)

      Reply
  3. Joseph Larkin says

    06/26/2021 at 6:24 pm

    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 ...

    Reply
  4. Gustavo Dorado says

    07/08/2023 at 2:43 am

    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 😀

    Reply
  5. Óscar P. says

    09/10/2023 at 12:51 am

    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.

    Reply

Thanks for the comment!Cancel reply

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

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC) across Private, Hybrid and Public Cloud

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • ESXi on Lenovo ThinkStation P3 Ultra 09/29/2023
  • Quick Tip - vSphere 7.0 Update 3o also supports disabling/enabling vSphere Cluster Services (vCLS) in vSphere UI 09/29/2023
  • Heads Up - New image identifier required by VM Service in vSphere 8.0 Update 2 09/27/2023
  • How to setup private GitLab on a Synology for Project Keswick? 09/26/2023
  • ESXi on SimplyNUC Moonstone 09/25/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023

 

Loading Comments...