OpenStack Kilo Design Summit

The community is agreed upon the need for a scheduler system that can take into account more than just compute resource usage calculations, however we have a significant amount of refactoring work that is needed before a split of the current Nova scheduler will be feasible. It is possible to get all that refactoring done, but we need a concerted effort.

This session is intended to finalize the plan for refactoring in Kilo, including:

* Sign-off on the foundational blueprints that turn currently unstructured interfaces into versioned, object-driven interfaces

* Isolating any calls to the Nova database from within the scheduler

* Stabilizing the RPC API in preparation for a split of the scheduler and an eventual REST API

As well as discussions around what pieces of data the scheduler should eventually own and changes proposed to the resource claim interfaces.

Etherpad:

https://etherpad.openstack.org/p/kilo-nova-scheduler-rt

Session moderator: Jay Pipes (jaypipes@gmail.com)

Required reading:

Active blueprints:

* Isolate scheduler DB:
https://review.openstack.org/#/c/89893/

* Detach service from compute node:
https://review.openstack.org/#/c/126895/

* Isolate scheduler DB for instance groups:
https://review.openstack.org/#/c/131553/

* Model resource objects:
https://review.openstack.org/#/c/127609/

* Model request spec object:
https://review.openstack.org/#/c/127610/

* Change select_destinations() to use RequestSpec object:
https://review.openstack.org/#/c/127612/