Sorry I haven't come up with a snazzy name for it yet, but what I have
in mind is a new service that is essential for my employer (Rackspace), and
might be important for other OpenStack deployments. This new service would be
completely optional, of course - only those for whom it is relevant would run
it.
Let me start by stating the problem: when a customer requests that we
create instances for them, nova casts those requests into the queue, where they
are eventually acted upon. That usually works great, but in cases where the
instance creation fails, we need to detect that failure and re-issue the create
request with a different host. This is currently not possible with the
asynchronous design of the compute-scheduler interactions.
So what I envision is a service that scans a list of recent requests'
reservation IDs, and follows up to see if the request was successful or not,
and takes action if needed. The blueprint for this can be found at
https://blueprints.launchpad.net/nova/+spec/instance-creation-assurance, with
an Etherpad created for ongoing idea exchange at
http://etherpad.openstack.org/instance-creation-assurance
-- Ed Leafe
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
