Bug 1197295

Summary:	[RFE][nova]: filter_scheduler: dynamicall choose filters based on filter_properties
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/request-based-filter-selection
Whiteboard:	upstream_milestone_none upstream_definition_drafting upstream_status_not-started
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2015-02-28 05:01:52 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/request-based-filter-selection.

Description:

This feature will make filter_scheduler be able to dynamically choose and run only the filters that make sense to the current request based on the information available in filter_properties at runtime. This can reduce much of the overhead of filter running when some of the configured filters don't apply to most requests, especially if there is a large set of available filters configured. For example, an openstack deployment wants to have the ability to use JSON-based grammar for selecting hosts while booting instance. But majority of the expected use cases would not make use of the hint query. Trade off must be taken when configuring available filters without this request based filter selection feature. Having this in place, administrator will be free to choose available filters without the need of considering such potential computational waste.

Specification URL (additional information):

None