Bug #5901

Unable to select more than 8 cores in VMware template

Added by Jon Skarpeteig over 2 years ago. Updated 4 months ago.

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

Description

VMware itself supports up to 32 cores (on a single CPU). Max 32 virtual sockets combined.

E.G:
1 x 32
2 x 16
4 x 8
8 x 4

are all valid configurations


Related issues

Related to Foreman - Bug #2314: Smaller grains for VM memory/RAM choice needed Closed 03/13/2013
Related to Foreman - Feature #10395: Compute Profile (oVirt) limited to 8 Cores and 16GB of me... Closed 05/06/2015
Duplicated by Foreman - Bug #10687: Max CPU count for compute profile is 8 Duplicate 06/03/2015

Associated revisions

Revision 0cd2ddf0
Added by Marek Hulán 4 months ago

Fixes #5901 - fine grain for vmware CPU selectors

History

#1 Updated by Dominic Cleal over 2 years ago

  • Project changed from Smart Proxy to Foreman
  • Category changed from Virtualization to Compute resources
  • Priority changed from High to Normal

#2 Updated by Dominic Cleal over 2 years ago

  • Related to Bug #2314: Smaller grains for VM memory/RAM choice needed added

#3 Updated by Dominic Cleal over 2 years ago

  • Category changed from Compute resources to Compute resources - VMware

#4 Updated by Michael Moll 7 months ago

  • Duplicated by Bug #10687: Max CPU count for compute profile is 8 added

#5 Updated by Martin Tessun 7 months ago

Jon Skarpeteig wrote:

VMware itself supports up to 32 cores (on a single CPU). Max 32 virtual sockets combined.

That is not only true for VMWare, but for all Virtualisations (OVirt, RHEV, HyperV, etc.).
So it would be easiest to just have a possibility to enter a number for the amount of vCPUs (vCores) to be added.

#6 Updated by Marek Hulán 6 months ago

  • Category changed from Compute resources - VMware to Compute resources
  • Target version set to Team Marek backlog

#7 Updated by Marek Hulán 6 months ago

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

#8 Updated by Marek Hulán 5 months ago

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

#9 Updated by Ondřej Pražák 5 months ago

  • Status changed from New to Assigned
  • Assigned To set to Ondřej Pražák

#10 Updated by Marek Hulán 5 months ago

This should be based on the limited spinner introduced in http://projects.theforeman.org/issues/2314, now it's WIP because of webpack changes so I'd recommend waiting until the PR is megred.

#11 Updated by The Foreman Bot 4 months ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3814 added

#12 Updated by Marek Hulán 4 months ago

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

#13 Updated by Ondřej Pražák 4 months ago

  • Assigned To changed from Ondřej Pražák to Marek Hulán

#14 Updated by Marek Hulán 4 months ago

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

#15 Updated by Marek Hulán 4 months ago

  • Release set to 1.13.1

Same argumentation as for #10395, this one is tiny.

#16 Updated by Marek Hulán 4 months ago

  • Related to Feature #10395: Compute Profile (oVirt) limited to 8 Cores and 16GB of memory added

#17 Updated by Brad Buckingham 4 months ago

  • Bugzilla link set to 1364606

Also available in: Atom PDF