Epic Goal

• Determine the functional and performance implications of using memory overcommit (CNV-32385) and the descheduler (CNV-49434)

Why is this important?

• Customers may wish to use memory overcommit (currently using the wasp-agent) together with the descheduler for VMs.  The presumptive customer goal would be to maximize system utilization (with memory overcommit) while using the descheduler to balance resource usage across the cluster.

Scenarios

1. TBD

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>