Hello, Patrick, Scott! I'll try to answer all your comments and show what vision we have now (after some internal discussions lasted all yesterday).
As for now we're under strong impression that the main consumer of Reservation-as-a-Service (as long as virtual resources are concerned) will be HEAT. Why? >From end user's perspective, it seems to be not sufficient to have separate reservations for a VM instance, Volume and Floating IP. User needs a way to attach reserved Volume to a reserved VM and associate Floating IP with it. Also, if there's a use case for that, we can support reservations of individual resources as well through Heat. That's why our current vision implies Heat as a main reservation consumer, and Climate as a service managing lease abstractions with its politics, notifications and so on.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
