resource tracker for bare metal nodes tries to subdivide resource

Bug #1178156 reported by Robert Collins
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
High
Unassigned

Bug Description

after deploying a small instance on big hardware:

2013-05-09 08:48:30,085.085 19736 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2013-05-09 08:48:30,208.208 19736 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 97792
2013-05-09 08:48:30,208.208 19736 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 2038
2013-05-09 08:48:30,209.209 19736 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 23
2013-05-09 08:48:30,308.308 19736 INFO nova.compute.resource_tracker [-] Compute_service record updated for ubuntu:96deccd5-0ad9-4bb5-979b-009bebac52fc

This should show 0, 0 and 0 : the size of the instance is not the amount to subtract :).

I don't know if this is just cosmetic.

Tags: baremetal
Revision history for this message
aeva black (tenbrae) wrote :

This suggests that BaremetalHostManager isn't doing what it's supposed to, which is ensure that a node's resources are consumed all-or-nothing.

Revision history for this message
Sean Dague (sdague) wrote :

Extremely old bm bug, marking as won't fix

Changed in nova:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.