Just a heads up for anyone consuming Cinder APIs. The v1 API was
deprecated in the Juno release, but
we've kept it around for quite awhile because we knew there were client
implementations out there that
were lagging in getting up to date.
Well, it's now been many releases, and we've had the v1
>>Nisha is raising the question about whether or not we're making incorrect
assumptions >>about how people are using nova/ironic and they want to use
the non-Exact filters for >>VCPU/MEMORY_MB/DISK_GB, which as far as I have
ever heard is not >>recommended/supported upstream as it can lead to
resou
Forgot to copy the ops list on my reply.
Forwarded Message
Subject: Re: [openstack-dev] [nova][ironic] Concerns over rigid resource
class-only ironic scheduling
Date: Thu, 7 Sep 2017 14:57:24 -0500
From: Matt Riedemann
To: openstack-...@lists.openstack.org
On 9/7/2017 2:48
Hi Ironic Operators,
>From Pike, ironic nodes get scheduled based on just the resource class from
nova. Do you guys see any concerns over this "rigid resource class only
ironic scheduling"?
To be more specific, at your datacentre/production environment what all
filters are configured in nova.conf
