This is a follow up to VIRTSTRAT-81

Feature Overview

OpenShift Virtualization is now enabling higher workload density by default and is in turn making the use of your hardware more efficient.

Goals

• Allow customers to leverage their existing hardware. Today, due to the memory overcommit differences between existing hypervisors i.e. (1.5:1) and OCPv (1:1 by default) has lead to the situation, where the existing hardware did not have enough capacity anymore in order to run all the VMs it was able to run before - while it could, because the workloads had a low utilization.
• Today enabling memory overcommit via HCO, and provisioning SWAP are to actions on the customer. After this feature, this work will be done automatically, and transparently for all deployments.
• Simplify testing by making this feature (higher density) part of the default flow.

• Customers

Requirements

(Optional) Use Cases

How will the user interact with this feature? It will be almost transparent to users.

Out of Scope

Fix swap in OCP.
This is still a long term goal, but out of scope of this feature.
Eventually this feature would consume swap from OCP once it lands.

Background, and strategic fit

Two main reasons:
1. Improve testabilty by making it the default
2. Improve competitiveness by enabling memory overcommit by default

Assumptions

• <your text here>

Risks
CNV will have to own things that otherwise belong to the platform (SWAP and descheduler configuration).

Customer Considerations

We had 2 customers asking for making higher density simpler. (At this point in time)

Documentation Considerations

We want to create a dedicated section to describe higher density from a holistic pov. 

User Experience Considerations
No UXD support needed