Bug 1124670 - [RFE][ceilometer]: Rebase partitioned alarm evaluation on taskflow
Summary: [RFE][ceilometer]: Rebase partitioned alarm evaluation on taskflow
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Upstream M3
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/ceil...
Whiteboard: upstream_milestone_juno-3 upstream_de...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-30 04:04 UTC by RHOS Integration
Modified: 2015-03-19 17:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:22:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description RHOS Integration 2014-07-30 04:04:44 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/taskflow-alarm-partitioning.

Description:

In the long term, it could be a replacement for the PartitionedAlarmService. It uses the same basic idea: a master node keeps track of the alarms to be evaluated, but instead of distributing a slice of the alarms to each node, it just maintains a pool from which the other nodes can pick some work. This pool is managed by taskflow, for instance by using a multi-node Zookeeper configuration.

The election of the master node works as in the PartitionCoordinator.

In this service, the nodes are not "passive" (they do not wait for work to be given to them); they are "active" (they ask for work when they have nothing more to do).


Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.