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 :-) #openstack-state-management From: Doug Hellmann <[email protected]<mailto:[email protected]>> Reply-To: OpenStack Development Mailing List <[email protected]<mailto:[email protected]>> Date: Friday, August 16, 2013 1:24 PM To: OpenStack Development Mailing List <[email protected]<mailto:[email protected]>> 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 <[email protected]<mailto:[email protected]>> 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 event. >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: https://wiki.openstack.org/wiki/DuplicateWorkCeilometer 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. Thanks! -S cc/ Josh, I think the State Management team can really help out here. _______________________________________________ OpenStack-dev mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
