Difference between revisions of "Mellanox-vif-driver"
(Created page with "== Introduction == Hardware Based Virtual NICs (SR-IOV) can be achieved in via the following ways: * Direct Interface (Para-virtualized) * PCI Device (hostdev). == Direct In...") |
(→Physical network) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
− | Hardware Based Virtual NICs (SR-IOV) can be achieved in | + | Hardware Based Virtual NICs (SR-IOV) can be achieved in the following ways |
* Direct Interface (Para-virtualized) | * Direct Interface (Para-virtualized) | ||
− | * PCI Device (hostdev). | + | * PCI Device (hostdev). |
== Direct Interface == | == Direct Interface == | ||
− | + | Assigning vNIC via Direct Interface is achieved by using libvirt direct interface.<br /> | |
− | The device name | + | The direct interface device name assigned a logical name that is derived from the VIF UUID (neutron port ID). <br /> |
− | The VIF Driver is using vnic_type = 'direct' and using the Eswitch control utility to plug/unplug the | + | This allows support for VM live migration.<br /> |
+ | The VIF Driver is using vnic_type = 'direct' and using the Eswitch control utility to plug/unplug the VIF<br /> | ||
== Physical network == | == Physical network == | ||
− | In order to | + | In order to support number of physical connections of the compute node to different physical networks, physical network identification should be propagated to the VIF Driver together with vnic_type and virtual network attributes. <br /> |
+ | Physical_network is propagated to the VIF driver from Neutron v2 API response on port creation/update. | ||
== PCI Device(hostdev) == | == PCI Device(hostdev) == |
Latest revision as of 19:39, 1 July 2013
Introduction
Hardware Based Virtual NICs (SR-IOV) can be achieved in the following ways
- Direct Interface (Para-virtualized)
- PCI Device (hostdev).
Direct Interface
Assigning vNIC via Direct Interface is achieved by using libvirt direct interface.
The direct interface device name assigned a logical name that is derived from the VIF UUID (neutron port ID).
This allows support for VM live migration.
The VIF Driver is using vnic_type = 'direct' and using the Eswitch control utility to plug/unplug the VIF
Physical network
In order to support number of physical connections of the compute node to different physical networks, physical network identification should be propagated to the VIF Driver together with vnic_type and virtual network attributes.
Physical_network is propagated to the VIF driver from Neutron v2 API response on port creation/update.
PCI Device(hostdev)
See Roadmap
Roadmap
First phase is to support Ethernet Direct Interface.
Next phases will include hostdev support and Infiniband support.