[openstack-dev] [Openstack-operators] [nova] Default scheduler filters survey

Jay Pipes jaypipes at gmail.com
Mon Apr 30 13:46:48 UTC 2018


On 04/30/2018 09:18 AM, Mikhail Medvedev wrote:
> On Sun, Apr 29, 2018 at 4:29 PM, Ed Leafe <ed at leafe.com> wrote:
>>
>> Another data point that might be illuminating is: how many sites use a custom (i.e., not in-tree) filter or weigher? One of the original design tenets of the scheduler was that we did not want to artificially limit what people could use to control their deployments, but inside of Nova there is a lot of confusion as to whether anyone is using anything but the included filters.
>>
>> So - does anyone out there rely on a filter and/or weigher that they wrote themselves, and maintain outside of OpenStack?
>>
> 
> Internal cloud that is used for Power KVM CI single use VMs:
> 
> AvailabilityZoneFilter
> AggregateMultiTenancyIsolation
> RetryFilter
> RamFilter
> ComputeFilter
> ComputeCapabilitiesFilter
> ImagePropertiesFilter
> CoreFilter
> NumInstancesFilter *
> NUMATopologyFilter
> 
> NumInstancesFilter is a custom weigher I have added that returns
> negative number of instances on a host. Using it this way gives an
> even spread of instances over the compute nodes up to a point the
> compute cores are filled up evenly, then it overflows to the compute
> nodes with more CPU cores. Maybe it is possible to achieve the same
> with existing filters, at the time I did not see how.

Hi Mikhail,

Did you mean to say you created a new *weigher*, not filter?

Best,
-jay



More information about the OpenStack-dev mailing list