add support for ovf transport com.vmware.guestInfo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
New
|
Undecided
|
Unassigned | ||
cloud-init |
Fix Released
|
Medium
|
Scott Moser |
Bug Description
cloud-init OVF datasource currently supports the OVF "ISO" transport (attached cdrom).
It should be updated to also support the com.vmware.
In this transport the ovf environment file can be read with:
vmtoolsd "--cmd=info-get guestinfo.ovfEnv"
Things to note:
a.) I recently modified ds-identify to invoke the vmtoolsd command above
in order to check the presense of the transport. It seemed to work
fine, running even before open-vm-
up. See http://
I think this can be made acceptable if do so only when on vmware.
b.) You can deploy a VM like this using OVFtool and the official Ubuntu OVA files. You simply need to modify the .ovf file inside the .ova to contain
<VirtualHard
Having both listed will "attach" both when deployed.
c.) after doing this and getting the changes into released ubuntu
we should change the official OVA on cloud-images.
the com.vmware.
Example ovftool command to deploy:
ovftool --datastore=
--
modified-
"vi://<email address hidden>
Related branches
- Server Team CI bot: Approve (continuous-integration)
- Scott Moser: Needs Resubmitting
- Ryan Harper: Needs Information
-
Diff: 251 lines (+121/-21)4 files modifiedcloudinit/sources/DataSourceOVF.py (+19/-15)
tests/unittests/test_datasource/test_ovf.py (+66/-6)
tests/unittests/test_ds_identify.py (+15/-0)
tools/ds-identify (+21/-0)
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Scott Moser (smoser) |
This bug is fixed with commit f55bb17d to cloud-init on branch master. /git.launchpad. net/cloud- init/commit/ ?id=f55bb17d
To view that commit see the following URL:
https:/