Change compute updates from periodic to on demand

Registered by Don Dugger on 2014-06-03

Currently, all compute nodes update status info in the DB on a periodic basis (the period is currently 60 seconds). Given that the status of the node only changes at specific points (manyline image creation/destruction) this leads to significant DB overhead on a large system. This BP changes the update mechanism to only update the DB when a node state changes, specifically at node startup, instance creation and instance destruction.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
Don Dugger
Direction:
Approved
Assignee:
Don Dugger
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
Don Dugger on 2014-06-16
Completed by
John Garbutt on 2014-07-21

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/changes,n,z

Addressed by: https://review.openstack.org/97903
    Change compute updates from periodic to on demand

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)

Addressed by: https://review.openstack.org/101008
    Change compute updates from periodic to on demand

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.