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

documentation changes for labeling nodes & providing node selectors to schedule

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • CNV v4.21.0, 4.21
    • CNV Documentation
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Yes
    • None

      Add a note or paragraph to section 5.2.1 (https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/virtualization/postinstallation-configuration#virt-node-placement-virt-components in 4.20) and/or 8.1.2 (https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/virtualization/advanced-vm-creation#virt-golden-image-heterogeneous-clusters) in both versions 4.20 and 4.21  specific to IBM System Z, along the lines of:

       

      In the case that you are running a cluster with mixed System Z hypervisors (LPAR, z/VM, zKVM) the supported nodes to run virtual machines are as follows:

       

      Node Architecture Hypervisor VM deployment Supported? Node selection VM architecture supported
      s390x LPAR YES set node selector for LPAR node s390x
      s390x z/VM NO or set anti-affinity for z/VM node N/A
      s390x zKVM NO or set anti-affinity for zKVM node N/A

      The scheduler will not at this time select LPAR over z/VM or KVM nodes on s390x by default. In order to have a supported s390x virtual machine, you must set at least one s390x LPAR node as a schedulable worker node, and you must set the node selector for it before deploying the virtual machine. 

              sniemann@redhat.com Silke Niemann
              cfilleke@redhat.com Cheryl Fillekes
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: