Bug #15895

Format of memory and storage size in API should be more consistent

Added by Tomáš Strachota 8 months ago.

Status:New
Priority:Normal
Assigned To:-
Category:Compute resources
Target version:Team Marek backlog
Difficulty: Bugzilla link:
Found in release: Pull request:
Story points-
Velocity based estimate-

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.


Related issues

Related to Foreman - Bug #2314: Smaller grains for VM memory/RAM choice needed Closed 03/13/2013

History

#1 Updated by Tomáš Strachota 8 months ago

  • Related to Bug #2314: Smaller grains for VM memory/RAM choice needed added

Also available in: Atom PDF