← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1771707] [NEW] allocation candidates with nested providers have inappropriate candidates when traits specified

 

Public bug reported:

* We are setting up two compute nodes with numa node & pf nested providers.
  And only one pf from cn1 has HW_NIC_OFFLOAD_GENEVE trait.

                   compute node (cn1)
            [CPU:16, MEMORY_MB:32768]
                 /+++++++++++++++\
                /++++++++++++++++ \
           cn1_numa0 ++++++++++++ cn1_numa1
               | ++++++++++++++++++ |
               | ++++++++++++++++++ | 
       cn1_numa0_pf0 ++++++++ cn1_numa1_pf1 (trait=HW_NIC_OFFLOAD_GENEVE)
     [SRIOV_NET_VF:8]                             [SRIOV_NET_VF:8]

                   compute node (cn2)
               [CPU:16, MEMORY_MB:32768]
                /++++++++++++++++++\
               /+++++++++++++++++++ \
           cn2_numa0 ++++++++++++ cn2_numa1
              | ++++++++++++++++++++ |
              | ++++++++++++++++++++ |
         cn2_numa0_pf0 ++++++++ cn2_numa1_pf1
    [SRIOV_NET_VF:8]                 [SRIOV_NET_VF:8]

* Next request with
    - resources={CPU: 2, MEMORY_MB: 256, SRIOV_NET_VF: 1}
    - required_traits=[HW_NIC_OFFLOAD_GENEVE]

* The expected result is to get allocation request with only “cn1_numa1_pf1”,
[('cn1’, fields.ResourceClass.VCPU, 2),
 ('cn1’, fields.ResourceClass.MEMORY_MB, 256),
 ('cn1_numa1_pf1’, fields.ResourceClass.SRIOV_NET_VF, 1)],

* But actually we also get allocation request with “cn1_numa1_pf0”  from the same tree with traits.
[('cn1’, fields.ResourceClass.VCPU, 2),
 ('cn1’, fields.ResourceClass.MEMORY_MB, 256),
 ('cn1_numa1_pf1’, fields.ResourceClass.SRIOV_NET_VF, 1)],
[('cn1’, fields.ResourceClass.VCPU, 2),
 ('cn1’, fields.ResourceClass.MEMORY_MB, 256),
 ('cn1_numa0_pf0', fields.ResourceClass.SRIOV_NET_VF, 1)],

** 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/1771707

Title:
  allocation candidates with nested providers have inappropriate
  candidates when traits specified

Status in OpenStack Compute (nova):
  New

Bug description:
  * We are setting up two compute nodes with numa node & pf nested providers.
    And only one pf from cn1 has HW_NIC_OFFLOAD_GENEVE trait.

                     compute node (cn1)
              [CPU:16, MEMORY_MB:32768]
                   /+++++++++++++++\
                  /++++++++++++++++ \
             cn1_numa0 ++++++++++++ cn1_numa1
                 | ++++++++++++++++++ |
                 | ++++++++++++++++++ | 
         cn1_numa0_pf0 ++++++++ cn1_numa1_pf1 (trait=HW_NIC_OFFLOAD_GENEVE)
       [SRIOV_NET_VF:8]                             [SRIOV_NET_VF:8]

                     compute node (cn2)
                 [CPU:16, MEMORY_MB:32768]
                  /++++++++++++++++++\
                 /+++++++++++++++++++ \
             cn2_numa0 ++++++++++++ cn2_numa1
                | ++++++++++++++++++++ |
                | ++++++++++++++++++++ |
           cn2_numa0_pf0 ++++++++ cn2_numa1_pf1
      [SRIOV_NET_VF:8]                 [SRIOV_NET_VF:8]

  * Next request with
      - resources={CPU: 2, MEMORY_MB: 256, SRIOV_NET_VF: 1}
      - required_traits=[HW_NIC_OFFLOAD_GENEVE]

  * The expected result is to get allocation request with only “cn1_numa1_pf1”,
  [('cn1’, fields.ResourceClass.VCPU, 2),
   ('cn1’, fields.ResourceClass.MEMORY_MB, 256),
   ('cn1_numa1_pf1’, fields.ResourceClass.SRIOV_NET_VF, 1)],

  * But actually we also get allocation request with “cn1_numa1_pf0”  from the same tree with traits.
  [('cn1’, fields.ResourceClass.VCPU, 2),
   ('cn1’, fields.ResourceClass.MEMORY_MB, 256),
   ('cn1_numa1_pf1’, fields.ResourceClass.SRIOV_NET_VF, 1)],
  [('cn1’, fields.ResourceClass.VCPU, 2),
   ('cn1’, fields.ResourceClass.MEMORY_MB, 256),
   ('cn1_numa0_pf0', fields.ResourceClass.SRIOV_NET_VF, 1)],

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


Follow ups