yahoo-eng-team team mailing list archive

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

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

** Changed in: nova
    Milestone: None => havana-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/1175383

Title:
  Default 'tiny' instance_type has wrong root_gb

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  The current `tiny` instance_type currently has a `root_gb` setting of
  '0'.

  There are two problems with this:

  1) It doesn't follow the power of 2 pattern:

  m1.tiny root_gb=0   <= this should be 10
  m1.small root_gb=20
  m1.medium root_gb=40

  2) More importantly, a 0 root_gb means we can build an instance with
  it using xenserver because any the _check_vdi_size call will return
  false since any image will be greater than 0 bytes!

  The proposed solution is to just fix this going forward by updating
  the folsom migration. This won't affect, for better or worse, those
  who've already the migration, and presumably customized the instance
  types to meet their needs.

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