Re: [openstack-dev] [nova] Default scheduler filters survey

[Artom Lifshitz]

Thanks everyone for your input!

I wrote a small Python script [1] to present all your responses in an
understandable format. Here's the output:

Filters common to all deployments: {'ComputeFilter',
'ServerGroupAntiAffinityFilter'}

Filter counts (out of 9 deployments):
ServerGroupAntiAffinityFilter9
ComputeFilter9
AvailabilityZoneFilter   8
ServerGroupAffinityFilter8
AggregateInstanceExtraSpecsFilter8
ImagePropertiesFilter8
RetryFilter  7
ComputeCapabilitiesFilter5
AggregateCoreFilter  4
RamFilter4
PciPassthroughFilter 3
AggregateRamFilter   3
CoreFilter   2
DiskFilter   2
AggregateImagePropertiesIsolation2
SameHostFilter   2
AggregateMultiTenancyIsolation   1
NUMATopologyFilter   1
AggregateDiskFilter  1
DifferentHostFilter  1

Based on that, we can definitely say that SameHostFilter and
DifferentHostFilter do *not* belong in the defaults. In fact, we got
our defaults pretty spot on, based on this admittedly very limited
dataset. The only frequently occurring filter that's not in our
defaults is AggregateInstanceExtraSpecsFilter.

[1] https://gist.github.com/notartom/0819df7c3cb9d02315bfabe5630385c9

On Fri, Apr 27, 2018 at 8:10 PM, Lingxian Kong  wrote:
> At Catalyst Cloud:
>
> RetryFilter
> AvailabilityZoneFilter
> RamFilter
> ComputeFilter
> AggregateCoreFilter
> DiskFilter
> AggregateInstanceExtraSpecsFilter
> ImagePropertiesFilter
> ServerGroupAntiAffinityFilter
> SameHostFilter
>
> Cheers,
> Lingxian Kong
>
>
> On Sat, Apr 28, 2018 at 3:04 AM Jim Rollenhagen 
> wrote:
>>
>> On Wed, Apr 18, 2018 at 11:17 AM, Artom Lifshitz 
>> wrote:
>>>
>>> Hi all,
>>>
>>> A CI issue [1] caused by tempest thinking some filters are enabled
>>> when they're really not, and a proposed patch [2] to add
>>> (Same|Different)HostFilter to the default filters as a workaround, has
>>> led to a discussion about what filters should be enabled by default in
>>> nova.
>>>
>>> The default filters should make sense for a majority of real world
>>> deployments. Adding some filters to the defaults because CI needs them
>>> is faulty logic, because the needs of CI are different to the needs of
>>> operators/users, and the latter takes priority (though it's my
>>> understanding that a good chunk of operators run tempest on their
>>> clouds post-deployment as a way to validate that the cloud is working
>>> properly, so maybe CI's and users' needs aren't that different after
>>> all).
>>>
>>> To that end, we'd like to know what filters operators are enabling in
>>> their deployment. If you can, please reply to this email with your
>>> [filter_scheduler]/enabled_filters (or
>>> [DEFAULT]/scheduler_default_filters if you're using an older version)
>>> option from nova.conf. Any other comments are welcome as well :)
>>
>>
>> At Oath:
>>
>> AggregateImagePropertiesIsolation
>> ComputeFilter
>> CoreFilter
>> DifferentHostFilter
>> SameHostFilter
>> ServerGroupAntiAffinityFilter
>> ServerGroupAffinityFilter
>> AvailabilityZoneFilter
>> AggregateInstanceExtraSpecsFilter
>>
>> // jim
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
--
Artom Lifshitz
Software Engineer, OpenStack Compute DFG

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Default scheduler filters survey

[Lingxian Kong]

At Catalyst Cloud:

RetryFilter
AvailabilityZoneFilter
RamFilter
ComputeFilter
AggregateCoreFilter
DiskFilter
AggregateInstanceExtraSpecsFilter
ImagePropertiesFilter
ServerGroupAntiAffinityFilter
SameHostFilter

Cheers,
Lingxian Kong


On Sat, Apr 28, 2018 at 3:04 AM Jim Rollenhagen 
wrote:

