yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1249279

Title:
  Resource Usage Page table views shows statistics in a wrong way

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  It was pointed out to me that some of the table columns are displayed
  in a wrong way, also the table heading Average 30 days won't be usable
  for all statistics.

  As I look back on this, almost each column has to be considered separately. So e.g. average over some time make
  sense only for gauge maybe delta type. Though for the cumulative type max makes much more sense. Also if I want
  to see a total value of a particular timeframe, I will have to do some extra computation (like max - min) to see e.g.
  network.incoming.bytes of the last month. (the max is a total of all times)

  There is e.g. *storage.objects.outgoing.bytes=Delta* but there is a * network. outgoing.bytes=Cumulative* , so there
  can't be unified approach of getting average over some time from them. Not sure why it is like that, but I am sure it has
  a good reason. :-)

  These table stats will be enhanced by the sparklines. So there it will
  be much more readable.

  The solution
  ==========

  Here comes the list of all used meters and description how each meter
  should be properly displayed:

  Global disk usage
  ------------------------

  "disk.read.bytes",
  "disk.read.requests",
  "disk.write.bytes",
  "disk.write.requests"

  All above are cumulative. The best here will be show 'total for last
  30 days aggregated by project'. But it will have to load all
  statistics grouped_by resource, computing (min - max) for each
  resource (gives the total amount in the time period for the one
  resource=disk). Then sum of them for each project is what we want. Or
  there can be average of them, not sure what is better.

  GlobalNetworkTrafficUsage
  ---------------------------------------

  "network.incoming.bytes"
  "network.incoming.packets"
  "network.outgoing.bytes"
  "network.outgoing.packets"

  Same approach as in Global disk usage will be done.

  GlobalNetworkUsage
  -----------------------------

  "network"
  "network_create"
  "subnet"
  "subnet_create"
  "port"
  "port_create"
  "router"
  "router_create"
  "ip_floating"
  "ip_floating_create"

  They all follow pattern of these two:

  "network" - Gauge - Duration - I suspect it doesn't return the time
  up, but rather 1 or 0, depending whether the network was up or down
  during sampling. Not sure what to show here. Maybe counting a duration
  of each network of the tenant in last 30 days and then show average
  up-time of them?

  "network_create" - Creation requests: I suspect the samples doesn't
  show e.g. number of network_creates but there is a one record for each
  network created. So this should show rather count then avg. The field
  would show 'total in 30 days aggregated by tenant'

  GlobalObjectStoreUsage
  ----------------------------------

  "storage.objects"
  "storage.objects.size"
  "storage.objects.incoming.bytes"
  "storage.objects.outgoing.bytes"

  all above are either delta or gauge and it make sense to leave them
  'last 30 days average aggregated by tenant' as it is now

  Confirmation from Ceilometer
  --------------------------------------------

  Not sure if I understand all of the meters correctly, eglynn please
  could you confirm or correct the above?

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