Skip to content

Automating the Deployment of Log Insight

Log Insight ships as a virtual appliance. Given its single packaging model, automated deployment is easy thanks to the freely available OVF Tool. OVF Tool is a command line utility available for Windows, Linux and Mac that allows you to deploy OVA/OVF files. For the list of options available with OVF Tool run ovftool –help or see check the documentation. I would like to walk you through how to automate the deployment of Log Insight via ovftool.

Log Insight OVA options

The easiest way to see what options are available as part of an OVA/OVF is to run ovftool without any flags, but specifying the OVA/OVF to be deployed (e.g. ovftool </path/to/loginsight.ova>). In the case of Log Insight, the important options are:

  • Networks

  • Properties

  • Deployment Options

Additional OVF Tool information

In addition to the Log Insight OVA options, a few additional pieces of information are needed:

  • Name – what do you want to call the OVA/OVF in vSphere/vCD?
  • Datastore – to which datastore do you wish to deploy the OVA/OVF?
  • Power on – do you wish to power on the OVA/OVF post-deployment?
  • Where – where exactly do you want to deploy the OVA/OVF?
    • vSphere – requires information such as username, password, FQDN/IP of vCS, datacenter name, and cluster/host name
    • vCD – requires information such as username, password, FQDN/IP of vCD, organization name, vdc name, and catalog name

OVF Tool command gotchas

With all of this information, all you need to do is construct an ovftool command. The two places where this can be difficult are:

  • Specifying the desired properties in the correct format – In the case of properties, the format is: –prop:<ClassId>.<Key>.<InstanceId>=”<yourInfoHere>”. Most people, myself included, make the mistake of trying to use –prop:<Key>=”<yourInfoHere>”, which does not work.
  • Specifying the destination in the correct format – be sure to check the documentation if you are running into issues here
    • For vSphere, the format is: vi://<username>:<password>@<host>:<port>/<search-term>
    • For vCD, the format is: vcloud://username:[email protected]:port?org=name_of_org&vapp=name_of_deployed_vapp&catalog=name_of_catalog &vappTemplate=name_of_vapp_template_in_catalog&vdc=name_of_vdc

Deploying Log Insight with OVF Tool

So how do you use ovftool to deploy Log Insight?

  • For production environments a static IP address should be used, in which case the following ovftool command will work to deploy to vSphere:

  • For demo/POC environments you may be okay with DHCP network settings, in which case the following ovftool command will work to deploy to vSphere:

UPDATE: Added allow extra config flag and root password information introduced in Log Insight 2.0.

© 2014, Steve Flanders. All rights reserved.

Published inVMware

Be First to Comment

    Leave a Reply

    Your email address will not be published. Required fields are marked *