...by accepting that in certain situations no load data is available. - If an instance has recently migrated, load data is not available on the new node; we can use the one from the old node, assuming that the way the instance is used has not changed by the migration.
- If an instance has recently been moved off an offline node, data on the old node is not available either. In order to continue quickly with the evacuation of that node, we assume that the load is 0 which is a fair assumption for an instance running on a down node. Klaus Aehlig (6): Speed up balancing by accepting pre-migration loads Make the Xen CPU collector keep old data longer Extend maintenance configuration by evacuated instances Also keep the list of recently evacuated instance in memory Keep track of Xen instances moved out of offline nodes Expose the list of recently evacuated instances lib/objects.py | 2 +- man/ganeti-maintd.rst | 7 +++ src/Ganeti/DataCollectors/XenCpuLoad.hs | 3 +- src/Ganeti/MaintD/Balance.hs | 98 ++++++++++++++++++++++++++------ src/Ganeti/MaintD/MemoryState.hs | 36 ++++++++++-- src/Ganeti/MaintD/Server.hs | 3 +- src/Ganeti/Objects/Maintenance.hs | 1 + src/Ganeti/WConfd/ConfigModifications.hs | 12 ++++ src/Ganeti/WConfd/Core.hs | 7 ++- 9 files changed, 143 insertions(+), 26 deletions(-) -- 2.5.0.rc2.392.g76e840b
