Rebase partitioned alarm evaluation on tooz

Registered by Eoghan Glynn

The assignment of alarms to individual partitioned alarm evaluators could follow the same pattern as the division of resources between scaled-out central agents.

The evaluators will each join a tooz group, emit a periodic heartbeat to tooz, and accept callbacks from tooz when other evaluators join or leave the group.

Thus the set of evaluators share minimal knowledge, but this is sufficient to guide a hash-based approach to determining whether an individual alarm UUID falls under the responsibility of an individual evaluator.

So the current RPC-fanout-based presence reporting and the master/slave division of responsibilities can be dropped. Also the rebalancing logic when a certain threshold of alarm deletion is crossed will no longer be required.

Blueprint information

Status:
Complete
Approver:
Eoghan Glynn
Priority:
Medium
Drafter:
Eoghan Glynn
Direction:
Approved
Assignee:
Nejc Saje
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
Eoghan Glynn
Completed by
Eoghan Glynn

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/hash-based-alarm-partitioning,n,z

Addressed by: https://review.openstack.org/115237
    Switch partitioned alarm evaluation to a hash-based approach

Addressed by: https://review.openstack.org/113549
    Central agent work-load partitioning

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.