On 5/2/2018 12:39 PM, Matt Riedemann wrote:
FWIW, I think we can also backport the data migration CLI to stable
branches once we have it available so you can do your migration in let's
say Queens before g
FYI, here is the start on the data migration CLI:
On Wed, May 2, 2018 at 1:39 PM, Matt Riedemann wrote:
>
> I know you're just one case, but I don't know how many people are really
> running the CachingScheduler with ironic either, so it might be rare. It
> would be nice to get other operator input here, like I'm guessing
On 5/2/2018 12:00 PM, Mathieu Gagné wrote:
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.
You're
On Wed, May 2, 2018 at 12:49 PM, Matt Riedemann 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
>
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
What's the state of caching_scheduler which could still be using those configs?
Mathieu
On Wed, May 2, 2018 at 12:25 PM, Matt Riedemann wrote:
> The baremetal scheduling options were deprecated in Pike [1] and the
> ironic_host_manager was deprecated in Queens [2] and is
The baremetal scheduling options were deprecated in Pike [1] and the
ironic_host_manager was deprecated in Queens [2] and is now being
removed [3]. Deployments must use resource classes now for baremetal
scheduling. [4]
The large host subset size value is also no longer needed. [5]
I've gone