Jump to: navigation, search

Difference between revisions of "Mellanox-Neutron-Juno-Ethernet"

(Created page with "=Ethernet Configuration with Mellanox= =SR-IOV Networking in OpenStack Juno= OpenStack Juno added inbox support to request VM access to virtual network via SR-IOV NIC. With t...")
 
m (Ethernet Configuration with Mellanox)
Line 1: Line 1:
=Ethernet Configuration with Mellanox=
 
 
=SR-IOV Networking in OpenStack Juno=  
 
=SR-IOV Networking in OpenStack Juno=  
 
OpenStack Juno added inbox support to request VM access to virtual network via SR-IOV NIC. With the introduction of SR-IOV based NICs, the traditional virtual bridge is no longer required. Each SR-IOV port is associated with a virtual function (VF). SR-IOV ports may be provided by Hardware-based Virtual Ethernet Bridging (HW VEB); or they may be extended to an upstream physical switch (IEEE 802.1br).
 
OpenStack Juno added inbox support to request VM access to virtual network via SR-IOV NIC. With the introduction of SR-IOV based NICs, the traditional virtual bridge is no longer required. Each SR-IOV port is associated with a virtual function (VF). SR-IOV ports may be provided by Hardware-based Virtual Ethernet Bridging (HW VEB); or they may be extended to an upstream physical switch (IEEE 802.1br).

Revision as of 14:27, 31 October 2016

SR-IOV Networking in OpenStack Juno

OpenStack Juno added inbox support to request VM access to virtual network via SR-IOV NIC. With the introduction of SR-IOV based NICs, the traditional virtual bridge is no longer required. Each SR-IOV port is associated with a virtual function (VF). SR-IOV ports may be provided by Hardware-based Virtual Ethernet Bridging (HW VEB); or they may be extended to an upstream physical switch (IEEE 802.1br). There are two ways that SR-IOV port may be connected:

  • directly connected to its VF
  • connected with a macvtap device that resides on the host, which is then connected to the corresponding VF

Configuration

Configure SR-IOV