Open Stack

Hi,
Hopefully I will be able to address your questions. First lets start with
the group anti-affinity. This was added towards the end of the Grizzly
release cycle as a scheduling hint. At the last summit we sat and agreed
on a more formal approach to deal with this and we proposed and developed
https://blueprints.launchpad.net/openstack/?searchtext=instance-group-api-e
xtension (https://wiki.openstack.org/wiki/GroupApiExtension).
At the moment the following are still in review and I hope that we will
make the feature freeze deadline:
Api support:
https://review.openstack.org/#/c/30028/

Scheduler support:
https://review.openstack.org/#/c/33956/

Client support:
https://review.openstack.org/#/c/32904/

In order to make use of the above you need to add GroupAntiAffinityFilter
to the filters that will be active (this is not one of the default
filters). When you deploy the first instance of a group you need to
specify that it is part of the group. This information is used for
additional VM's that are being deployed.

Can you please provide some extra details so that I can help you debug the
issues that you have encountered (I did not encounter the problems that
you have described):
1. Please provide the commands that you used with the deploying of the
instance
2. Please provide the nova configuration file
3. Can you please look at the debug traces and see if you see the log
message on line 97 
(https://review.openstack.org/#/c/21070/8/nova/scheduler/filters/affinity_f
ilter.py)

Now regarding the AffinityFilter. At this stage this does not work with
the AntiAffinity filter. We were banking on this being used with the
multiple scheduler policies (https://review.openstack.org/#/c/37407/)

Thanks
Gary



On 9/3/13 10:16 AM, "Simon Pasquier" <simon.pasquier at bull.net> wrote:

>Reposting to openstack-dev as I got no answer on the general mailing list.
>
>
>-------- Message original --------
>Sujet: [Openstack] Confused about GroupAntiAffinityFilter and
>GroupAffinityFilter
>Date : Mon, 2 Sep 2013 11:19:58 +0200
>De : Simon Pasquier <simon.pasquier at bull.net>
>Organisation : Bulll SAS
>Pour : <openstack at lists.openstack.org>
>
>Hello,
>
>I tried to play with GroupAntiAffinityFilter and GroupAffinityFilter
>filters but it looks like the documentation is misleading [1]. Looking
>more precisely at the commits that introduced these filters [2][3], my
>assumption is that to use these filters, one would boot a first instance
>with '--hint group=foo' and the scheduler would update the
>instance_system_metadata table with {key:'group',value:'foo}. Then when
>starting other instances with the same hint option, the scheduler would
>filter the candidate hosts by querying the instance_system_metadata table.
>
>Still this doesn't work for me. In my tests with
>GroupAntiAffinityFilter, I have 3 compute nodes, each running one
>instance not in any group. Then when I launch a VM specifying a group
>hint, the scheduler fails to find a valid host because
>GroupAntiAffinityFilter filter returns 0 host.
>
>Could someone provide some guidance on how to use this filter?
>
>Regards,
>
>[1]
>http://docs.openstack.org/trunk/openstack-compute/admin/content/scheduler-
>filters.html#groupaffinityfilter
>[2] https://review.openstack.org/#/c/21070/
>[3] https://review.openstack.org/#/c/35788/
>
>-- 
>Simon Pasquier
>Software Engineer
>Bull, Architect of an Open World
>Phone: + 33 4 76 29 71 49
>http://www.bull.com
>
>_______________________________________________
>Mailing list: 
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>Post to     : openstack at lists.openstack.org
>Unsubscribe : 
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev