Feature #10395

Compute Profile (oVirt) limited to 8 Cores and 16GB of memory

Added by Richard Davis about 2 years ago. Updated about 1 month ago.

Status:Closed
Priority:Normal
Assigned To:Marek Hulán
Category:Compute resources - oVirt
Target version:Team Marek Iteration 3
Difficulty: Bugzilla link:1458754
Found in release:1.7.2 Pull request:https://github.com/theforeman/foreman/pull/3813
Story points-
Velocity based estimate-
Release1.13.1Release relationshipAuto

Description

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 ?

Thanks


Related issues

Related to Foreman - Bug #1580: Limitiation to create only 32 GB VM Duplicate 04/20/2012
Related to Foreman - Bug #5901: Unable to select more than 8 cores in VMware template Closed 05/23/2014

Associated revisions

Revision 80963357
Added by Marek Hulán 10 months ago

Fixes #10395 - fine grain for CPU selectors

History

#1 Updated by Dominic Cleal about 2 years ago

  • Category changed from Compute resources - libvirt to Compute resources - oVirt

#2 Updated by Dominic Cleal over 1 year ago

  • Related to Bug #1580: Limitiation to create only 32 GB VM added

#3 Updated by Marek Hulán 12 months ago

  • Target version set to Team Marek backlog

#4 Updated by Marek Hulán 12 months ago

  • Target version changed from Team Marek backlog to Team Marek Iteration 1

#5 Updated by Marek Hulán 11 months ago

  • Target version changed from Team Marek Iteration 1 to Team Marek Iteration 2

#6 Updated by The Foreman Bot 11 months ago

  • Status changed from New to Ready For Testing
  • Assigned To set to Marek Hulán
  • Pull request https://github.com/theforeman/foreman/pull/3813 added

#7 Updated by Marek Hulán 11 months ago

  • Target version changed from Team Marek Iteration 2 to Team Marek Iteration 3

#8 Updated by Marek Hulán 10 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#9 Updated by Dominic Cleal 10 months ago

  • Release set to 1.14.0

#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 :-)

#11 Updated by Dominic Cleal 10 months ago

  • Release changed from 1.13.0 to 1.13.1

We can consider it for 1.13.1 if it appears stable, but this missed the 1.13.0 branching by a long time. It's not appropriate to add new features between RCs.

#12 Updated by Marek Hulán 10 months ago

I understand we don't introduce new features after branching but this is actually a bugfix. The bug is that user can't specify number higher than N... 1.13.1 is better than nothing though.

#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.)

#14 Updated by Marek Hulán 10 months ago

Ok, makes sense. I admit I'm biased on how safe it is to merge it :-) 1.13.1 is good (if the fix is stable enough), thanks for clarification.

#15 Updated by Marek Hulán 10 months ago

  • Related to Bug #5901: Unable to select more than 8 cores in VMware template added

#16 Updated by Ivan Necas about 1 month ago

  • Bugzilla link set to 1458754

Also available in: Atom PDF