yahoo-eng-team team mailing list archive

[yao ning <1841932@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
when we enable nova AggregateInstanceExtraSpecsFilter, and then we need to passthrough a nvidia gpu so that we need to set hide_hypervisor_id in nova flavor extra specs. hide_hypervisor_id cannot pass the AggregateInstanceExtraSpecsFilter because of # Either not scope format, or aggregate_instance_extra_specs scope. 

See the codes below:
            # Either not scope format, or aggregate_instance_extra_specs scope
            scope = key.split(':', 1)
            if len(scope) > 1:
                if scope[0] != _SCOPE:
                    continue
                else:
                    del scope[0]
            key = scope[0]


Steps to reproduce
==================
in nova.conf
[filter_scheduler]
enabled_filters = ....,AggregateInstanceExtraSpecsFilter,...

create a flavor like "g3.8xlarge" and setting extra_specs
"hide_hypervisor_id":

nova flavor-key g3.8xlarge set hide_hypervisor_id=true

then create a instance with flavor g3.8xlarge, it will report "Filter
AggregateInstanceExtraSpecsFilter returned 0 hosts" in nova schedualer
log.

Environment
===========
(nova-scheduler)[nova@control1 /]$ rpm -qa | grep nova
openstack-nova-common-18.2.1-0.1.el7.noarch
openstack-nova-scheduler-18.2.1-0.1.el7.noarch
python-nova-18.2.1-0.1.el7.noarch
python2-novaclient-11.0.0-1.el7.noarch


I think this is a BUG in AggregateInstanceExtraSpecsFilter, can I suggest to remove the "not scope format" support in AggregateInstanceExtraSpecsFilter? or add a explicitly scope for "hide_hypervisor_id". Otherwise, I cannot use AggregateInstanceExtraSpecsFilter and hide_hypervisor_id at the same time.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  hide_hypervisor_id extra_specs in nova flavor cannot pass
  AggregateInstanceExtraSpecsFilter

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  when we enable nova AggregateInstanceExtraSpecsFilter, and then we need to passthrough a nvidia gpu so that we need to set hide_hypervisor_id in nova flavor extra specs. hide_hypervisor_id cannot pass the AggregateInstanceExtraSpecsFilter because of # Either not scope format, or aggregate_instance_extra_specs scope. 

  See the codes below:
              # Either not scope format, or aggregate_instance_extra_specs scope
              scope = key.split(':', 1)
              if len(scope) > 1:
                  if scope[0] != _SCOPE:
                      continue
                  else:
                      del scope[0]
              key = scope[0]

  
  Steps to reproduce
  ==================
  in nova.conf
  [filter_scheduler]
  enabled_filters = ....,AggregateInstanceExtraSpecsFilter,...

  create a flavor like "g3.8xlarge" and setting extra_specs
  "hide_hypervisor_id":

  nova flavor-key g3.8xlarge set hide_hypervisor_id=true

  then create a instance with flavor g3.8xlarge, it will report "Filter
  AggregateInstanceExtraSpecsFilter returned 0 hosts" in nova schedualer
  log.

  Environment
  ===========
  (nova-scheduler)[nova@control1 /]$ rpm -qa | grep nova
  openstack-nova-common-18.2.1-0.1.el7.noarch
  openstack-nova-scheduler-18.2.1-0.1.el7.noarch
  python-nova-18.2.1-0.1.el7.noarch
  python2-novaclient-11.0.0-1.el7.noarch

  
  I think this is a BUG in AggregateInstanceExtraSpecsFilter, can I suggest to remove the "not scope format" support in AggregateInstanceExtraSpecsFilter? or add a explicitly scope for "hide_hypervisor_id". Otherwise, I cannot use AggregateInstanceExtraSpecsFilter and hide_hypervisor_id at the same time.

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