© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Another tricky thing to keep in mind is the new flavor is used to update the instance.vcpus and instance.memory_mb values:
https:/
https:/
And those are used when counting quotas:
https:/
I'm not sure that directly affects the allocations really since it's different data in a different database, but reminds me that this might have implications if we start counting quota usage from placement:
https:/
Although with that proposal we're counting usage from the project_id, not the consumer, so as long as the migration/instance consumer allocations for that project are accurate (max of old/new flavors) we should be OK.