yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74412
[Bug 1788708] [NEW] cannot positively identify vmware cloud with ovf customization
Public bug reported:
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?
** Affects: cloud-init
Importance: Medium
Assignee: Pengzhen Cao (pengzhencao)
Status: Confirmed
** Tags: dsid
** Tags added: ds-identify
** Tags removed: ds-identify
** Tags added: dsidentify
** Changed in: cloud-init
Assignee: (unassigned) => Pengzhen Cao (pengzhencao)
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Tags removed: dsidentify
** Tags added: dsid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1788708
Title:
cannot positively identify vmware cloud with ovf customization
Status in cloud-init:
Confirmed
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1788708/+subscriptions
Follow ups