OpenManage Enterprise 4.1.x User's Guide

Deploy programmatically

OpenManage Enterprise can be deployed programmatically (using a script) on VMware ESXi version 6.5 or later. Download Open Virtualization Format (OVF) files from the Dell support site.

1. Download and extract the openmanage_enterprise_ovf_format.zip file or download the following OVF files individually from the Dell support site:
   • openmanage_enterprise.x86_64-0.0.1-disk-0.vmdk
   • openmanage_enterprise.x86_64-0.0.1-disk-1.vmdk
   • openmanage_enterprise.x86_64-0.0.1.mf
   • openmanage_enterprise.x86_64-0.0.1.ovf
   • ovf_properties.config
   • update_ovf_property.py

   Place the files in the same folder where the OVF tool is installed (The default location is C:\Program Files\VMware\VMware OVF Tool).

2. Open the ovf_properties.config and set the following parameters:

   Table 1. Parameters in ovf_properties.configThe following table lists the parameters that are used in ovf_properties.config.

   Parameter	Accepted Values	Description
   bEULATxt	true or false	By setting this value to true, you agree to the terms and conditions in the End-User License Agreement (EULA). The EULA is available at the bottom of the ovf_properties.config file.
   adminPassword	The password should contain a minimum of eight characters. The password should contain at least one numerical character. The password should contain at least one special character.	Type a new administrator password for the OpenManage Enterprise.
   bEnableDHCP	true or false	Set to true if you want the appliance to enable IPv4 DHCP and to ignore the static IPv4.
   bEnableIpv6AutoConfig	true or false	Set to true if you want the appliance to enable IPv6 auto configuration and to ignore the static IPv6.
   staticIP	static IP in CIDR format	IP addresses can be IPv4 or IPv6. (You cannot set both the IPv4 and IPv6 types at a time.)
   gateway	IPv4 or IPv6	You cannot set static Gateway as IPv4 and IPv6 types at a time.

3. Open a command prompt terminal where the above files are located and run ovftool.exe while passing the following parameters:
   • --datastore=<> indicates the VMware datastore that assigns storage to the appliance.
   • -dm=<thin/thick> indicates whether storage is allocated to the appliance using thin or thick provisioning.
   • --name=<> is the user-defined name of the appliance.
   • --noSSLVerify skips SSL verification for vSphere connections.
   • --acceptAllEulas accepts all end-user license agreements without being prompted.
   • --X:logToConsole=true enables console logging during the deployment.
   • --X:logLevel="info" indicates the level of console logging. Possible levels of logging are none, quiet, panic, error, warning, info, verbose, or trivia.
   • --X:injectOvfEnv injects the passed parameters into the appliance when it is powering on.
   • --powerOn openmanage_enterprise.x86_64-0.0.1.ovf powers on the appliance post successful deployment.
   • vi://%{TEST_USERNAME}:%{TEST_PASSWORD}@%{TEST_URL}/%{TEST_RESOURCE}: The target locator indicates a local file path for the VMX, OVF, OVA, or vApprun workspace. Alternatively, it could indicate a vSphere locator identifying a cluster, host, or a vSphere location.

   NOTE:

   • The ovftool command must be run with the --X:injectOvfEnv and --powerOn flags because they are required for programmatic deployment.
   • Remember to replace the entire tag including the < and > symbols.
   For example, ovftool.exe --datastore=datastore2 -dm=thin --name=SampleAppliance --noSSLVerify --acceptAllEulas --X:logToConsole=true --X:logLevel="info" --X:injectOvfEnv --powerOn openmanage_enterprise.x86_64-0.0.1.ovf vi://root :user@xx.xx.xx.xx.
   After the ovftool command is run, the manifest validates and the deployment begins.