-
Epic
-
Resolution: Obsolete
-
Critical
-
None
-
None
-
ga-live-affinity-change
-
False
-
-
False
-
- node affinity can be updated when a VM is running
- after a change to node affinity a live migration is triggered in order to put this change into effect
-
To Do
-
-
0% To Do, 0% In Progress, 100% Done
-
---
-
---
Goal
Change VM affinity rules without disturbing VM workload
User Stories
- As an owner of an important running VM, I would like to tweak its affinity rules so that it no longer runs next to a chatty class of workload. I want to do it without disturbing VM workload;
I expect this VM (or the other chatty VM I want to avoid) would be migrated away from each other. - As an owner of important running VMs, I asked my cluster-admin to taint a few nodes just for them. I would like to add the corresponding toleration to my VMs so they may migrate to the tainted nodes when need arises.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- This epic may serve as a helper in cases such as Sahibinden's, when a customer to trigger live migration to a specific set of nodes.
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
| DEV | Upstream documentation merged | <link to meaningful PR> |
| DEV | gap doc updated | <name sheet and cell> |
| DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
| DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
| 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> |
