Open Stack

2014-02-10 18:45 GMT+01:00 Chris Friesen <chris.friesen at windriver.com>:

>
> In that model, we would pass a bunch of information about multiple
> resources to the solver scheduler, have it perform scheduling *and reserve
> the resources*, then return some kind of resource reservation tokens back
> to the caller for each resource.  The caller could then allocate each
> resource, pass in the reservation token indicating both that the resources
> had already been reserved as well as what the specific resource that had
> been reserved (the compute-host in the case of an instance, for example).
>
> Chris
>
>
Please be aware that Climate [1] already exists for managing resources
reservations. That doesn't make sense and has been discussed during last
summit that reservations should be managed by Nova, but rather by another
service.

-Sylvain

[1] : https://launchpad.net/climate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140211/59ba00c2/attachment.html>