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

Topology aware VM scheduling

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • CNV Infrastructure
    • None
    • topology-scheduling-for-vms
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • VIRTSTRAT-227 - NUMA aware scheduling
    • VIRTSTRAT-227NUMA aware scheduling

      Goal

      CNF has added a topology aware scheduler. This epic is about understanding if VMs can be scheduled with this scheduler and closing potential gaps.

      CNF work https://docs.openshift.com/container-platform/4.11/scalability_and_performance/cnf-numa-aware-scheduling.html

      User Stories

      • As a VM owner,
        I want have my VM scheduled with awareness tot opolgoy
        so that it will land on a node according to the requested topology
      • another user story

      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

      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>

              dholler@redhat.com Dominik Holler
              fdeutsch@redhat.com Fabian Deutsch
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: