cannot positively identify vmware cloud with ovf customization

Bug #1788708 reported by Scott Moser on 2018-08-23
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Pengzhen(Peter) Cao

Bug Description

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?

Scott Moser (smoser) on 2018-08-23
tags: added: ds-identify
tags: added: dsidentify
removed: ds-identify
Changed in cloud-init:
assignee: nobody → Pengzhen Cao (pengzhencao)
status: New → Confirmed
importance: Undecided → Medium
tags: added: dsid
removed: dsidentify
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers