Exactly! ... or it could be handled in the notifier itself.

From: openstack-bounces+sandy.walsh=rackspace....@lists.launchpad.net 
[openstack-bounces+sandy.walsh=rackspace....@lists.launchpad.net] on behalf of 
Mark Washenberger [mark.washenber...@rackspace.com]
Sent: Wednesday, December 07, 2011 12:36 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [Orchestration] Handling error events ... explicit     
vs. implicit


So the way this might work is, for example, when a run_instance fails on 
compute node, it would publish a "run_instance for uuid=<blah> failed" event. 
There would be a subscriber associated with the scheduler listening for such 
events--when it receives one it would go check the capacity table and update it 
to reflect the failure. Does that sound about right?

Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to