[Feature]: Possibility to deploy version VCF 9.1.0.0 with the most current installable patches

[freddyblue]

Description

It takes much time to update from 9.1.0.0 to 9.1.0.0100, 9.1.0.0200 9.1.0.0300, etc. So I'd like to deploy 9.1.0.0 with the most current installable patches right away when setting up a new instance with new-holodeckinstance.

Use case / Motivation

saving time

Proposed solution

This is my workaround, I have tested successfully:
Prerequisite:
Offline Depot with version 9.1.0.0 and most current installable patches (e.g. 9.1.0.0100, 9.1.0.0300)

login to holo-router 9.1
cp -i /holodeck-runtime/templates/bom.json /holodeck-runtime/templates/bom.json.org

change to most current installable patch version for ESX and SDDC-Manager (VCF Installer)
vi /holodeck-runtime/templates/bom.json
"9.1.0.0" : {
"esx" : ["VMware-VMvisor-Installer-9.1.0.0100.25433460.x86_64.iso"],
"vcf-installer" : ["VCF-SDDC-Manager-Appliance-9.1.0.0300.25536191.ova"]

cp -i /root/.local/share/powershell/Modules/HoloDeck/Modules/PreCheck.psm1 /root/.local/share/powershell/Modules/HoloDeck/Modules/PreCheck.psm1.org
vi /root/.local/share/powershell/Modules/HoloDeck/Modules/PreCheck.psm1

elseif($Version -eq "9.1.0.0"){
    $requiredFilePatterns = @(
        @{Path = "/PROD/COMP/ESX_HOST/"; Pattern = "VMware-VMvisor-Installer-9.1.0.*.x86_64.iso"},
        @{Path = "/PROD/COMP/NSX_T_MANAGER/"; Pattern = "nsx-unified-appliance-9.1.0.0.*.ova"},
        @{Path = "/PROD/COMP/SDDC_MANAGER_VCF/Compatibility/"; Pattern = "VmwareCompatibilityData.json"},
        @{Path = "/PROD/COMP/SDDC_MANAGER_VCF/"; Pattern = "VCF-SDDC-Manager-Appliance-9.1.0.*.ova"},

cp -i /holodeck-runtime/templates/config.json /holodeck-runtime/templates/config.json.org
vi /holodeck-runtime/templates/config.json

"vcf-9-1": {
"management-domain-spec": {
"sddcId": "mgmt-a",
"vcfInstanceName": "instance-a",
"workflowType": "VCF",
"version": "",

"vcf-9-1": {
"management-domain-spec": {
"sddcId": "mgmt-b",
"vcfInstanceName": "instance-b",
"workflowType": "VCF",
"version": "",

cp -i /root/.local/share/powershell/Modules/HoloDeck/Modules/SddcMgmtDeployment.psm1 /root/.local/share/powershell/Modules/HoloDeck/Modules/SddcMgmtDeployment.psm1.org
vi /root/.local/share/powershell/Modules/HoloDeck/Modules/SddcMgmtDeployment.psm1

search for => Each component has versions[], we need to extract bundle info from the first/latest version
$latestVersion = $component.versions[0] => $latestVersion = $component.versions[-1]

Additional context

No response

[dhruv-tyagi-broadcom]

9.1.0.0100 is a patch version. It cannot be deployed as greenfield installation

[freddyblue]

sorry, but that is not true. 9.1.0.0100 is installable. We already have done an installation with this version, not for all components, but for most. vcf installer always uses the newest version you have downloaded if you don't set a fix version in the json input file. That is what holodeck is doing. Please can you check again. Thanks in advance

[dhruv-tyagi-broadcom]

Okay, I haven't tried it yet. But if it works, then you can try updating /holodeck-runtime/templates/bom.json with the VCF Installer and ESX file names. You will also have to update these 2 lines in the prechecks:

            @{Path = "/PROD/COMP/ESX_HOST/"; Pattern = "VMware-VMvisor-Installer-9.1.0.0.*.x86_64.iso"},

            @{Path = "/PROD/COMP/SDDC_MANAGER_VCF/"; Pattern = "VCF-SDDC-Manager-Appliance-9.1.0.0.*.ova"},

Change 9.1.0.0.* to 9.1.0.*

[freddyblue]

What script modifications are necessary so that in VCF Installer the 9.1.0.0100 Patch Binaries have a Download Status "Success". Right now they are "Not downloaded". If they are "Not downloaded" the deployment is not going to use the 9.1.0.0100 Patch Version for installation. In non Holodeck environments it works fine.

[alan-harrington]

This is working great, deployed 9.1.0.0300 right out of the gate. Thanks for the deep dive into figuring this out!