yahoo-eng-team team mailing list archive

[Hamdy Khader <1829734@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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/

** Affects: neutron
     Importance: Undecided
     Assignee: Hamdy Khader (hamdyk)
         Status: In Progress

** Affects: nova
     Importance: Undecided
     Assignee: Hamdy Khader (hamdyk)
         Status: In Progress

** Affects: os-vif
     Importance: Undecided
     Assignee: Hamdy Khader (hamdyk)
         Status: In Progress

** Also affects: neutron
   Importance: Undecided
       Status: New

** Also affects: os-vif
   Importance: Undecided
       Status: New

** Changed in: nova
     Assignee: (unassigned) => Hamdy Khader (hamdyk)

** Changed in: os-vif
     Assignee: (unassigned) => Hamdy Khader (hamdyk)

** Changed in: neutron
     Assignee: (unassigned) => Hamdy Khader (hamdyk)

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

Title:
  [RFE] OVS DPDK port representors support

Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in os-vif:
  In Progress

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