Bug 1239087 - Nova scheduler doesn't check on DiskFilter
Summary: Nova scheduler doesn't check on DiskFilter
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: Director
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Director
Assignee: chris alfonso
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-03 13:05 UTC by Jaromir Coufal
Modified: 2016-04-18 06:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-06 13:31:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaromir Coufal 2015-07-03 13:05:16 UTC
Description of problem:
From logs in nova-scheduler it seems that we don't filter nodes based on DiskFilter. Therefore it happened multiple times that we miss-match required HW for storage or other roles.

Version-Release number of selected component (if applicable):
2015-07-02.1 Puddle

Steps to Reproduce:
1. deploy overcloud
2. check nova-scheduler log for filters

Actual results:
DiskFiler is missing from the list

Expected results:
We filter hosts based on Disk attribute as well

Additional info:
Flavor: http://paste.openstack.org/show/338519/
Miss-match: http://paste.openstack.org/show/338521/
Scheduler: http://pastebin.test.redhat.com/294742

Comment 3 Mike Burns 2015-07-06 13:31:29 UTC
The advanced matching is handled with ahc-tools.  Profiles are created and matched to flavors using ahc-tools

Comment 4 Jaromir Coufal 2015-07-07 08:45:18 UTC
This is definitely a bug. AHC is advanced filtering -- not installed by default. And I already was debugging two issues, where people were complaining that their compute nodes ended up on storage dedicated nodes and that our filtering doesn't work.

Furthermore in basic flow we instruct people to create nova flavors with certain disk size and then we are not filtering on them.


Note You need to log in before you can comment on or make changes to this bug.