Bug 2223559 - [RFE] naming of VirtualMachineClusterInstancetype are not consistant with memory values
Summary: [RFE] naming of VirtualMachineClusterInstancetype are not consistant with mem...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Infrastructure
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Lee Yarwood
QA Contact: Roni Kishner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-18 08:37 UTC by Roni Kishner
Modified: 2023-07-19 12:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-19 12:02:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
large suffix list (6.50 KB, text/plain)
2023-07-18 08:37 UTC, Roni Kishner
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-31117 0 None None None 2023-07-18 08:38:00 UTC

Description Roni Kishner 2023-07-18 08:37:45 UTC
Created attachment 1976305 [details]
large suffix list

Description of problem:
The Values of spec.memory.guest in the VirtualMachineClusterInstancetype we deploy are not consistent with the names of the resources series.

example:
u1.large memory = 8Gi
m1.large memory = 16Gi
cx1.large memory =4Gi

Version-Release number of selected component (if applicable):
CNV 4.14.0

How reproducible:
100%

Actual results:
All the VirtualMachineClusterInstancetype with the "large" suffix have different values in spec.memory.guest

Expected results:
All of the series should have the same values in the memory when using the same "suffix" resource

Comment 1 Roni Kishner 2023-07-19 12:02:46 UTC
Decided to keep this behavior since different work loads use different sizing
for example: large desktop will need 8Gi while large server who uses 2 CPU will need 16Gi


Note You need to log in before you can comment on or make changes to this bug.