Project

General

Profile

Actions

Bug #27086

closed

Update hardcoded max values for CPUs and memory for ovirt CR

Added by Baptiste Agasse almost 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
trivial
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

max_cpu_count, max_socket_count and max_memory are hardcoded in the ovirt compute resources on the foreman side. It should be nice to update these value to actual supported values on ovirt side:

engine-config --get MaxNumOfVmCpus
MaxNumOfVmCpus: 288 version: 4.1
MaxNumOfVmCpus: 384 version: 4.2
MaxNumOfVmCpus: 384 version: 4.3

engine-config --get MaxNumOfVmSockets
MaxNumOfVmSockets: 16 version: 4.1
MaxNumOfVmSockets: 16 version: 4.2
MaxNumOfVmSockets: 16 version: 4.3

engine-config --get VM64BitMaxMemorySizeInMB
VM64BitMaxMemorySizeInMB: 4194304 version: 4.1
VM64BitMaxMemorySizeInMB: 4194304 version: 4.2
VM64BitMaxMemorySizeInMB: 4194304 version: 4.3

Updating these values to the lowest supported (4.1) should be nice.

Actions #1

Updated by The Foreman Bot almost 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Baptiste Agasse
  • Pull request https://github.com/theforeman/foreman/pull/6852 added
Actions #2

Updated by Baptiste Agasse almost 5 years ago

  • Tracker changed from Feature to Bug

As discussed in the PR, can be closed in favor of #27334 (I can't close it myself)

Actions #3

Updated by Baptiste Agasse over 4 years ago

  • Status changed from Ready For Testing to Rejected
Actions

Also available in: Atom PDF