From 0c72e63948e053020e065769d353b95bc1989dd5 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Fri, 15 Mar 2019 11:44:06 -0400 Subject: [PATCH] Remove "Fixing the Scheduler DB model" from schedule evolution doc 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 --- doc/source/reference/scheduler-evolution.rst | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/doc/source/reference/scheduler-evolution.rst b/doc/source/reference/scheduler-evolution.rst index 8207d31faa97..5eb003da8507 100644 --- a/doc/source/reference/scheduler-evolution.rst +++ b/doc/source/reference/scheduler-evolution.rst @@ -72,17 +72,6 @@ Key areas we are evolving Here we discuss, at a high level, areas that are being addressed as part of 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 ------------------------------------------