© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Looking back over the history on this, it's my fault it looks like:
https:/
It also looks like we had some conversation about doing a max of the allocations rather than a sum:
https:/
And decided "do the sum since it's simpler". Well, that's great. :)
There was also a note added to the code that dealt with this in pike:
https:/
"""
# Note that we sum the allocations rather than take the max per
# resource class between the current and new allocations because
# the compute node/resource tracker is going to adjust for
# decrementing any old allocations as necessary, the scheduler
# shouldn't make assumptions about that.
"""
I believe that's referring to the fact that in Pike, if you still had at least one Ocata compute in the deployment, the resource tracker in the nova-compute service would delete the old allocations, or at least overwrite the allocations using the new flavor, so it sort of healed itself. However, once all of your computes are upgraded that is no longer true (the compute doesn't PUT allocations anymore since that's the job of the scheduler). Additionally, we have since dropped that old compute compatibility code.