Keep disk resize behavior consistency for all hypervisor which ignore it
Currently, almost all of the hypervisor which can't safely resize the disk from bigger size to small size just ignore it, either compare the old size and newer size then just pick the bigger one or just log it, for both case it would be a problem since the flavor of the instance changed, but the disk size doesn't, for now just hyperv and xen verify it and thow a exception, for other hypervisor we need to deal with it in the same way.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Review
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I am glad to see this being done, as right now drivers all have different behaviors. It would be nice to see this blueprint generalized a little to cover other cases (that you list here) as well, but just an idea --jogo
Agreed, there's a whole spectrum of inconsistencies that could be tackled.
With Icehouse-1 just over two weeks away (December 5th), moving this to Icehouse-2 since it hasn't been started yet. If it does get into Icehouse-1, we can re-target. --jogo
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
