-
Epic
-
Resolution: Unresolved
-
Critical
-
None
SUMMARY
Some workloads are going to require the ability to do memory hotplug, especially compute intensive tasks.
USER STORIES
- As cluster admin/operator i would like to add additional compute power so that i could give extra processing power during an end of the month/year periods
UX DESIGN DOC
https://docs.google.com/document/d/15bo-vDVzxVBpctxzeP_GhV8E--m74pIvgg-WOHQOCmU/edit
https://docs.google.com/document/d/1O3t-OccxDFkxUveRA8I4-QS0hp6Ybel0ZcN8wzDUlNY/edit
OWNERS
| Role | Contact |
|---|---|
| PM | TBD |
| Documentation Owner | TBD |
| Delivery Owner | (See assignee) |
| Quality Engineer | (See QA contact) |
NOTES
There are some potential issues that need to be sorted out.
- Kubernetes scheduling needs to be aware of increased memory requirements of a pod.
- We need a consistent API to follow for hotplug in general
Goals:
- Additional memory could be added from admin console
- Additional memory could be added from CLI console
- In the case adding memory is failing a proper error message with the reason/next steps should be populated to the user
Link to some background info for oVirt: https://ovirt.org/develop/release-management/features/virt/hot-plug-memory.html
DONE CHECKLIST
| Who | What | Reference |
|---|---|---|
| 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 | gap doc updated | Virtualization K3 |
| QE | Test plans in Polarion | Polarion link |
| QE | Automated tests merged | Gerrit PR |
| DOC | Downstream documentation merged | <link to meaningful PR> |
- blocks
-
-
- Stakeholder Acceptance
-
- is blocked by
-
-
- To Do
-
-
OCPSTRAT-225 Enhancement to VPA : In-Place Update of Pod Resources
-
- Refinement
-
- is depended on by
-
-
- Backlog
-