Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1197295 - [RFE][nova]: filter_scheduler: dynamicall choose filters based on filter_properties
Summary: [RFE][nova]: filter_scheduler: dynamicall choose filters based on filter_prop...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 7.0 (Kilo)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_defi...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-28 05:01 UTC by RHOS Integration
Modified: 2015-03-19 17:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

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


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