We broke the possibility in Ocata with Icdcf839b6d28893694bfa1355e9dbe8dbb5ea8c3
to use other scheduler drivers but the ones we provided in tree.
Unfortunately, that was an incidental change without any communication.
Removing the choices kwarg will allow operators to run their own scheduler driver.
Whether Nova would stop supporting custom drivers would require a totally separate
change which would clearly communicate thru a deprecation notice but that is not
the intent for that bugfix, which aims only to bring back the capability.
Reviewed: https:/ /review. openstack. org/484828 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=1e5c7b52a40 3e708dba5a069dd 86b628a4cb952c
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1e5c7b52a403e70 8dba5a069dd86b6 28a4cb952c
Author: Sylvain Bauza <email address hidden>
Date: Tue Jul 18 16:33:49 2017 +0200
Accept any scheduler driver entrypoint
We broke the possibility in Ocata with Icdcf839b6d2889 3694bfa1355e9db e8dbb5ea8c3
to use other scheduler drivers but the ones we provided in tree.
Unfortunately, that was an incidental change without any communication.
Removing the choices kwarg will allow operators to run their own scheduler driver.
Whether Nova would stop supporting custom drivers would require a totally separate
change which would clearly communicate thru a deprecation notice but that is not
the intent for that bugfix, which aims only to bring back the capability.
Change-Id: I346881bc3bc487 94b139cc471be1d e11c49b8ee3
Closes-Bug: #1704788