From 4777f9f265058242b37f18046621c181715b82be Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Thu, 6 Apr 2017 09:59:30 -0400 Subject: [PATCH] Remove a fallacy in scheduler.driver config option help text Change fe3d6dba3d1db8f97dab4baffcc11dda56368096 removed the ability to specify a full classpath to load up your own scheduler driver. After that point stevedore extensions had to be used from setup.cfg. Change 6832a417c93046750ec7eff51eb59be802fd70dc encoded the supported in-tree scheduler driver options by using the "choices" kwarg with the scheduler.driver option. This means if you specify something not in that list, you get a ValueError. So the part in the help text about registering your own stevedore extension is a lie since it would still fail because of "choices". Change-Id: I60ce26f7370b71b2dc266d582d9b17d35e8cd9c1 --- nova/conf/scheduler.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/nova/conf/scheduler.py b/nova/conf/scheduler.py index 99e36bea3788..a2d5b6cda6c4 100644 --- a/nova/conf/scheduler.py +++ b/nova/conf/scheduler.py @@ -76,8 +76,6 @@ Possible values: multiple schedulers ** 'chance_scheduler', which simply picks a host at random ** 'fake_scheduler', which is used for testing -** A custom scheduler driver. In this case, you will be responsible for - creating and maintaining the entry point in your 'setup.cfg' file """), cfg.IntOpt("periodic_task_interval", default=60,