Bug 2093932 - [RFE][CNV] memory overcommit in openshift virtualization
Summary: [RFE][CNV] memory overcommit in openshift virtualization
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.10.6
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: sgott
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-06 12:02 UTC by Ulhas Surse
Modified: 2025-10-03 12:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 12:23:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ulhas Surse 2022-06-06 12:02:55 UTC
Description of problem:


Version-Release number of selected component (if applicable):
OCP 4.10

What is the nature and description of the request?
-to have overcommit feature with ballooning memory , as described in the case 

Why do you need this? (List the business requirements here)
-mandatory for customer in large env

How would you like to achieve this? (List the functional requirements here)
- there is a need to add this func into OCP virt

Do you have any specific time-line dependencies?
- ASAP as we are in the phase of making PoC 

List any affected packages or components.
-  this func in OCP virt

Would you be able to assist in testing this functionality if implemented?
-it depends for how long time we will have PoC env

For each functional requirement listed in the previous question, can test to confirm the requirement is successfully implemented.
- if improvment will be done , we wil  check it and inform

Comment 2 sgott 2022-06-08 12:23:27 UTC
We are actively looking into this feature, but it is still in the design phase. Progress on that is being tracked in Jira. Because this is already being tracked, closing this BZ as deferred. Please feel to re-open if you feel this is in error.


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