Project

General

Profile

Actions
Copy link

Bug #5901

closed

Unable to select more than 8 cores in VMware template

Added by Jon Skarpeteig over 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Marek Hulán
Category:
Compute resources
Target version:
1.13.1
Difficulty:
trivial
Triaged:
Bugzilla link:
1364606
Pull request:
https://github.com/theforeman/foreman/pull/3814
Fixed in Releases:
Found in Releases:
1.5.0
Red Hat JIRA:

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 3 (0 open — 3 closed)

Related to Foreman - Bug #2314: Smaller grains for VM memory/RAM choice neededClosedMarek Hulán03/13/2013Actions
Related to Foreman - Feature #10395: Compute Profile (oVirt) limited to 8 Cores and 16GB of memoryClosedMarek Hulán05/06/2015Actions
Has duplicate Foreman - Bug #10687: Max CPU count for compute profile is 8Duplicate06/03/2015Actions
Actions
Copy link
 #1

Updated by Dominic Cleal over 10 years ago

  • Project changed from Smart Proxy to Foreman
  • Category changed from Virtualization to Compute resources
  • Priority changed from High to Normal
Actions
Copy link
 #2

Updated by Dominic Cleal over 10 years ago

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

Updated by Dominic Cleal over 10 years ago

  • Category changed from Compute resources to Compute resources - VMware
Actions
Copy link
 #4

Updated by Anonymous over 8 years ago

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

Updated by Martin Tessun over 8 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.

Actions
Copy link
 #6

Updated by Marek Hulán over 8 years ago

  • Category changed from Compute resources - VMware to Compute resources
  • Target version set to 115
Actions
Copy link
 #7

Updated by Marek Hulán over 8 years ago

  • Target version changed from 115 to 1.6.3
Actions
Copy link
 #8

Updated by Marek Hulán over 8 years ago

  • Target version changed from 1.6.3 to 1.6.0
Actions
Copy link
 #9

Updated by Ondřej Pražák over 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Ondřej Pražák
Actions
Copy link
 #10

Updated by Marek Hulán over 8 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.

Actions
Copy link
 #11

Updated by The Foreman Bot over 8 years ago

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

Updated by Marek Hulán over 8 years ago

  • Target version changed from 1.6.0 to 1.5.3
Actions
Copy link
 #13

Updated by Ondřej Pražák over 8 years ago

  • Assignee changed from Ondřej Pražák to Marek Hulán
Actions
Copy link
 #14

Updated by Marek Hulán over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #15

Updated by Marek Hulán over 8 years ago

  • Translation missing: en.field_release set to 190

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

Actions
Copy link
 #16

Updated by Marek Hulán over 8 years ago

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

Updated by Brad Buckingham over 8 years ago

  • Bugzilla link set to 1364606
Actions
Copy link

Also available in: Atom PDF