> On Wed, Apr 18, 2018 at 11:17 AM, Artom Lifshitz 
> wrote:
>
>> Hi all,
>>
>> A CI issue [1] caused by tempest thinking some filters are enabled
>> when they're really not, and a proposed patch [2] to add
>> (Same|Different)HostFilter to the default filters as a workaround, has
>> led to a discussion about what filters should be enabled by default in
>> nova.
>>
>> The default filters should make sense for a majority of real world
>> deployments. Adding some filters to the defaults because CI needs them
>> is faulty logic, because the needs of CI are different to the needs of
>> operators/users, and the latter takes priority (though it's my
>> understanding that a good chunk of operators run tempest on their
>> clouds post-deployment as a way to validate that the cloud is working
>> properly, so maybe CI's and users' needs aren't that different after
>> all).
>>
>> To that end, we'd like to know what filters operators are enabling in
>> their deployment. If you can, please reply to this email with your
>> [filter_scheduler]/enabled_filters (or
>> [DEFAULT]/scheduler_default_filters if you're using an older version)
>> option from nova.conf. Any other comments are welcome as well :)
>>
>
> At Oath:
>
> AggregateImagePropertiesIsolation
> ComputeFilter
> CoreFilter
> DifferentHostFilter
> SameHostFilter
> ServerGroupAntiAffinityFilter
> ServerGroupAffinityFilter
> AvailabilityZoneFilter
> AggregateInstanceExtraSpecsFilter
>
> // jim
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Default scheduler filters survey

[Jim Rollenhagen]

On Wed, Apr 18, 2018 at 11:17 AM, Artom Lifshitz 
wrote:

> Hi all,
>
> A CI issue [1] caused by tempest thinking some filters are enabled
> when they're really not, and a proposed patch [2] to add
> (Same|Different)HostFilter to the default filters as a workaround, has
> led to a discussion about what filters should be enabled by default in
> nova.
>
> The default filters should make sense for a majority of real world
> deployments. Adding some filters to the defaults because CI needs them
> is faulty logic, because the needs of CI are different to the needs of
> operators/users, and the latter takes priority (though it's my
> understanding that a good chunk of operators run tempest on their
> clouds post-deployment as a way to validate that the cloud is working
> properly, so maybe CI's and users' needs aren't that different after
> all).
>
> To that end, we'd like to know what filters operators are enabling in
> their deployment. If you can, please reply to this email with your
> [filter_scheduler]/enabled_filters (or
> [DEFAULT]/scheduler_default_filters if you're using an older version)
> option from nova.conf. Any other comments are welcome as well :)
>

At Oath:

AggregateImagePropertiesIsolation
ComputeFilter
CoreFilter
DifferentHostFilter
SameHostFilter
ServerGroupAntiAffinityFilter
ServerGroupAffinityFilter
AvailabilityZoneFilter
AggregateInstanceExtraSpecsFilter

// jim
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Default scheduler filters survey

[Tobias Urdin]

Two different setups, very basic.

AggregateInstanceExtraSpecsFilter
RetryFilter
AvailabilityZoneFilter
ComputeFilter
ComputeCapabilitiesFilter
ImagePropertiesFilter
ServerGroupAntiAffinityFilter
ServerGroupAffinityFilter

RetryFilter
AvailabilityZoneFilter
RamFilter
ComputeFilter
ComputeCapabilitiesFilter
ImagePropertiesFilter
ServerGroupAntiAffinityFilter
ServerGroupAffinityFilter

On 04/18/2018 06:34 PM, Chris Friesen wrote:
> On 04/18/2018 09:17 AM, Artom Lifshitz wrote:
>
>> To that end, we'd like to know what filters operators are enabling in
>> their deployment. If you can, please reply to this email with your
>> [filter_scheduler]/enabled_filters (or
>> [DEFAULT]/scheduler_default_filters if you're using an older version)
>> option from nova.conf. Any other comments are welcome as well :)
> RetryFilter
> ComputeFilter
> AvailabilityZoneFilter
> AggregateInstanceExtraSpecsFilter
> ComputeCapabilitiesFilter
> ImagePropertiesFilter
> NUMATopologyFilter
> ServerGroupAffinityFilter
> ServerGroupAntiAffinityFilter
> PciPassthroughFilter
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Default scheduler filters survey

[Simon Leinen]

Artom Lifshitz writes:
> To that end, we'd like to know what filters operators are enabling in
> their deployment. If you can, please reply to this email with your
> [filter_scheduler]/enabled_filters (or
> [DEFAULT]/scheduler_default_filters if you're using an older version)
> option from nova.conf. Any other comments are welcome as well :)

We have the following enabled on our semi-public (academic community)
cloud, which runs on Newton:

AggregateInstanceExtraSpecsFilter
AvailabilityZoneFilter
ComputeCapabilitiesFilter
ComputeFilter
ImagePropertiesFilter
PciPassthroughFilter
RamFilter
RetryFilter
ServerGroupAffinityFilter
ServerGroupAntiAffinityFilter

(sorted alphabetically) Recently we've also been trying

AggregateImagePropertiesIsolation

...but it looks like we'll replace it with our own because it's a bit
awkward to use for our purpose (scheduling Windows instance to licensed
compute nodes).
-- 
Simon.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Default scheduler filters survey

[Jonathan D. Proulx]

On Wed, Apr 18, 2018 at 05:20:13PM +, Tim Bell wrote:
:I'd suggest asking on the openstack-operators list since there is only a 
subset of operators who follow openstack-dev.

I'd second that, which I'm (obviously) subscribed to both I do pay more
attention to operators, and almost missed this ask.

but here's mine:

scheduler_default_filters=ComputeFilter,AggregateInstanceExtraSpecsFilter,AggregateCoreFilter,AggregateRamFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,ImagePropertiesFilter,PciPassthroughFilter

:Tim
:
:-Original Message-
:From: Chris Friesen <chris.frie...@windriver.com>
:Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
:Date: Wednesday, 18 April 2018 at 18:34
:To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
:Subject: Re: [openstack-dev] [nova] Default scheduler filters survey
:
:On 04/18/2018 09:17 AM, Artom Lifshitz wrote:
:
:> To that end, we'd like to know what filters operators are enabling in
:> their deployment. If you can, please reply to this email with your
:> [filter_scheduler]/enabled_filters (or
:> [DEFAULT]/scheduler_default_filters if you're using an older version)
:> option from nova.conf. Any other comments are welcome as well :)
:
:RetryFilter
:ComputeFilter
:AvailabilityZoneFilter
:AggregateInstanceExtraSpecsFilter
:ComputeCapabilitiesFilter
:ImagePropertiesFilter
:NUMATopologyFilter
:ServerGroupAffinityFilter
:ServerGroupAntiAffinityFilter
:PciPassthroughFilter
:
:
:__
:OpenStack Development Mailing List (not for usage questions)
:Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
:http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
:
:
:__
:OpenStack Development Mailing List (not for usage questions)
:Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
:http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Default scheduler filters survey

[Tim Bell]

I'd suggest asking on the openstack-operators list since there is only a subset 
of operators who follow openstack-dev.

Tim

-Original Message-
From: Chris Friesen <chris.frie...@windriver.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Wednesday, 18 April 2018 at 18:34
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [nova] Default scheduler filters survey

On 04/18/2018 09:17 AM, Artom Lifshitz wrote:

> To that end, we'd like to know what filters operators are enabling in
> their deployment. If you can, please reply to this email with your
> [filter_scheduler]/enabled_filters (or
> [DEFAULT]/scheduler_default_filters if you're using an older version)
> option from nova.conf. Any other comments are welcome as well :)

RetryFilter
ComputeFilter
AvailabilityZoneFilter
AggregateInstanceExtraSpecsFilter
ComputeCapabilitiesFilter
ImagePropertiesFilter
NUMATopologyFilter
ServerGroupAffinityFilter
ServerGroupAntiAffinityFilter
PciPassthroughFilter


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Default scheduler filters survey

[Chris Friesen]

On 04/18/2018 09:17 AM, Artom Lifshitz wrote:


To that end, we'd like to know what filters operators are enabling in
their deployment. If you can, please reply to this email with your
[filter_scheduler]/enabled_filters (or
[DEFAULT]/scheduler_default_filters if you're using an older version)
option from nova.conf. Any other comments are welcome as well :)


RetryFilter
ComputeFilter
AvailabilityZoneFilter
AggregateInstanceExtraSpecsFilter
ComputeCapabilitiesFilter
ImagePropertiesFilter
NUMATopologyFilter
ServerGroupAffinityFilter
ServerGroupAntiAffinityFilter
PciPassthroughFilter


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev