yahoo-eng-team team mailing list archive

[OpenStack Infra <1774676@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/571998
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b4d87b33f93ab41721a77b1adc5c837833570be
Submitter: Zuul
Branch:    master

commit 1b4d87b33f93ab41721a77b1adc5c837833570be
Author: tianhui <tianhui@xxxxxxxxxxx>
Date:   Mon Jun 4 10:14:49 2018 +0800

    Fix bug to filter_scheduler
    
    In https://docs.openstack.org/nova/latest/configuration/config.html#filter_scheduler.max_instances_per_host
    refers to the "num_instances_filter" but that's the name
    of the python module, not the actual filter.
    So the config option help text should be updated to use
    the actual filter names that would go in the 'enabled_filters'
    option, not the python module in which those filters live.
    
    Change-Id: Icf7e64ed45fa5013714d85ea22794f106d4e387c
    Closes-bug: #1774676


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1774676

Title:
  Confusing usage information in  max_instances_per_host config option

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  https://docs.openstack.org/nova/latest/configuration/config.html#filter_scheduler.max_instances_per_host

  Refers to the "num_instances_filter" but that's the name of the python
  module, not the actual filter, and there are two of them:

  NumInstancesFilter
  AggregateNumInstancesFilter

  So the config option help text should be updated to use the actual
  filter names that would go in the 'enabled_filters' option, not the
  python module in which those filters live.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1774676/+subscriptions