Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-256

As an operator i would like to be able to leverage multiqueue with VDPA devices for networking

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • openstack-nova
    • None
    • Multi-queue support for vDPA
    • False
    • Hide

      This RFE is blocked on documenation form the VIRT teams on how to configure multiqueue end to end with vdpa.

      specifically we need a domain XML example for how to use multi quel vdpa with libvirt.
      the minimum versions of libvirt and qemu that support this feature.
      how to discover the vdpa device queue count via the noddev API (this might need a new libvirt feature to report that)

      we also are blocked on how to statically configured the nvida connectx-6 dx/lx to create VFs with multiple queues and create a multi queue vdpa device statically.

      Show
      This RFE is blocked on documenation form the VIRT teams on how to configure multiqueue end to end with vdpa. specifically we need a domain XML example for how to use multi quel vdpa with libvirt. the minimum versions of libvirt and qemu that support this feature. how to discover the vdpa device queue count via the noddev API (this might need a new libvirt feature to report that) we also are blocked on how to statically configured the nvida connectx-6 dx/lx to create VFs with multiple queues and create a multi queue vdpa device statically.
    • False
    • Proposed
    • Proposed
    • To Do
    • Proposed
    • Proposed

      To enable vdpa with multi queue tehre are many aspect that need to be assets.

      (1) Report the device queue to the db so that it can later be used for scheduling

      (2) Ensure that the libvirt driver can properly configure multi-queue. the generic code might work but it may need to be adapted to clamp the number of core to min(flavor.cpus, device. queues)

      (3) Request the number of queues for each device ideally as metadata on the port passed from neutron this may or may not require a neutron change but it could be a new QOS type or similar extension we would then need to modify the scheduler/pci claim code and or placement modeling to accommodate the new resource.

      (4) Work to track VF and VDPA devices in placement is being done by the community this cycle. while we could do the queue aware scheduling on the nova side eventually it should be modeled in placement somehow, so there would be follow on work to enable that

              Unassigned Unassigned
              smooney@redhat.com Sean Mooney
              rhos-workloads-compute
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: