The VMware Edge Cloud Orchestrator host can also be deployed directly from a pre-created VM packaged in a OVA.

The key differences from the preceding section are as follows:

  • This method uses a OVA package instead of the VMware Edge Cloud Orchestrator installer media.

  • The entire VMware Edge Cloud Orchestrator ESXi install phase is skipped, using the sizing of the VM baked in the OVA package.

  • The VMware Edge Cloud Orchestrator configuration input is provided directly through YAML files instead of ks.cfg kickstart document.

  • Download VMware Edge Cloud Orchestrator ESXi OVA along with deployment script and sample YAML input files on the machine where Fusion is running.

  • Modify keswick_firstboot.yaml sample to specify the GitOps configuration and Kubernetes workloads to be run (in addition to or in absence of GitOps provided workload). (Optional, if not provided to deployment script, the VMware Edge Cloud Orchestrator host runs the workload specified only through GitOps, if specified). This mode is useful for quick deployment verification and demo purpose.

  • Invoke the deployment script at a shell terminal prompt as follows. The deployment script imports the OVA as a VM, configures guestenv config for VMware Edge Cloud Orchestrator.

Procedure

  1. Download the following files to a local folder:
    1. deploy_keswickova.sh
    2. keswick_config.yaml
    3. keswick_firstboot.yaml
  2. Edit the keswick_config.yaml file according to your requirements.
  3. Edit the keswick_firstboot.yaml file according to your requirements.
  4. Start a terminal session and change directory (cd) to the folder where these items are downloaded and run the following commands:
    1. chmod +x ./deploy_keswickova.sh
    2. Replace CLI arguments appropriately in the following command: 
      /deploy_keswickova.sh -v fusion \  -o "path/to/ESXi-ec-...ova" \  -m a-unique-VM-name -r 'some-ec-ESXi-root-password' \  -f "./keswick_firstboot.yaml" \  -t "path/to/a/dir/to/store/ova-imported-vm"
      Note:

      ec-ESXi-root-password (specified in the -r CLI argument) must meet the ESXi password complexity requirements.