Compute Profile (oVirt) limited to 8 Cores and 16GB of memory
|Assigned To:||Marek Hulán|
|Category:||Compute resources - oVirt|
|Target version:||Team Marek Iteration 3|
|Found in release:||1.7.2||Pull request:||https://github.com/theforeman/foreman/pull/3813|
|Velocity based estimate||-|
Compute Profile created using oVirt Compute Resource limits user to "8 Cores" and "16GB Memory" (available in the dropdowns) despite what's available on the oVirt/RHEV hypervisor environment.
These limits appear to be hardcoded in Foreman.
Could some extended intelligence be added to enable the user to select Core and Memory within bounds of the hypervisor environment ?
#1 Updated by Dominic Cleal about 2 years ago
- Category changed from Compute resources - libvirt to Compute resources - oVirt
#10 Updated by Marek Hulán 10 months ago
- Release changed from 1.14.0 to 1.13.0
Dominic, could I ask you to CP this to 1.13? It's related to #2314 and fixes the second part of the same problem, this time for CPU select field. I think it's safe, in worst case scenario if the JS that was added failed it would leave simple text field in the form. That would be still better than current 1.13 situation where select2 options are restricted to hardcoded maximum. Please reset to 1.14, if you disagree. I would fix all 1.13 related issues if that helped deciding :-)
#13 Updated by Dominic Cleal 10 months ago
RCs don't generally don't introduce bug fixes for issues that aren't regressions in the RC either, they're targeted for the next bug fix release (.1) instead. The RCs are there to stabilise the changes present when it was branched, I try not to keep adding new bug fixes else it never ends.
(The exception is usually only fixes that are good enough to go into a previous branch simultaneously, i.e. 1.12-stable, so as to ensure 1.13-stable is always ahead of 1.12-stable.)