[openstack-dev] [Ceilometer] Pipeline Retry Semantics ...
harlowja at yahoo-inc.com
Mon Aug 26 17:51:18 UTC 2013
Hey, seems like taskflow could help here also.
Check out the twiki which should have some good details for u guys: https://wiki.openstack.org/wiki/TaskFlow
Hit me up on irc if u guys want to talk :-)
From: Doug Hellmann <doug.hellmann at dreamhost.com<mailto:doug.hellmann at dreamhost.com>>
Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, August 16, 2013 1:24 PM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Ceilometer] Pipeline Retry Semantics ...
I added a couple of comments in the wiki page. We should have at least one summit session about this, I think, unless we work it out before then.
On Thu, Aug 15, 2013 at 12:20 PM, Sandy Walsh <sandy.walsh at rackspace.com<mailto:sandy.walsh at rackspace.com>> wrote:
Recently I've been focused on ensuring we don't drop notifications in
CM. But problems still exist downstream, after we've captured the raw
>From the efforts going on with the Ceilometer sample pipeline, the new
dispatcher model and the upcoming trigger pipeline, the discussion
around retry semantics has being coming up a lot.
In other words "What happens when step 4 of a 10 step pipeline fails?"
As we get more into processing billing events, we really need to have a
solid understanding of how we prevent double-counting or dropping events.
I've started writing down some thoughts here:
It's a little scattered and I'd like some help tuning it.
Hopefully it'll help grease the skids for the Icehouse Summit talks.
cc/ Josh, I think the State Management team can really help out here.
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev