Open Stack

On Wed, Apr 18, 2018 at 11:17 AM, Artom Lifshitz <alifshit at redhat.com>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180427/024981d5/attachment.html>