yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

As we use the "direct-release" model in Nova we don't use the
"fix comitted" status for merged bug fixes anymore. I'm setting
this manually to "fix-released" to be consistent.

[1] "[openstack-dev] [release][all] bugs will now close automatically
    when patches merge"; Doug Hellmann; 2015-12-07;
    http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html

** Changed in: nova
       Status: Fix Committed => Fix Released

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

Title:
  compute_node.metrics field should be a nova.objects object.

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Right now, the compute_nodes.metrics field is defined as a TEXT field
  and contains a straight JSON-ified string of the single-level dict of
  keys returned by the single monitor currently in the Nova tree: the
  CPU monitor.

  https://review.openstack.org/#/c/180983/12/specs/liberty/approved/mem-
  bw.rst introduces a potential new memory bandwidth monitor class, and
  we should evolve the metrics field to be a versioned object field
  instead of the flat string field it currently is.

  We need to do the following:

  1) Change the CPU monitor to return a nova.objects.CPUStats (or similar)
  2) Change nova.objects.ComputeNode's metrics field from a String field to a nova.objects.VirtMetrics field, which will have as its only field an ObjectField('CPUStats')
  3) Add data migration functionality that will convert over time the legacy JSON serialized metrics data into a serialized versioned object

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