Project

General

Profile

Actions

Bug #2314

closed

Smaller grains for VM memory/RAM choice needed

Added by Jaroslav Henner almost 12 years ago. Updated over 6 years ago.

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

Description

Currenly, I can create VM that has ... 1, 2, 4 or 8G ram. What if 4 is too much and 2 is too little?


Related issues 8 (3 open5 closed)

Related to Foreman - Bug #5901: Unable to select more than 8 cores in VMware templateClosedMarek Hulán05/23/2014Actions
Related to Foreman - Bug #1580: Limitiation to create only 32 GB VMDuplicateMarek Hulán04/20/2012Actions
Related to Foreman - Bug #15895: Format of memory and storage size in API should be more consistentNew07/29/2016Actions
Related to Foreman - Bug #16577: String::to_gb fails to parse "0 Bytes"ClosedMarek Hulán09/16/2016Actions
Related to Foreman - Refactor #16601: Cover spinner fields with testsNew09/19/2016Actions
Related to Xen - Bug #17199: Unable to create a new host deployed on XenServerClosed11/03/2016Actions
Related to Foreman - Feature #10875: Add option to choose between MB and GB when selecting Memory for new virtual machineNew06/18/2015Actions
Has duplicate Foreman - Feature #12289: Possibility to set value of memory for compute profile under RHEV other then dropdown listDuplicate10/23/2015Actions
Actions

Also available in: Atom PDF