Policy-based Scheduling Module

Registered by Khanh-Toan TRAN on 2013-10-15

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.

Blueprint information

Status:
Started
Approver:
Russell Bryant
Priority:
Undefined
Drafter:
Khanh-Toan TRAN
Direction:
Needs approval
Assignee:
Khanh-Toan TRAN
Definition:
Drafting
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Khanh-Toan TRAN on 2013-12-12

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/policy-based-scheduler,n,z

Addressed by: https://review.openstack.org/61386
    Policy-Based-Scheduler

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyGerrit topic: https://review.openstack.org/#q,topic:bp/policy-based-scheduler,n,z

Addressed by: https://review.openstack.org/61386
    Policy-Based-Scheduler

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)Gerrit topic: https://review.openstack.org/#q,topic:bp/policy-based-scheduler,n,z

Addressed by: https://review.openstack.org/61386
    Policy-Based-Scheduler

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyGerrit topic: https://review.openstack.org/#q,topic:bp/policy-based-scheduler,n,z

Addressed by: https://review.openstack.org/61386
    Policy-Based-Scheduler

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

Gerrit topic: https://review.openstack.org/#q,topic:bp/proposes,n,z

Addressed by: https://review.openstack.org/97503
    Create a scheduler that functions based on policies defined by admin.

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)

(?)

Work Items