Jump to: navigation, search

Mellanox-Neutron-Kilo-Redhat-InfiniBand

Revision as of 13:11, 9 July 2015 by Lenny Verkhovsky (talk | contribs) (→‎Network Node)

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.

Prerequisites

 yum-config-manager --add-repo  http://www.mellanox.com/repository/solutions/openstack/kilo/

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


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 = mlnx, (linuxbridgе|openvswitch)
[ml2_type_vlan]
network_vlan_ranges = <network_name>:2:100

4. Start (or restart) the Neutron server: 

#systemctl restart  neutron-server.service

Compute Nodes

To configure the Compute Node:

1.Configure yum with Mellanox OpenStack Juno repository yum repo http://www.mellanox.com/repository/solutions/openstack/juno/rhel7

2. Install Mellanox RPMs: 

#yum install -y 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: TODO upload to ftp and change instructions 

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

# /bin/systemctl stop  opensm.service
# /etc/init.d/openibd restart

9. 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_mapping = default:ib<your_interface>

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

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

12. Restart Nova: 

 #systemctl restart openstack-nova-compute

13. Start eSwitchd: 

 #systemctl restart eswitchd

14. Start the Neutron agent: 

#systemctl restart neutron-mlnx-agent

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>

if you are using openvswitch than modify /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini 

[ovs]
integration_bridge = ib0
bridge_mappings = default:ib0

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: 

#systemctl restart neutron-linuxbridge-agent.service
#systemctl restart neutron-openvswitch-agent.service

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)

1. Install the Mellanox Dnsmasq: 

#yum install -y  mlnx-dnsmasq

3. Modify /etc/neutron/dhcp_agent.ini as follows: 

dhcp_driver = mlnx_dhcp.MlnxDnsmasq
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver/neutron.agent.linux.interface.OVSInterfaceDriver

4. Start DHCP server: 

#service neutron-dhcp-agent restart

Known issues and Troubleshooting

For known issues and troubleshooting options refer to Mellanox OpenStack Troubleshooting

Retrieved from "https://wiki.openstack.org/w/index.php?title=Mellanox-Neutron-Kilo-Redhat-InfiniBand&oldid=85529"