Revision as of 09:15, 29 June 2015

Overview

Mellanox Neutron ML2 Driver

Mellanox ML2 Mechanism Driver implements the ML2 Plugin Mechanism Driver API.

This driver supports Mellanox embedded switch functionality as part of the VPI (Ethernet/InfiniBand) HCA. Mellanox ML2 Mechanism Driver provides functional parity with Mellanox Neutron plugin.

Mellanox ML2 Mechanism Driver supports DIRECT (pci passthrough) and MACVTAP (virtual interface with a tap-like software interface) vnic types. For vnic type configuration API details, please refer to configuration reference guide (click here). Hardware vNICs mapped to the guest VMs allow higher performance and advanced features such as RDMA (remote direct memory access).

The driver supports VLAN network type to facilitate virtual networks either on Ethernet or InfiniBand fabrics.

• Mellanox OpenStack Neutron Agent (L2 Agent) runs on each compute node.
• Agent should apply VIF connectivity based on mapping between a VIF (VM vNIC) and Embedded Switch port.

Mellanox Neutron Plugin

For details regarding Mellanox Neutron plugin, please refer to https://wiki.openstack.org/wiki/Mellanox-Neutron-Havana-Redhat.

Mellanox Nova VIF Driver

The Mellanox Nova VIF driver should be used when running Mellanox Mechnism Driver. The VIF driver supports the VIF plugin by binding vNIC of type DIRECT to the embedded switch port. VIF Driver for MACVTAP type is included in Nova libvirt generic vif driver. For SR-IOV pass-through (vnic type DIRECT) one needs to use VIF driver from Mellanox git repository or RPM.

Prerequisites

• A running OpenStack environment installed with the ML2 plugin on top of Linux Bridge.
• All nodes equipped with Mellanox ConnectX®-3 Network Adapter (http://www.mellanox.com/page/products_dyn?product_family=119)
• Mellanox OFED 2.4 or greater installed on all nodes. Please refer to Mellanox website for the latest OFED: http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers
• SR-IOV enabled on all compute nodes. For more information, please refer to Mellanox Community click here.
• The software package iproute2 - (http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 ) installed on all Compute nodes

InfiniBand Network

The Mellanox Neutron Plugin use InfiniBand Partitions (PKeys) to separate Networks.

SM Node

OpenSM Configuration – Without UFM

To configure OpenSM:

• Make sure that all the PKeys are predefined in the partitions.conf file (/etc/opensm/partitions.conf).
• Add/Change the following in the partitions.conf file:

management=0xffff,ipoib, sl=0, defmember=full: ALL, ALL_SWITCHES=full,SELF=full;

• For every network you want to configure in Neutron, you have to configure the PKey associated with the VLAN of this network (defined in Neutron):

vlan1=0x1, ipoib, sl=0, defmember=full : ALL;

Below is an example of the configuration of the partitions.conf file in case you have 10 VLANs defined in the configuration of the file: /etc/neutron/plugins/mlnx/mlnx_conf.ini. ( network_vlan_ranges = default:1:10)

management=0x7fff,ipoib, sl=0, defmember=full : ALL, ALL_SWITCHES=full,SELF=full;
vlan1=0x1, ipoib, sl=0, defmember=full: ALL_CAS;
vlan2=0x2, ipoib, sl=0, defmember=full: ALL_CAS;
vlan3=0x3, ipoib, sl=0, defmember=full: ALL_CAS;
vlan4=0x4, ipoib, sl=0, defmember=full: ALL_CAS;
vlan5=0x5, ipoib, sl=0, defmember=full: ALL_CAS;
vlan6=0x6, ipoib, sl=0, defmember=full: ALL_CAS;
vlan7=0x7, ipoib, sl=0, defmember=full: ALL_CAS;
vlan8=0x8, ipoib, sl=0, defmember=full: ALL_CAS;
vlan9=0x9, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0xa, ipoib, sl=0, defmember=full: ALL_CAS;

4. Modify the following line in the file /etc/opensm/opensm.conf from FALSE to TRUE:

allow_both_pkeys TRUE

5. Restart the OpenSM:

#service opensmd restart

2.2 Neutron Server Node To configure the Neutron Server node: 1. Make sure ML2 is the current Neutron plugin by checking the core_plugin parameter in /etc/neutron/neutron.conf: core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin 2. Make sure /etc/neutron/plugin.ini is pointing to /etc/neutron/plugins/ml2/ml2_conf.ini (symbolic link) 3. Modify /etc/neutron/plugins/ml2/ml2_conf.ini by adding the following: [ml2] type_drivers = vlan,flat tenant_network_types = vlan mechanism_drivers = linuxbridge,mlnx [ml2_type_vlan] network_vlan_ranges = <network_name>:2:100 [eswitch] vnic_type = hostdev apply_profile_patch = True 4. Start (or restart) the Neutron server:

1. service neutron-server restart

2.3 Compute Nodes To configure the Compute Node: 1. Download Mellanox OpenStack repo file (Juno.zip) 2. Install the eSwitch Daemon (eSwitchd) RPM:

1. yum install eswitchd

3. Install the required RPM for the Neutron agent:

1. yum install openstack-neutron-mellanox

Edit the following file: /usr/lib/systemd/system/neutron-mlnx-agent.service Change the --config file to this path: --config-file /etc/neutron/plugins/mlnx/mlnx_conf.ini 4. Run: #systemctl enable neutron-mlnx-agent.service 5. Run: #systemctl daemon-reload 6. Copy the file vif_driver_workaround.patch and Run:

1. patch < vif_driver_workaround.patch #You’ll need to give the right python path

7.Create the file /etc/modprobe.d/mlx4_ib.conf and add the following: options mlx4_ib sm_guid_assign=0 8. Restart the driver:

1. service openibd restart

9.In the file /etc/neutron/plugins/mlnx/mlnx_conf.ini, the parameters tenant_network_type , vnic_type and network_vlan_ranges should be configured as the controllers:

physical_interface_mapping = default:ib<your_interface>

10. Modify the file /etc/eswitchd/eswitchd.conf as follows: fabrics = default:ib<your_interface> (for example default:ib0) 11. Verify Mellanox VIF driver is configured in /etc/nova/nova.conf: [libvirt] vif_driver=mlnxvif.vif.MlxEthVIFDriver 12. Restart Nova:

1. service openstack-nova-compute restart

13. Start eSwitchd:

1. service eswitchd start

14. Start the Neutron agent:

1. service neutron-mlnx-agent start

2.4 Network Node To configure the Network node: 1. Make sure that eIPoIB module is up and configured in /etc/infiniband/openib.conf: For more information, please refer to eIPoIB configuration in Mellanox OFED User Manual. E_IPOIB_LOAD=yes 2. Restart openibd:

1. service openibd restart

3. Modify the file /etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini as follows: [linux_bridge] physical_interface_mappings = default:<eIPoIB interface> NOTE: In order to obtain the eIPoIB interface name, run the ethtool tool command (see below) and check the driver name:

1. ethtool -i <eIPoIB_interface>

driver: eth_ipoib version: 1.0.0 firmware-version: 1 bus-info: ib0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no 4. Restart neutron-linuxbridge-agent and neutron-dhcp-agent:

1. service neutron-linuxbridge-agent restart

NOTE: For DHCP support, the Network node should use the Mellanox Dnsmasq driver as the DHCP driver. 2.4.1 DHCP Server (Usally part of the Network node) 1. Install the Mellanox Dnsmasq:

1. yum localinstall mlnx-dnsmasq-2014.2.1-1.noarch.rpm

3. Modify /etc/neutron/dhcp_agent.ini as follows: dhcp_driver = mlnx_dhcp.MlnxDnsmasq interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver 4. Start DHCP server:

1. service neutron-dhcp-agent restart

3 Known issues and Troubleshooting For known issues and troubleshooting options refer to Mellanox OpenStack Troubleshooting