Difference between revisions of "Mellanox-Neutron-Kilo-Redhat-Ethernet"
(→SR-IOV Networking in OpenStack Kilo) |
(→SDN Mechanism Driver) |
||
| Line 10: | Line 10: | ||
==SDN Mechanism Driver== | ==SDN Mechanism Driver== | ||
| − | [https://community.mellanox.com/docs/DOC-2155 | + | [https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically configure VLANs on the network. |
| + | |||
| + | More details about applying SDN Mechanism Driver with [http://www.mellanox.com/page/products_dyn?product_family=220&mtag=mellanox_neo NEO] can be found [https://community.mellanox.com/docs/DOC-2251 here] | ||
==Ceilometer== | ==Ceilometer== | ||
Revision as of 15:05, 21 July 2015
Contents
Ethernet Configuration with Mellanox
SR-IOV Networking in OpenStack Kilo
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
SDN Mechanism Driver
SDN Mechanism Driver allows OpenSM dynamically configure VLANs on the network.
More details about applying SDN Mechanism Driver with NEO can be found here
