throw exception if no configured affinity filter

Bug #1302238 reported by Guangya Liu (Jay Lau)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Gary Kotton

Bug Description

After https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension, nova has the feature of creating instance groups with affinity or anti-affinity policy and creating vm instance with affinity/anti-affinity group.

If did not enable ServerGroupAffinityFilter and ServerGroupAntiAffinityFilter, then the instance group will not able to leverage affinity/anti-affinity.

Take the following case:
1) Create a group with affinity
2) Create two vms with this group
3) The result is that those two vms was not created on the same host.

We should throw exception if using server group with no configured affinity filter

Tracy Jones (tjones-i)
tags: added: conductor
Revision history for this message
Gary Kotton (garyk) wrote :

I am not sure if the filters should be enabled by default. That could be a performance hit.

tags: added: scheduler
removed: conductor
Changed in nova:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Gary Kotton (garyk)
tags: added: icehouse-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/85594

Changed in nova:
status: Confirmed → In Progress
Gary Kotton (garyk)
Changed in nova:
milestone: none → juno-1
description: updated
summary: - Enable ServerGroupAffinityFilter and ServerGroupAntiAffinityFilter by
- default
+ throw exception if no configured affinity filter
Revision history for this message
Gary Kotton (garyk) wrote :
Changed in nova:
status: In Progress → Fix Released
Gary Kotton (garyk)
Changed in nova:
status: Fix Released → In Progress
Thierry Carrez (ttx)
tags: added: icehouse-backport-potential
removed: icehouse-rc-potential
Revision history for this message
John Garbutt (johngarbutt) wrote :

We use milestones only at the very end of the milestone to track bugs that should block the release of the milestone. Please use tags not milestones to track bugs, try things like: my_bug_topic_milestone_name

Changed in nova:
milestone: juno-1 → none
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/85594
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=18917d9e0d6fe250cc3b4f7301d37a6c5f5faffb
Submitter: Jenkins
Branch: master

commit 18917d9e0d6fe250cc3b4f7301d37a6c5f5faffb
Author: Gary Kotton <email address hidden>
Date: Sun Apr 6 05:54:23 2014 -0700

    Scheduler: throw exception if no configured affinity filter

    If the scheduler hint indicates that the scheduling should perform
    either anti-affinity or affinity scheduling and the relevant filter
    is not configured then a NoValidHost exception will be thrown.

    This is valuable if an existing OpenStack installation is running
    and these filters are not defined after an upgrade.

    Change-Id: I79bb44ad7481b3ff924687a8d6afdd6c715c0b59
    Closes-bug: #1302238

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → juno-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: juno-3 → 2014.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.