Bug 1041378

Summary: [RFE][nova]: Policy-based Scheduling Module
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: high    
Version: unspecifiedCC: markmc, ndipanov, sgordon, yeylon
Target Milestone: ---Keywords: FutureFeature, Triaged, Upstream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/policy-based-scheduler
Whiteboard: upstream_milestone_none upstream_status_needs-code-review upstream_definition_drafting
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:49:57 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 15:39:11 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/policy-based-scheduler.

Description:

In a cloud infrastructure it is important to be able to dynamically define different policies according to different contexts, like clients’ contracts, resource types, etc. This blueprint proposes a new scheduler driver which is capable of providing business-level services. It has four main characteristics:

    - Dynamic scheduling: Admin could dynamically change the policy at any moment without service disruption.
    - Client context consideration: The new scheduler would take into account the context of each and every client, so that their contracts are enforced.
    - Fine granularity: Admin could define one policy per group of resources to make the best use of the latter.
    - Extensible architecture: The new driver would be flexible; it could incorporate different policies determined by admin. In addition, the new driver would be generic in order to allow admin to integrate other solutions in it.

This driver functions according to the rules defined by admin. Admin can add/modify/remove rules at any moment to enforce different policies for a particular set of computes without service interruption.

Specification URL (additional information):

https://docs.google.com/document/d/1gr4Pb1ErXymxN9QXR4G_jVjLqNOg2ij9oA0JrLwMVRA