Project

General

Profile

Bug #5901

Unable to select more than 8 cores in VMware template

Added by Jon Skarpeteig over 5 years ago. Updated about 1 year ago.

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

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 neededClosed2013-03-13
Related to Foreman - Feature #10395: Compute Profile (oVirt) limited to 8 Cores and 16GB of memoryClosed2015-05-06
Has duplicate Foreman - Bug #10687: Max CPU count for compute profile is 8Duplicate2015-06-03

Associated revisions

Revision 0cd2ddf0 (diff)
Added by Marek Hulán almost 3 years ago

Fixes #5901 - fine grain for vmware CPU selectors

Revision b9af9b32 (diff)
Added by Marek Hulán almost 3 years ago

Fixes #5901 - fine grain for vmware CPU selectors

(cherry picked from commit 0cd2ddf0cff1b07aeca2e2dee835937fde613b8b)

History

#1 Updated by Dominic Cleal over 5 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 5 years ago

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

#3 Updated by Dominic Cleal almost 5 years ago

  • Category changed from Compute resources to Compute resources - VMware

#4 Updated by Michael Moll over 3 years ago

  • Has duplicate Bug #10687: Max CPU count for compute profile is 8 added

#5 Updated by Martin Tessun about 3 years 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 about 3 years ago

  • Category changed from Compute resources - VMware to Compute resources
  • Target version set to 115

#7 Updated by Marek Hulán about 3 years ago

  • Target version changed from 115 to 1.6.3

#8 Updated by Marek Hulán about 3 years ago

  • Target version changed from 1.6.3 to 1.6.0

#9 Updated by Ondřej Pražák about 3 years ago

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

#10 Updated by Marek Hulán about 3 years 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 about 3 years 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 about 3 years ago

  • Target version changed from 1.6.0 to 1.5.3

#13 Updated by Ondřej Pražák almost 3 years ago

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

#14 Updated by Marek Hulán almost 3 years ago

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

#15 Updated by Marek Hulán almost 3 years ago

  • Legacy Backlogs Release (now unused) set to 190

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

#16 Updated by Marek Hulán almost 3 years ago

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

#17 Updated by Brad Buckingham almost 3 years ago

  • Bugzilla link set to 1364606

Also available in: Atom PDF