Comment 6 for bug 1402502

Hi, Melanie,

"""There are likely many reasons for this, some of which I think are if you scheduled the extra instance while one was suspended, and you resume the suspended one, you can immediately get into an overcommit situation you didn't intend"""

I agree with you. I think, besides refreshing resource usage after "suspending", resource tracker should also be invoked before "resuming". In case "resume" action will lead to an overcommit situation, either an error code should be given, or an automatically migration should be performed.

I noticed that you set "Importance" field of "OpenStack Compute (nova) " as "Wishlist", does it mean that this will be improved in future?

"suspend" function is very important for us, as suspended instance can be resumed very quickly, as well as saving resources.
Different from "shelve", suspended instance will not be shutdown.
But if the resource usage didn't refresh after "suspend", why not leave it running? Since the released resource can't be used by other new instances.

Best Regards!
Jin Ming