yahoo-eng-team team mailing list archive

[Russell Bryant <1234440@xxxxxxxxxxxxxxxxxx>]

This is expected behavior.  It's not really expected that an end user
that also does not have control over the configuration of the scheduler
would be setting these parameters.

** Tags added: scheduler

** Changed in: nova
       Status: New => Won't Fix

-- 
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/1234440

Title:
  scheduler will success if corresponding filter is not enabled

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  The extra_specs can be used to specify request to scheduler like
  trusted poll in trusted_filter.py or aggregate_instance_extra_specs.py
  and the scheduler would filter hosts based on the extra_spec value.

  However, below scenarios will cause issue:
  a) A flavor created specify that 'trust:trusted_host' is true, meaning that the instance can only run in trusted node, however, the trusted_filter is not enabled at all. Then the instance may be booted into non-trusted host.

  b) A flavor created specify the host aggregation requirement, but the
  AggregateInstanceExtraSpecsFilter is not enabled, the user may have no
  idea.

  I think a mechanism is needed to make sure the contents in the
  extra_specs, or more general, all boot requirement, has been checked.

  --jyh

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