Nova plugin should listen to compute.instance.suspend events

[Steve McLellan]

Spying on nova's notifications, suspend (or resume) follows this order:

  compute.instance.[suspend,resume].start
  compute.instance.update
  compute.instance.[suspend,resume].end

We currently watch update events (and poweron/poweroff) but not suspend/resume (and this might be why we've had occasions where suspend/resume isn't represented well in the index. These additional events can map to update_or_create (though in actual fact they should only alter the running state).

[Steve McLellan (sjmc7)]

This might not actually be such a great idea while we hit the API on every event. At the very least wait until https://blueprints.launchpad.net/searchlight/+spec/optionally-disable-some-events is implemented.

[Travis Tripp (travis-tripp)]

This should be implemented so that callbacks to nova are not required.

[Steve McLellan (sjmc7)]

Lakshmi - looks like https://review.openstack.org/#/c/289599 addresses this?

[Lakshmi N Sampath (lakshmi-sampath)]

Looks like itisha started working on this at the same time I added this to bugsmash without assigning to herself. I can assign this bug to her.

[Steve McLellan (sjmc7)]

Moving this to n-1 because the current behavior while not ideal doesn't warrant a change at this stage. Once we can move to notification-only updates we can bring this in since it does represent the transient state change (resuming/suspending).

[Steve McLellan (sjmc7)]

This was fixed during newton.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Steve McLellan (<email address hidden>) on branch: master
Review: https://review.openstack.org/289599
Reason: This was added as part of the rework for nova status notifications