Open Stack

Sure, the problem I'm immediately facing is reclaiming resources from the Capacity table when something fails. (we claim them immediately in the scheduler when the host is selected to lessen the latency).

The other situation is Orchestration needs it for retries, rescheduling, rollbacks and cross-service timeouts.

I think it's needed core functionality. I like Fail-Fast for the same reasons, but it can get in the way.

-S

________________________________________
From: openstack-bounces+sandy.walsh=rackspace.com at lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace.com at lists.launchpad.net] on behalf of Mark Washenberger [mark.washenberger at rackspace.com]
Sent: Wednesday, December 07, 2011 11:53 AM
To: openstack at lists.launchpad.net
Subject: Re: [Openstack] [Orchestration] Handling error events ... explicit     vs. implicit

Can you talk a little more about how you want to apply this failure notification? That is, what is the case where you are going to use the information that an operation failed? In my head I have an idea of getting code simplicity dividends from an "everything succeeds" approach to some of our operations. But it might not really apply to the case you're working on.