Actions
Bug #15895
openFormat of memory and storage size in API should be more consistent
Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
-
Description
Expected formats of memory and storage parameters in compute attributes for hosts differ across compute resources. Also the parameter names are different:
Libvirt
memory: memory (integer, in bytes) storage: capacity (string, eg 10G)
oVirt
memory: memory (integer, in bytes) storage: size_gb (integer)
VMware
memory: memory_mb (integer) storage: size_gb (integer)
We should ideally provide consistent way of setting the attributes and convert them into a format required by Fog internally.
Updated by Tomáš Strachota over 8 years ago
- Related to Bug #2314: Smaller grains for VM memory/RAM choice needed added
Actions