WilliamLam.com

Quick Tip - How to deploy OVF/OVA to multiple networks using OVFTool?

by // Leave a Comment

For automation purposes, customers use the handy OVFTool, which is a multi-platform command-line utility for uploading or exporting OVF/OVA images. During an upload, users would typically specify the --network argument which will assign the desired vSphere Network to the deployed VM and if the VM included multiple network adapters, it would assign the same network which can then be modified during post-deployment.

What if you had a OVF/OVA that included multiple network adapters and you wanted a different network for each adapter? Luckily, this is also supported with OVFTool by using the --nic argument, which expects the network name as codified within the OVF/OVA to tell OVFTool which vSphere Network to assign. You can find OVF/OVA network name by simply running OVFTool command against the OVF/OVA without any arguments and you should see the name as shown in the screenshot below.


Note: The network name in the OVF/OVA MUST be unique to be able to assign different networks during upload.

[Read more...]

Automating the deployment of Application Transformer for VMware Tanzu

by // Leave a Comment

I recently wrote about our Application Transformer for VMware Tanzu solution and how it can really benefit IT Admins, beyond just the App Modernization use case which it was primarily designed for. App Transformer is provided as a Virtual Appliance (OVA) and the deployment using the vSphere UI is very straight forward. In this blog post, we will focus on automating the deployment of the App Transformer OVA.

To demonstrate the automation, I have created two example scripts, one that uses PowerCLI and the other using OVFTool. Both scripts contain the exact same variable names that will need to be updated by customers based on their environment. You can find the description for each variable blow covering both the appliance and application settings.

App Transformer Appliance Settings

  • AT_IP - IP Addres
  • AT_NETMASK - Netmask
  • AT_GATEWAY - Gateway
  • AT_DNS - DNS Server
  • AT_DNS_DOMAIN - DNS Search Domain
  • AT_DNS_SEARCH - DNS Search Path
  • AT_NTP - NTP Server
  • AT_ROOT_PASSWORD - Password for root (requires a minimum of 12 characters)

App Transformer Application Settings:

  • AT_USERNAME - Username to login to App Transformer UI
  • AT_PASSWORD - Password to login to App Transformer UI (requires a minimum of 12 characters)
  • AT_ENCRYPTION_PASSWORD - Password used to encrypt the database
  • AT_INSTALL_EMBEDDED_HARBOR - Install Embedded Harbor registry, useful for proof of concept/testing purposes

[Read more...]

Quick Tip - Dynamic OVF input properties using DeploymentOptions

by // Leave a Comment

I first talked about OVF DeploymentOptions back in 2013, which enables an OVF/OVA author to define a set of deployment profiles (e.g. small, medium, large) which then automatically translate to a pre-defined set of compute, network and storage configurations when deploying an OVF/OVA. There are a number VMware Appliances that takes advantage of this OVF capability, the most well known is the vCenter Server Appliance (VCSA) when it prompts you to select the size of the VCSA that you wish to deploy.


Now although the primary driver for DeploymentOptions is for having out of the box resource configurations when deploying an OVF/OVA, it can also be used to control which OVF properties are shown to end users for input based on the selected deployment option.

I recently had a need for this capability and it was only after taking another look at the OVF specification, did I realize this was possible through the use of DeploymentOptions. Below is a quick example on how you can control specific OVF properties. Imagine, we have three deployment options: Development, Stage and Production which maps to the following DeploymentOption IDs: dev, stage and prod

[Read more...]