yahoo-eng-team team mailing list archive

[wuhao <wuhao@xxxxxxxxxxxxxxx>]

Public bug reported:

Currently, ComputeCapabilitiesFilter returns false if 'extra_specs'
can't retrieve in the host state. And, AggregateInstanceExtraSpecsFilter
also use extra_specs to create new instance in a host aggregate. The
problem is they failed to select any destinations, when the key is in
non-scope format. As is shown in,
https://github.com/openstack/nova/blob/master/nova/scheduler/filters/compute_capabilities_filter.py#L77.

For example, we may want to use host aggregate to create a new instance
in some servers with specified properties. So we create a new flavor and
set 'extra_specs' to {"property": "balabala"}，the
computecapabilitiesfilter will return false.  In this situation,
ComputeCapabilitiesFilter failed to work with
AggregateInstanceExtraSpecsFilter

I think we'd better check the capabilities only when the key for the
filter is scope format in capabilities scope (i.e.
capabilities:xxx:yyy), rather than non-scope format (i.e. no :
contained).

** Affects: nova
     Importance: Undecided
     Assignee: wuhao (wuhao)
         Status: New

** Description changed:

  Currently, ComputeCapabilitiesFilter returns false if 'extra_specs'
  can't retrieve in the host state. And, AggregateInstanceExtraSpecsFilter
  also use extra_specs to create new instance in a host aggregate. The
  problem is they failed to select any destinations, when the key is in
- on-scope format. As is shown in,
+ non-scope format. As is shown in,
  https://github.com/openstack/nova/blob/master/nova/scheduler/filters/compute_capabilities_filter.py#L77.
  
  For example, we may want to use host aggregate to create a new instance
  in some servers with specified properties. So we create a new flavor and
  set 'extra_specs' to {"property": "balabala"}，the
  computecapabilitiesfilter will return false.  In this situation,
  ComputeCapabilitiesFilter failed to work with
  AggregateInstanceExtraSpecsFilter
  
  I think we'd better check the capabilities only when the key for the
  filter is scope format in capabilities scope (i.e.
  capabilities:xxx:yyy), rather than non-scope format (i.e. no :
  contained).

** Changed in: nova
     Assignee: (unassigned) => wuhao (wuhao)

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

Title:
  ComputeCapabilitiesFilter failed to work with
  AggregateInstanceExtraSpecsFilter

Status in OpenStack Compute (nova):
  New

Bug description:
  Currently, ComputeCapabilitiesFilter returns false if 'extra_specs'
  can't retrieve in the host state. And,
  AggregateInstanceExtraSpecsFilter also use extra_specs to create new
  instance in a host aggregate. The problem is they failed to select any
  destinations, when the key is in non-scope format. As is shown in,
  https://github.com/openstack/nova/blob/master/nova/scheduler/filters/compute_capabilities_filter.py#L77.

  For example, we may want to use host aggregate to create a new
  instance in some servers with specified properties. So we create a new
  flavor and set 'extra_specs' to {"property": "balabala"}，the
  computecapabilitiesfilter will return false.  In this situation,
  ComputeCapabilitiesFilter failed to work with
  AggregateInstanceExtraSpecsFilter

  I think we'd better check the capabilities only when the key for the
  filter is scope format in capabilities scope (i.e.
  capabilities:xxx:yyy), rather than non-scope format (i.e. no :
  contained).

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