openstack/nova
Code Issues Proposed changes

Remove "Fixing the Scheduler DB model" from schedule evolution doc

Browse Source 
Blueprint detach-service-from-computenode in Kilo decoupled the
compute node and services concepts so this section is no longer
relevant and can be removed from the doc - it's no longer evolving.

Change-Id: Ibba2aa83b0afe2be05415b69a1ff8ae86866b860
Related-Bug: #1820283
This commit is contained in:
Matt Riedemann 2019-03-15 11:44:06 -04:00
parent 18c40cacc1
commit 0c72e63948
1 changed files with 0 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/reference/scheduler-evolution.rst
View File

@ -72,17 +72,6 @@ Key areas we are evolving
Here we discuss, at a high level, areas that are being addressed as part of Here we discuss, at a high level, areas that are being addressed as part of
the scheduler evolution work. the scheduler evolution work.
Fixing the Scheduler DB model
------------------------------
We need the nova and scheduler data models to be independent of each other.
The first step is breaking the link between the ComputeNode and Service
DB tables. In theory where the Service information is stored should be
pluggable through the service group API, and should be independent of the
scheduler service. For example, it could be managed via zookeeper rather
than polling the nova DB.
Versioning Scheduler Placement Interfaces Versioning Scheduler Placement Interfaces
------------------------------------------ ------------------------------------------