[openstack-dev] [scheduler] APIs for Smart Resource Placement - Updated Instance Group Model and API extension model - WIP Draft

Sylvain Bauza sylvain.bauza at bull.net
Tue Oct 8 07:40:01 UTC 2013


Hi Yathi,

Le 08/10/2013 05:10, Yathiraj Udupi (yudupi) a écrit :
> Hi,
>
> Based on the discussions we have had in the past few scheduler 
> sub-team meetings,  I am sharing a document that proposes an 
> updated Instance Group Model and API extension model.
> This is a work-in-progress draft version, but sharing it for early 
> feedback.
> https://docs.google.com/document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit?usp=sharing 
>
>
> This model support generic instance types, where an instance can 
> represent a virtual node of any resource type.  But in the context of 
> Nova, an instance refers to the VM instance.
>
> This builds on the existing proposal for Instance Group Extension as 
> documented here in this blueprint: 
> https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension
>
> Thanks,
> Yathi.



Well, I actually read the design document, and I'm strongly interested 
in jumping to the project.
We started a few months ago a Stackforge project, called Climate [0], 
aiming to reserve both physical and virtual resources. Initially, the 
project came from a blueprint targeting only physical reservations [1], 
and then Mirantis folks joined us having a new usecase for virtual 
reservations (potentially implementing deferred starts, as said above).

Basically, the physical host reservation is not about deferred starts of 
instances, it's about grouping for a single tenant a list of hosts, in 
other words a whole host allocation (see [2]).

We'll provide to end-users a Reservation API allowing to define policies 
for selecting hosts based on their capabilities [3] and then create host 
aggregates (or "Pclouds" if we implement [2]). Actually, we could define 
some policies in the Climate host aggregate for affinity and 
network-proximity policies, so that any VM to boot from one of these 
hosts would be applied these host aggregate policies.

As you maybe see, there are some concerns which are close in between 
your BP [4] and our vision of Climate. What are your thoughts about it ?

[0] : https://github.com/stackforge/climate
[1] : 
https://wiki.openstack.org/wiki/Blueprint-nova-planned-resource-reservation-api
[2] : https://wiki.openstack.org/wiki/WholeHostAllocation
[3] : 
https://docs.google.com/document/d/1U36k5wk0sOUyLl-4Cz8tmk8RQFQGWKO9dVhb87ZxPC8/edit#heading=h.ujapi6o0un65
[4] : 
https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131008/a16d2b22/attachment.html>


More information about the OpenStack-dev mailing list