On Wed, May 2, 2018 at 12:49 PM, Matt Riedemann <mriede...@gmail.com> wrote: > On 5/2/2018 11:40 AM, Mathieu Gagné wrote: >> >> What's the state of caching_scheduler which could still be using those >> configs? > > > The CachingScheduler has been deprecated since Pike [1]. We discussed the > CachingScheduler at the Rocky PTG in Dublin [2] and have a TODO to write a > nova-manage data migration tool to create allocations in Placement for > instances that were scheduled using the CachingScheduler (since Pike) which > don't have their own resource allocations set in Placement (remember that > starting in Pike the FilterScheduler started creating allocations in > Placement rather than the ResourceTracker in nova-compute). > > If you're running computes that are Ocata or Newton, then the > ResourceTracker in the nova-compute service should be creating the > allocations in Placement for you, assuming you have the compute service > configured to talk to Placement (optional in Newton, required in Ocata). > > [1] https://review.openstack.org/#/c/492210/ > [2] https://etherpad.openstack.org/p/nova-ptg-rocky-placement
If one can still run CachingScheduler (even if it's deprecated), I think we shouldn't remove the above options. As you can end up with a broken setup and IIUC no way to migrate to placement since migration script has yet to be written. -- Mathieu _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
