[openstack-dev] VM Ensembles

Gary Kotton gkotton at redhat.com
Sun Feb 3 15:22:43 UTC 2013


Hi,

At last weeks nova meeting it was decided that the "initial patch to 
simply extend multi-boot to schedule with hint". This has been 
implemented by the following https://review.openstack.org/#/c/21070/ 
<https://review.openstack.org/#/c/21070/>

This patch does the following:
1. It introduces two scheduling hints:
     i. group_name - the name of a scheduling group
     ii. group_policy - the group scheduling policy. At the moment 
anti-affinity is supported. In the future we plan to add network proximity.
2. In order to be able to treat addition of new VM's to the scheduling 
policy the group_name and group_policy are stored in the database as 
metadata (hopefully at the summit we will be able to discuss this in 
more detail to see how they can become first class citizens).

In order to be able to achieve better performance and availability it 
would be best to do the entire group deployment in one shot (this is 
what was implemented in https://review.openstack.org/#/c/19906/ 
<https://review.openstack.org/#/c/19906/>)

Any input and comments will be great.
Thanks
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130203/51f83062/attachment.html>


More information about the OpenStack-dev mailing list