yahoo-eng-team team mailing list archive

["Dmitry \"Divius\" Tantsur" <divius.inside@xxxxxxxxx>]

** Summary changed:

- Changing nodes properties after it's deployed will count as available resources in Nova 
+ Changing node's properties in Ironic after node is deployed will count as available resources in Nova

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

** Tags added: ironic

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

Title:
  Changing node's properties in Ironic after node is deployed will count
  as available resources in Nova

Status in OpenStack Bare Metal Provisioning Service (Ironic):
  Triaged
Status in OpenStack Compute (Nova):
  New

Bug description:
  If you increase the properties of a node which was already deployed
  the different will go to nova as available resources. For e.g, a node
  with properties/memory_mb=512 was deployed, and n-cpu is showing:

  2014-04-02 10:37:26.514 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 0
  2014-04-02 10:37:26.514 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 0
  2014-04-02 10:37:26.514 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0

  Now if we update that that to properties/memory_mb=1024, the
  difference will be shown in nova as available resources:

  2014-04-02 10:40:48.266 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 512
  2014-04-02 10:40:48.266 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 0
  2014-04-02 10:40:48.266 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0

  LOGs: http://paste.openstack.org/show/74806/

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