© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
Another idea is simply don't keep any allocations on the migration record if we know we're doing same host resize, leave the max allocations on the instance record. That would have implications for how the allocations are cleaned up on revert or failure in the same host resize case, and older computes wouldn't have that logic...