filter_scheduler: dynamicall choose filters based on filter_properties
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.
Blueprint information
- Status:
- Not started
- Approver:
- John Garbutt
- Priority:
- Undefined
- Drafter:
- Liang Chen
- Direction:
- Needs approval
- Assignee:
- Liang Chen
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I think this is a cross cutting item that probably warrants some discussion. The idea is interesting, we have quite a few optimisations already. This will need a spec please, before we can approve it. --johnthetubaguy 11th June 2015