-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
virtctl-cluster-cpu
-
77
-
-
To Do
-
CNV-11088 - Heterogenuous clusters
Goal
An admin today has the ability to set a default CPU model on the cluster via
https://docs.openshift.com/container-platform/4.15/virt/virtual_machines/advanced_vm_management/virt-configuring-default-cpu-model.html
The goal of this epic is to enable the admin to understand 2 things:
1. What CPU models are available on the cluster at what quantity, in order to make a quantity based decision ("what cpus do I have most")
2. What are the most recent CPUs in order to make a qualitative decision ("what is the best cpu") (stretched, only if libvirt is providing this by now)
User Stories
- "As a cluster administrator,
I Want to run `virtctl cluster cpus` in order to see all CPUs and their quantity,
so that I can then set one of them as the default on the cluster level." - "As a cluster administrator,
I Want to run `virtctl cluster cpus --make-default THE_MODEL`
so that I can set the CPU model THE_MODEL as the default on the cluster level (virtctl patches kubevirtcr)
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
1.
|
upstream roadmap issue | New | Unassigned | ||
2.
|
upstream design | New | Unassigned | ||
3.
|
upstream documentation | New | Unassigned | ||
4.
|
upgrade consideration | New | Unassigned | ||
5.
|
CEE/PX summary presentation | New | Unassigned | ||
6.
|
test plans in polarion | New | Unassigned | ||
7.
|
automated tests | New | Unassigned | ||
8.
|
downstream documentation merged | New | Unassigned |