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

As an end user i would like to be able to use different hw_vif_model per neutron port

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None
    • per port vif model
    • False
    • Hide

      None

      Show
      None
    • False
    • OSPRH-120Compute Engineering Backlog
    • Proposed
    • Proposed
    • To Do
    • OSPRH-120 - Compute Engineering Backlog
    • Proposed
    • Proposed
    • Compute

      https://etherpad.opendev.org/p/r.6ad6a4b8c378756c66185a7b35f1bcf9#L388

      as discussed in the ptg this may be possible by reusing the neutron port taging feature which is separate form the nova port tagging feature.

      we may need the tag extension to be amended to allow key value tags.
      this would require a neutron spec to detail this api change.

      the nova team need to review the apis shared by the neutron team
      to understand if the port hints extension (admin only?)
      https://review.opendev.org/c/openstack/neutron/+/870081/12/neutron/api/definitions/port_hints.py

      This feature would likely be required to enable generic vdpa.

      https://review.opendev.org/c/openstack/nova-specs/+/879338/6/specs/2023.2/approved/generic-vdpa-support.rst

      as with OSPRH-49 the precidence relationship between hw_vir_model on the port and in the image is as follows

      if hw_vif_model is set on the port then that will be used
      if now we will fallback to the image porperty
      if that is not set we fallback to libosinfo
      and finally we fallback to the virt dirver default (virtio-net)

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

              Created:
              Updated: