yahoo-eng-team team mailing list archive

[Devananda van der Veen <1313779@xxxxxxxxxxxxxxxxxx>]

** Tags removed: nova-driver

** Changed in: ironic
       Status: Triaged => 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/1313779

Title:
  ResourceTracker auditing the wrong amount of free resources for Ironic

Status in OpenStack Bare Metal Provisioning Service (Ironic):
  Won't Fix
Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  I've two nodes avaiable in Ironic, they both have cpus=1,
  memory_mb=512, local_gb=10, cpu_arch=x86_64 but when you look at the
  audit logs it seems to be reporting the amount of resources of only
  one of the nodes:

  N-cpu:
  2014-04-28 16:09:47.200 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 512
  2014-04-28 16:09:47.200 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 10
  2014-04-28 16:09:47.200 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 1

  If I update the first of the nodes of the list and let's say double
  the ram, the audit will report it:

  N-cpu:
  2014-04-28 16:11:26.885 AUDIT nova.compute.resource_tracker [req-8a8a5d53-8cf1-4b9e-9420-5f0e3a6f9b27 None None] Free ram (MB): 1024

  But if I update the second node, no changes are reported back to the
  resource tracker...

  ...

  Worst, if I delete the properties from the first node, now the
  Resource Tracker will report:

  $ ironic node-update $NODE remove properties

  N-cpu:
  2014-04-28 16:13:07.735 AUDIT nova.compute.resource_tracker [req-c3211bd1-768d-40ea-b2cf-6e73c69e39b1 None None] Free ram (MB): 0
  2014-04-28 16:13:07.735 AUDIT nova.compute.resource_tracker [req-c3211bd1-768d-40ea-b2cf-6e73c69e39b1 None None] Free disk (GB): 0
  2014-04-28 16:13:07.735 AUDIT nova.compute.resource_tracker [req-c3211bd1-768d-40ea-b2cf-6e73c69e39b1 None None] Free VCPU information unavailable

  
  UPD from comment:
  We need to change Nova to understand the Ironic use case better. For nova each n-cpu is responsable for managing a X number of machines, but when the Ironic driver is loaded the n-cpu is just a small thin layer that talks to the Ironic api, and every n-cpu is managing _all_ the machines in the cluster. So in the Ironic use case different n-cpus would share the same machines and that's what making nova confused when auditing the resources.

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