yahoo-eng-team team mailing list archive

[Doug Fish <drfish@xxxxxxxxxx>]

Public bug reported:

While reviewing https://review.openstack.org/#/c/96800 it seemed to me
the code would sometimes select a larger time unit that people would
normally use to describe the data.

Consider these 2 representations of 2 data sets

Data set 1a:  15 sec 30 sec 45 sec 30 sec 75 sec
Data set 1b:  .2 min .5 min .7 min 1.2 min

Data set 2a :  1 day 2 days 3 days 10 days 18 days
Data set 2b:  .1 weeks .3 weeks .4 weeks 1.4 weeks 2.6 weeks

IMO the "a" version is how people normally think about the data, yet the
metering unit code will select "b".

Specifically I think the metering time unit selection code should not
move to the next higher unit at 1 unit, but instead should convert at 2
or 3 units.

** Affects: horizon
     Importance: Undecided
     Assignee: Doug Fish (drfish)
         Status: New

** Changed in: horizon
     Assignee: (unassigned) => Doug Fish (drfish)

** Summary changed:

- Adjust metering units to sometime use a smaller unit
+ Adjust metering time units to sometime use a smaller unit

** Description changed:

  While reviewing https://review.openstack.org/#/c/96800 it seemed to me
- the code would sometimes select a larger unit that people would normally
- use to describe the data.
+ the code would sometimes select a larger time unit that people would
+ normally use to describe the data.
  
  Consider these 2 representations of 2 data sets
  
  Data set 1a:  15 sec 30 sec 45 sec 30 sec 75 sec
  Data set 1b:  .2 min .5 min .7 min 1.2 min
  
  Data set 2a :  1 day 2 days 3 days 10 days 18 days
  Data set 2b:  .1 weeks .3 weeks .4 weeks 1.4 weeks 2.6 weeks
  
  IMO the "a" version is how people normally think about the data, yet the
  metering unit code will select "b".
  
- Specifically I think the metering unit selection code should not move to
- the next higher unit at 1 unit, but instead should convert at 2 or 3
- units.
+ Specifically I think the metering time unit selection code should not
+ move to the next higher unit at 1 unit, but instead should convert at 2
+ or 3 units.

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

Title:
  Adjust metering time units to sometime use a smaller unit

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  While reviewing https://review.openstack.org/#/c/96800 it seemed to me
  the code would sometimes select a larger time unit that people would
  normally use to describe the data.

  Consider these 2 representations of 2 data sets

  Data set 1a:  15 sec 30 sec 45 sec 30 sec 75 sec
  Data set 1b:  .2 min .5 min .7 min 1.2 min

  Data set 2a :  1 day 2 days 3 days 10 days 18 days
  Data set 2b:  .1 weeks .3 weeks .4 weeks 1.4 weeks 2.6 weeks

  IMO the "a" version is how people normally think about the data, yet
  the metering unit code will select "b".

  Specifically I think the metering time unit selection code should not
  move to the next higher unit at 1 unit, but instead should convert at
  2 or 3 units.

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