Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
VMware: address instance resize problems
The resize code in the driver is problematic. This stems from the fact that a clone of the VM takes place. There are a number of know issues with this: 1. resize selects an invalid datastore (bug 1407438) 2. resize may fail when a selected host does not have access to the datastore that has the config driver file (bug 1407050) 3. resized instances are not marked as owned by OpenStack on the VC (bug 1402784) In fact we could do the resize on the existing VM. This has the following advantages: 1. it does not need an additional VM 2. it fixes the bugs that are mentioned above 3. It is now far simpler and more robust 4. It does not require convoluted instance naming and tracking 5. VM deletion is simple 6. enables better test covergae The patch makes use of the same VM for resizing. Methods no longer used have been removed. These methods were specific to the old resize. Co-authored-by: Radoslav Gerganov <rgerganov@vmware.com> Change-Id: Ibcb108c2e0f84a84c599d2e7762a11efc7659395 Closes-bug: #1407438 Closes-bug: #1407050 Closes-bug: #1402784
- Loading branch information
Showing
4 changed files
with
318 additions
and
417 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.