Description
It takes much time to update from 9.1.0.0 to 9.1.0.0100. So I'd like to deploy 9.1.0.0100 right away when setting up a new instance with new-holodeckinstance.
Use case / Motivation
saving time
Proposed solution
I thought about the following workaround I have not tested yet, but perhaps someone can check in theory if it would work. The alternative is to wait until next holodeck version.
Prerequisite is an offline depot with all installable 9.1.0.0100 files; according to William Lam VCF Installer uses always the newest version if there is no explicit version in the input json-file. But holodeck sets the version to 9.1.0.0.
- rename VMware-VMvisor-Installer-9.1.0.0100.25433460.x86_64.iso to VMware-VMvisor-Installer-9.1.0.0.25370933.x86_64.iso
- rename VCF-SDDC-Manager-Appliance-9.1.0.0100.25428926.ova to VCF-SDDC-Manager-Appliance-9.1.0.0.25371088.ova
- copy both renamed files to holorouter /holodeck-runtime/bin/9.1.0.0
- in /holodeck-runtime/templates/config.json in section vcf-9-1 for instance-a and instance-b change "version":9.1.0.0" to "version":"",
- start New-HoloDeckInstance
Additional context
No response
Description
It takes much time to update from 9.1.0.0 to 9.1.0.0100. So I'd like to deploy 9.1.0.0100 right away when setting up a new instance with new-holodeckinstance.
Use case / Motivation
saving time
Proposed solution
I thought about the following workaround I have not tested yet, but perhaps someone can check in theory if it would work. The alternative is to wait until next holodeck version.
Prerequisite is an offline depot with all installable 9.1.0.0100 files; according to William Lam VCF Installer uses always the newest version if there is no explicit version in the input json-file. But holodeck sets the version to 9.1.0.0.
Additional context
No response