Difference between revisions of "Mellanox-Neutron-Kilo-Redhat-Ethernet"
| Line 1: | Line 1: | ||
| − | = SR-IOV | + | =Ethernet Configuration with Mellanox= |
| − | = SDN Mechanism Driver = | + | ==SR-IOV Networking in OpenStack Juno/Kilo== |
| − | = Ceilometer = | + | OpenStack Juno adds 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 | ||
| + | |||
| + | ==SDN Mechanism Driver== | ||
| + | ==Ceilometer== | ||
Revision as of 13:40, 21 July 2015
Contents
Ethernet Configuration with Mellanox
SR-IOV Networking in OpenStack Juno/Kilo
OpenStack Juno adds 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
