Latest revision as of 09:51, 1 January 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

Please note, Mellanox Plug-in is deprecated in the Icehouse release and won't be supported in the Juno release. The features in the plug-in are now part of the ML2 plug-in in the form of Mellanox mechanism driver.

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.2 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
• VLANs configured on the ports in the switch.

InfiniBand Network

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

SM Node

OpenSM Configuration – Without UFM

 To configure OpenSM:

1. Make sure that all the PKeys are predefined in the partitions.conf file (/etc/opensm/partitions.conf).

2. Add/Change the following in the partitions.conf file:

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

3. 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

OpenSM configuration - With UFM

To configure OpenSM:

1. Make sure that UFM is installed and connected to your fabric.

2. Edit /opt/ufm/conf/opensm/opensm.conf by changing the following values:

a. Set allow_both_pkeys to TRUE (by default allow_both_pkeys are FALSE):

Allow both full and limited membership on the same partition
allow_both_pkeys TRUE

b. Set sm_assign_guid_func to uniq_count (by default sm_assign_guid_func is base_port):

SM assigned Alias GUIDs algorithm sm_assign_guid_func uniq_count

3. Edit UFM user extension partitions.conf for overriding default partitioning configuration.

a. Edit file: /opt/ufm/conf/partitions.conf.user_ext (it should be empty right after UFM installation) Add the following line to the file to enable both full and limited management PKeys:

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

b. Add the additional PKey definitions relevant to the specific setup. For Example:

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;
vlan10=0xb, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0xc, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0xd, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0xe, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0xf, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0x10, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0x11, ipoib, sl=0, defmember=full: ALL_CAS;
vlan10=0x12, ipoib, sl=0, defmember=full: ALL_CAS;

4. Restart UFM

• Stand-alone

#/etc/init.d/ufmd restart

• High-availability

#/etc/init.d/ufmha restart

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:

#service neutron-server restart

Compute Nodes

To configure the Compute Node:

1. Download Mellanox OpenStack repo file:

#wget http://www.mellanox.com/downloads/solutions/openstack/icehouse/repo/mlnx-icehouse/mlnx-icehouse.repo -O /etc/yum.repos.d/mlnx-icehouse.repo  

2. Install the eSwitch Daemon (eSwitchd) RPM:

#yum install eswitchd

3. Install Mellanox VIF driver:

#yum install mlnxvif

3. Install the required RPM for the Neutron agent:

#yum install openstack-neutron-mellanox

4. Create the file /etc/modprobe.d/mlx4_ib.conf and add the following:

options mlx4_ib sm_guid_assign=0

5. Restart the driver:

#service openibd restart

6.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>

7. Modify the file /etc/eswitchd/eswitchd.conf as follows:

fabrics = default:ib<your_interface> (for example default:ib0)

8. Verify Mellanox VIF driver is configured in /etc/nova/nova.conf:

[libvirt]
vif_driver=mlnxvif.vif.MlxEthVIFDriver

9. Restart Nova:

#service openstack-nova-compute restart

10. Start eSwitchd:

#service eswitchd start

11. Start the Neutron agent:

#service neutron-mlnx-agent start

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:

#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:

#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:

#service neutron-linuxbridge-agent restart

NOTE: For DHCP support, the Network node should use the Mellanox Dnsmasq driver as the DHCP driver.

DHCP Server (Usally part of the Network node)

1. Install the Mellanox Dnsmasq:

#wget 
http://www.mellanox.com/downloads/solutions/openstack/icehouse/repo/mlnx-icehouse/mlnx-dnsmasq-2014.1.1-1.noarch.rpm
#yum localinstall mlnx-dnsmasq-2014.1.1-1.noarch.rpm 

2. In addition, Dnsmasq must be upgraded to version 2.66 or higher:

 #wget 
ftp://ftp.pbone.net/mirror/ftp5.gwdg.de/pub/opensuse/repositories/home:/kalyaka/CentOS_CentOS-6/x86_64/dnsmasq-2.66-3.1.x86_64.rpm

#yum localinstall dnsmasq-2.66-3.1.x86_64.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:

#service neutron-dhcp-agent restart

Known issues and Troubleshooting

For known issues and troubleshooting options refer to Mellanox OpenStack Troubleshooting.

References

1. http://www.mellanox.com/openstack/

2. Source repository

3. Mellanox OFED

4. Mellanox OpenStack Solution Reference Architecture

5. Mellanox OpenStack Troubleshooting

For more details, please refer your question to openstack@mellanox.com

Return to Mellanox-OpenStack wiki page.