Bug 1041147

Summary: [RFE][nova]: Enable nova use filters/weight from oslo
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: low    
Version: unspecifiedCC: markmc, ndipanov, sgordon, yeylon
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/nova-oslo-scheduler
Whiteboard: upstream_milestone_none upstream_status_started upstream_definition_drafting
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:50:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 13:47:29 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/nova-oslo-scheduler.

Description:

Now in oslo, we already put some scheduler filters/weights logic there and cinder is using oslo scheduler filters/weights logic, seems we want both nova&cinder use this logic in future.

It is better to enable nova use filter/weight logic from oslo and also use entry point to handle all filters/weight logic.

We can first sync from oslo with following filteres/weights:
1) availablity_zone_filter.py
2) capabilities_filter.py
3) extra_specs_ops.py
4) json_filter.py
5) retry_filter.py
6) base_filter.py
7) base_handle.py
8) base_weight.py

The last work item is enable nova use entry point to handle scheduler filters/weights.

Specification URL (additional information):

None