yahoo-eng-team team mailing list archive

[Matthias Runge <1161988@xxxxxxxxxxxxxxxxxx>]

OK, agreed. There are a few occasions, where this is hard-coded. I wish
this didn't went in at all.

** Changed in: horizon
       Status: Invalid => Confirmed

** Changed in: horizon
   Importance: Undecided => Wishlist

** Changed in: horizon
    Milestone: None => icehouse-1

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

Title:
  Flavor naming shouldn't include "m1"

Status in devstack - openstack dev environments:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Confirmed
Status in OpenStack Compute (Nova):
  In Progress
Status in Python client library for heat:
  New
Status in Python client library for Nova:
  New
Status in Tempest:
  New

Bug description:
  Flavor naming shouldn't include "m1"

  ENV: devstack trunk / nova 814e109845b3b2546f60e3f537dcfe32893906a3
  (grizzly)

  The default flavors are now:
  m1.nano 
  m1.micro
  m1.tiny 
  m1.small 
  m1.medium 
  m1.large 
  m1.xlarge

  We are propagating AWS "m1" designation. This is not useful
  information to the OpenStack administrator or user, and it's actually
  possible misinformation as the "m1" on AWS suggests a specific
  generation of hardware.

  POSSIBLE SOLUTION:

  Drop the "m1":
  nano 
  micro
  tiny 
  small 
  medium 
  large 
  xlarge

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