Bug #2314
Smaller grains for VM memory/RAM choice needed
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
Associated revisions
refs #2314 - more choices in memory drop down
(cherry picked from commit f7d5a22e0fd28c3689273c03b652d91b6ed661ae)
Fixes #2314 - fine grain for RAM selectors
Fixes #2314 - fine grain for RAM selectors
(cherry picked from commit eabbbeb4730abb51de2de8f9b302d26b14d6d33a)
History
#1
Updated by Robert Birnie over 8 years ago
- Assignee set to Robert Birnie
I also want this. PR incoming.
#3
Updated by Anonymous over 8 years ago
- Status changed from New to Ready For Testing
#4
Updated by Dominic Cleal over 8 years ago
- Category set to Compute resources
- Target version set to 1.9.2
#5
Updated by Dominic Cleal over 8 years ago
- Status changed from Ready For Testing to New
- Assignee deleted (
Robert Birnie) - Priority changed from High to Normal
- Target version deleted (
1.9.2)
Merging Robert's helpful change to add more options, but leaving this open so we can implement a more free-form entry (like text box or slider) as discussed on the PR.
#6
Updated by Dominic Cleal about 8 years ago
- Related to Bug #5901: Unable to select more than 8 cores in VMware template added
#7
Updated by Dominic Cleal almost 7 years ago
- Related to Bug #1580: Limitiation to create only 32 GB VM added
#8
Updated by Dominic Cleal almost 7 years ago
- Has duplicate Feature #12289: Possibility to set value of memory for compute profile under RHEV other then dropdown list added
#9
Updated by Dominic Cleal almost 7 years ago
- Subject changed from Smaller grains for Libvirt VM RAM needed to Smaller grains for VM memory/RAM choice needed
#10
Updated by Bryan Kearney almost 7 years ago
- Bugzilla link set to 1270771
#11
Updated by Marek Hulán about 6 years ago
- Target version set to 115
discussion about the partial solution can be found at PR https://github.com/theforeman/foreman/pull/1168
#12
Updated by Marek Hulán about 6 years ago
- Target version changed from 115 to 1.6.3
#13
Updated by Tomáš Strachota about 6 years ago
- Related to Bug #15895: Format of memory and storage size in API should be more consistent added
#14
Updated by Marek Hulán almost 6 years ago
- Status changed from New to Assigned
- Assignee set to Marek Hulán
#15
Updated by Marek Hulán almost 6 years ago
- Target version changed from 1.6.3 to 1.6.0
#16
Updated by The Foreman Bot almost 6 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3774 added
#17
Updated by Marek Hulán almost 6 years ago
- Target version changed from 1.6.0 to 1.5.3
#18
Updated by Marek Hulán almost 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset eabbbeb4730abb51de2de8f9b302d26b14d6d33a.
#19
Updated by Dominic Cleal almost 6 years ago
- Legacy Backlogs Release (now unused) set to 160
#20
Updated by Marek Hulán almost 6 years ago
- Related to Bug #16577: String::to_gb fails to parse "0 Bytes" added
#21
Updated by Marek Hulán almost 6 years ago
- Related to Refactor #16601: Cover spinner fields with tests added
#22
Updated by Anonymous almost 6 years ago
- Related to Bug #17199: Unable to create a new host deployed on XenServer added
#23
Updated by Anonymous over 5 years ago
- Has duplicate Feature #10875: Add option to choose between MB and GB when selecting Memory for new virtual machine added
#24
Updated by Anonymous over 5 years ago
- Has duplicate deleted (Feature #10875: Add option to choose between MB and GB when selecting Memory for new virtual machine)
#25
Updated by Anonymous over 5 years ago
- Related to Feature #10875: Add option to choose between MB and GB when selecting Memory for new virtual machine added
refs #2314 - more choices in memory drop down