Skip to content

[Feature]: Possibility to deploy version VCF 9.1 GA EP01 (9.1.0.0100) instead of 9.1.0.0 #141

Description

@freddyblue

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.

  1. rename VMware-VMvisor-Installer-9.1.0.0100.25433460.x86_64.iso to VMware-VMvisor-Installer-9.1.0.0.25370933.x86_64.iso
  2. rename VCF-SDDC-Manager-Appliance-9.1.0.0100.25428926.ova to VCF-SDDC-Manager-Appliance-9.1.0.0.25371088.ova
  3. copy both renamed files to holorouter /holodeck-runtime/bin/9.1.0.0
  4. 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":"",
  5. start New-HoloDeckInstance

Additional context

No response

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions