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.
Change-Id: I346881bc3bc48794b139cc471be1de11c49b8ee3
Closes-Bug: #1704788
(cherry picked from commit 1e5c7b52a403e708dba5a069dd86b628a4cb952c)
Reviewed: https:/ /review. openstack. org/490110 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=3eefcce2553 856a1635a62fecf 73cd9a2d9097cb
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit 3eefcce2553856a 1635a62fecf73cd 9a2d9097cb
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 8dba5a069dd86b6 28a4cb952c)
Closes-Bug: #1704788
(cherry picked from commit 1e5c7b52a403e70