cannot positively identify vmware cloud with ovf customization

This bug was originally filed in Launchpad as [LP: #1788708](https://bugs.launchpad.net/cloud-init/+bug/1788708)

Launchpad details

affected_projects = []

assignee = pengzhencao

assignee_name = Pengzhen(Peter) Cao

date_closed = None

date_created = 2018-08-23T21:22:16.945680+00:00

date_fix_committed = None

date_fix_released = None

id = 1788708

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1788708

milestone = None

owner = smoser

owner_name = Scott Moser

private = False

status = confirmed

submitter = smoser

submitter_name = Scott Moser

tags = ['dsid']

duplicates = []

_Launchpad user **Scott Moser(smoser)** wrote on 2018-08-23T21:22:16.945680+00:00_

cloud-init (ds-identify) cannot positively identify a vmware cloud environment where customization data will be present. In order to avoid false positive, it requires the user to set 'disable_vmware_customization: false' in a config file.

That is a very bad user experience, and means that the image with that set is less portable as it will identify as OVF even if it is moved outside vmware.

We need a way to positively identify VMWare where OVF customization is expected.
On other clouds this is done via DMI information.

Can we have VMware identify itself to cloud-init in some way?