Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-42906

virtctl for cluster level CPU informations

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • virtctl-cluster-cpu
    • 77
    • Hide
      Show
      tier1 only, no tier2 no ui/ux (dedicated epic for this) client tool for allowing an admin to understand what cpu model can be selected as the default client tool for allowing an admin to understand the best cpu model to be selected as the default `virtctl cluster cpus` docuentation update to https://docs.openshift.com/container-platform/4.15/virt/virtual_machines/advanced_vm_management/virt-configuring-default-cpu-model.html
    • 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 Sub-task New Normal Unassigned
        2.
        upstream design Sub-task New Normal Unassigned
        3.
        upstream documentation Sub-task New Normal Unassigned
        4.
        upgrade consideration Sub-task New Normal Unassigned
        5.
        CEE/PX summary presentation Sub-task New Normal Unassigned
        6.
        test plans in polarion Sub-task New Normal Unassigned
        7.
        automated tests Sub-task New Normal Unassigned
        8.
        downstream documentation merged Sub-task New Normal Unassigned

            Unassigned Unassigned
            fdeutsch@redhat.com Fabian Deutsch
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: