Jump to: navigation, search

Difference between revisions of "Mellanox-Neutron-Ocata-Ubuntu-InfiniBand"

(Created page with "=Overview= ==Mellanox Neutron ML2 Driver== Mellanox ML2 Mechanism Driver implements the ML2 Plugin Mechanism Driver API. This driver supports Mellanox embedded switch func...")
Line 92: Line 92:
* Install Mellanox RPMs:  
* Install Mellanox RPMs:  
  # apt-get install -y openstack-neutron-mellanox python-networking-mlnx
  # apt-get install -y python-networking-mlnx
Line 175: Line 175:
*  Install Mellanox RPMs:  
*  Install Mellanox RPMs:  
  # apt-get install -y openstack-neutron-mellanox eswitchd mlnx-python-networking-mlnx python-ethtool python-zmq  
  # apt-get install -y mlnx-python-networking-mlnx python-ethtool python-zmq  

Revision as of 11:28, 29 November 2017


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 InfiniBand HCA. Mellanox ML2 Mechanism Driver provides functional parity with Mellanox Neutron plugin.

Mellanox ML2 Mechanism Driver supports DIRECT (pci passthrough) vnic type. For vnic type configuration API details, please refer to configuration reference guide. 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 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.


  • A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge.
  • All nodes equipped with Mellanox ConnectX®-3/ConnectX®-3Pro Network Adapter
  • Mellanox OFED 2.4 or greater installed on all nodes.
  • SR-IOV enabled on all compute nodes.
  • iproute2 installed on all Compute nodes

InfiniBand Network

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

SM Node

OpenSM Provisioning with SDN Mechanism Driver

SDN Mechanism Driver allows OpenSM dynamically assign PKs in the IB network.

More details about applying SDN Mechanism Driver with NEO can be found here

Manual OpenSM Configuration

All the PKeys should be predefined in the partitions.conf file (/etc/opensm/partitions.conf) (Automatic cofiguration is planned in future phase)

For ConnectX®-3/ConnectX®-3Pro use the following configuration

Add/Change the following in the partitions.conf file

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

Change the following in /etc/opensm/opensm.conf:

  allow_both_pkeys TRUE

For ConnectX®-4 use the following configuration

Add/Change the following in the partitions.conf.user_ext

vlan1=0x1, ipoib, sl=0, defmember=full: ALL_CAS;
#Storage and management vlan should be define as follow
vlan2=0x2, ipoib, sl=0, defmember=full: ALL_CAS;
vlan3=0x3, ipoib, sl=0, defmember=full: ALL_CAS;
#define OpenSM as a member for all OpenStack vlans. If not guest will have link down on “ibdev2netdev” and no connectivity.
vlan4=0x4, ipoib, sl=0, defmember=full: SELF;
vlan5=0x5, ipoib, sl=0, defmember=full: SELF;
vlan6=0x6, ipoib, sl=0, defmember=full: SELF;
vlan7=0x7, ipoib, sl=0, defmember=full: SELF;
vlan8=0x8, ipoib, sl=0, defmember=full: SELF;
vlan9=0x9, ipoib, sl=0, defmember=full: SELF;
vlan10=0xa, ipoib, sl=0, defmember=full: SELF;

Change the following in /etc/opensm/opensm.conf:

virt_enabled 2
no_partition_enforcement TRUE
part_enforce off
allow_both_pkeys FALSE

5. Restart the OpenSM:

# service opensmd restart

Controller Node

To configure the Controller node:

  • Configure Debian OpenStack ocata repository

sudo add-apt-repository cloud-archive:ocata sudo apt-get update

  • Install prerequisites
# apt-get install -y python-ethtool python-zmq
  • Install Mellanox RPMs:
# apt-get install -y python-networking-mlnx

  • Run:
# service enable neutron-mlnx-agent networking-mlnx-eswitchd.service
# service daemon-reload
  • 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
  • Make sure /etc/neutron/plugin.ini is pointing to /etc/neutron/plugins/ml2/ml2_conf.ini (symbolic link)
  • Modify /etc/neutron/plugins/ml2/ml2_conf.ini by adding the following:
type_drivers = vlan,flat
tenant_network_types = vlan
# OVS Configuration
mechanism_drivers = mlnx_infiniband, openvswitch
# LinuxBridge Configuration
mechanism_drivers = mlnx_infiniband, linuxbridge
network_vlan_ranges = default:1:10

  • Start (or restart) the Neutron server:
# service neutron-server restart

Network Node

To configure the Network node:


E_IPoIB port is configured and up
  • 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.
  • Restart openibd:
# service openibd restart
  • Modify the network bridge configuration according to the use of OpenVswitch or LinuxBridge
    • OpenVswitch /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
bridge_mappings = default:br-<eIPoIB interface>
    • LinuxBridge file /etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini:
physical_interface_mappings = default:<eIPoIB interface>

NOTE: In order to obtain the eIPoIB interface name, run the ethtool tool command and check that driver name is eth_ipoib:

# ethtool -i <eIPoIB_interface> 
driver: eth_ipoib
  • Restart network bridge and neutron-dhcp-agent:
# service neutron-dhcp-agent restart
    • OpenVswitch
# service neutron-linuxbridge-agent restart
    • LinuxBridge
# service neutron-openvswitch-agent restart

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

DHCP Server (Usually part of the Network node)

  • Modify /etc/neutron/dhcp_agent.ini as follows and according to OVS or Linuxbridge:
dhcp_driver = mlnx_dhcp.MlnxDnsmasq
dhcp_broadcast_reply = True
# or interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
  • Start DHCP server:
# service neutron-dhcp-agent restart

Compute Nodes

To configure the Compute Node:

  • Configure Mellanox OpenStack ocata repository
  1. sudo add-apt-repository http://www.mellanox.com/repository/solutions/openstack/ocata/ubuntu

  • Install Mellanox RPMs:
# apt-get install -y  mlnx-python-networking-mlnx python-ethtool python-zmq 

  • Edit the following file: /usr/lib/systemd/system/neutron-mlnx-agent.service

Change the /etc/neutron/plugins/mlnx/mlnx.ini to /etc/neutron/plugins/mlnx/mlnx_conf.ini

  • Run:
# service neutron-mlnx-agent start
  • Run:
# service daemon-reload start
  • Create the file /etc/modprobe.d/mlx4_ib.conf and add the following:
# options mlx4_ib sm_guid_assign=0
  • Restart Nova:
# service openstack-nova-compute restart 
  • Restart the driver:
# service opensmd restart
# /etc/init.d/openibd restart
  • In the file /etc/neutron/plugins/mlnx/mlnx_conf.ini, the parameters tenant_network_type , and network_vlan_ranges should be configured as the controllers:
physical_interface_mappings = default:<ib_interface>(for example default:ib0)
  • Modify the file /etc/eswitchd/eswitchd.conf as follows:
fabrics = default:<ib_interface> (for example default:ib0)
  • Start eSwitchd:
# service eswitchd restart
  • Start the Neutron agent:
# service neutron-mlnx-agent restart

Known issues and Troubleshooting

For known issues and troubleshooting options refer to Mellanox OpenStack Troubleshooting