Different byte units in openstack API documentation
Bug #1714983 reported by
Dmitry
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-api-site |
Expired
|
Undecided
|
Unassigned | ||
openstack-manuals |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
There is a need to use one style for byte RAM units in api documentation.
As far as I discovered -
https:/
ram body integer The amount of RAM a flavor has, in MiB.
https:/
memory_mb body integer The memory of this hypervisor(in MB).
memory_mb_used body integer The memory used in this hypervisor(in MB).
Due to https:/
"MB" - in case of unit standart - can be interpreted as binary or decimal unit. So, we have ambigous situation with the RAM units in documentation.
Changed in openstack-manuals: | |
assignee: | nobody → Erwan Gallen (egallen) |
Changed in openstack-manuals: | |
assignee: | Erwan Gallen (egallen) → nobody |
Changed in openstack-manuals: | |
assignee: | nobody → Rajat Sharma (tajar29) |
Changed in openstack-manuals: | |
assignee: | Rajat Sharma (tajar29) → nobody |
Changed in openstack-api-site: | |
assignee: | nobody → Rajat Sharma (tajar29) |
Changed in openstack-api-site: | |
assignee: | Rajat Sharma (tajar29) → nobody |
To post a comment you must log in.
Removing from openstack-manuals and adding to the api-site project :) thank you