Size units are ambiguous in blockstorage createVolume API documentation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-api-site |
Fix Released
|
Medium
|
Diane Fleming | ||
openstack-manuals |
Fix Released
|
Medium
|
Diane Fleming |
Bug Description
The documentation says size in GBs
* http://
```
The size of the volume, in GBs.
```
But the implementations (that I've looked at) seem to interpret the supplied size as GiB
```
GB = units.Gi
```
* http://
```
Gi = 1024 ** 3
```
Eg
* The LVM driver appends `g` to the size
Which is interpreted by LVM as GiB...according to the `lvs` documentation
http://
```
--units hHbBsSkKmMgGtTpPeE
All sizes are output in these units: (h)uman-readable, (b)ytes, (s)ectors, (k)ilobytes, (m)egabytes, (g)igabytes, (t)erabytes, (p)etabytes, (e)xabytes. Capitalise to use multiples of 1000 (S.I.) instead of 1024. Can also specify custom units e.g. --units 3M
```
There is a related LVM documentation bug here:
* https:/
This is causing failures in our tests against Rackspace OpenStack, because we convert our `Byte` sizes to `GB` rather than `GiB`
* https:/
Changed in openstack-api-site: | |
assignee: | nobody → Diane Fleming (diane-fleming) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in openstack-manuals: | |
assignee: | Diane Fleming (diane-fleming) → Andreas Jaeger (jaegerandi) |
Changed in openstack-manuals: | |
assignee: | Andreas Jaeger (jaegerandi) → Diane Fleming (diane-fleming) |
Changed in openstack-api-site: | |
milestone: | none → liberty |
Changed in openstack-manuals: | |
milestone: | none → liberty |
Changed in openstack-api-site: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. openstack. org/184405
Review: https:/