Default 'tiny' instance_type has wrong root_gb
Bug #1175383 reported by
Rick Harris
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Rick Harris |
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.
Changed in nova: | |
assignee: | nobody → Rick Harris (rconradharris) |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/27991
Review: https:/