Allow filters to be run only once per request if their data doesn't change
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
Nova bp: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Mark McLoughlin
- Priority:
- Medium
- Drafter:
- Guangya Liu (Jay Lau)
- Direction:
- Approved
- Assignee:
- Guangya Liu (Jay Lau)
- Definition:
- New
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Guangya Liu (Jay Lau)
- Completed by
- Guangya Liu (Jay Lau)
Related branches
Related bugs
| Bug #1266685: Allow filters to be run only once per request if their data doesn't change | Invalid |
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Allow filters to only run once per request if their data is static
