yahoo-eng-team team mailing list archive

[OpenStack Infra <1829734@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/658784
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=47390226f5c755a083b0f181f7a81b480069c8a9
Submitter: Zuul
Branch:    master

commit 47390226f5c755a083b0f181f7a81b480069c8a9
Author: Hamdy Khader <hamdyk@xxxxxxxxxxxx>
Date:   Mon May 13 13:39:57 2019 +0300

    OVS DPDK port representors support
    
    Adds support for OVS DPDK port representors[1], a direct port on
    a netdev datapath is considered a DPDK representor port.
    
    get_vif_type returns OVS VIF type in case of a direct port.
    
    [1] http://docs.openvswitch.org/en/latest/topics/dpdk/phy/#representors
    
    Closes-Bug: #1829734
    Change-Id: I3956eeda19ebc93fdb0b13c1cfb3dc64abffee9f


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1829734

Title:
  [RFE] OVS DPDK port representors support

Status in neutron:
  Fix Released

Bug description:
  DPDK representors enable configuring a phy port to a guest (VM)
  machine.

  OVS resides in the hypervisor which has one or more physical
  interfaces also known as the physical functions (PFs). If a PF
  supports SR-IOV it can be used to enable communication with the VMs
  via Virtual Functions (VFs). The VFs are virtual PCIe devices created
  from the physical Ethernet controller.

  DPDK models a physical interface as a rte device on top of which an
  eth device is created. DPDK (version 18.xx) introduced the
  representors eth devices. A representor device represents the VF eth
  device (VM side) on the hypervisor side and operates on top of a PF.
  Representors are multi devices created on top of one PF.

  The goal is to enable having dpdk port attached to instance as a
  direct port when the hypervisor datapath type is netdev.

  
  Changes needed:

  * Neutron:
  return OVS VIF type in case of a direct port and a netdev databath.

  * Nova:
  In case of a port's OVS VIF type and a direct VNIC type, the datapath info must be set in the VIF profile as the VIF object is instantiated from VIFHostDevice class with profile of type VIFPortProfileOVSRepresentor.

  * os-vif: 
  Do the plugging using the DPDK Representors syntax[1] in case of VIFHostDevice and a netdev databath.


  [1] http://docs.openvswitch.org/en/latest/topics/dpdk/phy/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1829734/+subscriptions