yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

The code in the ironic virt driver to report VCPU/MEMORY_MB/DISK_GB
inventory was removed in Stein:

https://github.com/openstack/nova/commit/a985e34cdeef777fe7ff943e363a5f1be6d991b7

So this bug applies only to rocky/queens/pike.

Once the ironic instance flavor data migration is complete, it is then
safe to schedule only based on ironic node custom resource classes. We
have a nova-status check that goes back to queens for making sure you've
completed the data migration:

https://review.openstack.org/#/q/Ifd22325e849db2353b1b1eedfe998e3d6a79591c

Workarounds for this would be to use host aggregates to segregate VM and
BM hosts and pin flavors to those aggregates, or unset the
memory_mb/vcpu properties from ironic nodes, but those workarounds might
not be feasible at large scale (like CERN).

We can add a workaround config option to nova to disable reporting
standard resource class inventory for operators that can't use the other
alternative workarounds mentioned above and who know they have done
their data migrations.

** Tags added: ironic

** Changed in: nova
       Status: New => Triaged

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/pike
   Importance: Undecided
       Status: New

** Also affects: nova/rocky
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: Triaged => Invalid

** Changed in: nova/pike
       Status: New => Triaged

** Changed in: nova/queens
       Status: New => Triaged

** Changed in: nova/pike
   Importance: Undecided => High

** Changed in: nova/rocky
     Assignee: (unassigned) => Matt Riedemann (mriedem)

** Changed in: nova/queens
   Importance: Undecided => High

** Changed in: nova/rocky
       Status: New => Triaged

** Changed in: nova/rocky
   Importance: Undecided => High

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

Title:
  Baremetal nodes should not be exposing non-custom-resource-class
  (vcpu, ram, disk)

Status in OpenStack Compute (nova):
  Invalid
Status in OpenStack Compute (nova) pike series:
  Triaged
Status in OpenStack Compute (nova) queens series:
  Triaged
Status in OpenStack Compute (nova) rocky series:
  Triaged

Bug description:
  Description
  ===========
  Baremetal nodes report CPU, RAM and DISK inventory.

  The issue is that allocations for baremetal nodes are only done considering the custom_resource_class. This happens because baremetal flavors are set to not consume these resources.
  See: https://docs.openstack.org/ironic/queens/install/configure-nova-flavors.html

  If we use flavor that doesn't include a custom_resource_class ,
  placement can include a baremetal nodee that are already deployed because cpu, ram, disk is available (but results in a error from ironic), or worst the instance is created in a baremetal node (if it wasn't deployed yet).

  
  Environment
  ===========
  Nova and Ironic running Queens release.

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