Merge ~pengpengs/cloud-init:fix/load-DataSourceOVF-at-the-last-on-VMware-Platform-if-no-data-found into cloud-init:master
Status: | Needs review |
---|---|
Proposed branch: | ~pengpengs/cloud-init:fix/load-DataSourceOVF-at-the-last-on-VMware-Platform-if-no-data-found |
Merge into: | cloud-init:master |
Diff against target: |
127 lines (+38/-20) 2 files modified
cloudinit/sources/DataSourceOVF.py (+34/-16) tests/unittests/test_vmware_config_file.py (+4/-4) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Scott Moser | Needs Fixing | ||
Review via email: mp+375587@code.launchpad.net |
Description of the change
1. Generate random instance-id when vmware customization cfg found. If use fixed
instance-id, network configuration in customization cfg will not be applied.
2. Load DatasourceOVF when no vmware customization cfg found if machine fulfills:
a. VMware Virtualization Platform found
b. flag vmware_
c. flag disable_
d. VMware tools deployPkgPlugin found
These conditions are same with the ones in ds-identify script, if ds-identify
found OVF, then load DatasourceOVF.
3. Read instance-id from machine and set it to metadata when no vmware customization
cfg found, this prevents cloud-init load default network configuration, so that
existing network configuration will not be overwritten.
4. Modify check instance-id unittest.
5. Modify default timeout for waiting vmware customization cfg, 30 seconds
should be enough.
@Pengpeng,
Cloud-init has moved code-hosting and pull request to github. Please re-submit there.
https:/ /lists. launchpad. net/cloud- init/msg00231. html