Project

General

Profile

Actions

Bug #15895

open

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

Added by Tomáš Strachota over 8 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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 1 (0 open1 closed)

Related to Foreman - Bug #2314: Smaller grains for VM memory/RAM choice neededClosedMarek Hulán03/13/2013Actions
Actions

Also available in: Atom PDF