Allow filters to be run only once per request if their data doesn't change

Bug #1266685 reported by Guangya Liu (Jay Lau)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo-incubator
Invalid
Wishlist
Guangya Liu (Jay Lau)

Bug Description

Currently all scheduler filters are run for each resource in a request, but for many filters the data doesn’t change during a request.

For example the AZ filter is pretty static, but expensive to run on a large system.

I will introduces a new attribute that allows filters to declare that they only need to be run once per request. The default behavior is left as being run for each resource.

Nova already support this feature. I'm now planing to enable nova use oslo filters, so I need first put this feature to oslo then sync up to nova

Changed in oslo:
assignee: nobody → Jay Lau (jay-lau-513)
Changed in oslo:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo-incubator (master)

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

Changed in oslo:
status: Triaged → In Progress
Revision history for this message
Guangya Liu (Jay Lau) (jay-lau-513) wrote :

A bp was logged to trace this according to review comments: https://blueprints.launchpad.net/oslo/+spec/once-per-request-filters

Changed in oslo:
status: In Progress → Invalid
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.