OpenStack - User contributions [en]

Mellanox-Neutron-Rocky-Ubuntu-InfiniBand

2019-02-17T11:41:16Z

Hasanq:

=Overview=

==Mellanox Neutron ML2 Driver==

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

This driver supports Mellanaox 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.

===Prerequisites===
* A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge.
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] 2.4 or greater
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] 3.1-1.5.7 or greater.
* [https://community.mellanox.com/docs/DOC-1317 SR-IOV ]enabled on all compute nodes.
* [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] installed on all Compute nodes
* [http://www.mellanox.com/page/products_dyn?product_family=100 Mellanox UFM] greater than 5.9.5

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

==SM Node==

=== OpenSM Provisioning with SDN Mechanism Driver ===

[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically assign PKs in the IB 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]

=== 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 rocky repository
sudo add-apt-repository cloud-archive:rocky
sudo apt-get update

* Install prerequisites
# apt-get install -y python-ethtool python-zmq

* Install Mellanox RPMs:
# apt-get install -y openstack-neutron-mellanox 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:
[ml2]
type_drivers = vlan,flat
tenant_network_types = vlan

# OVS Configuration
mechanism_drivers = mlnx_infiniband, openvswitch
# LinuxBridge Configuration
mechanism_drivers = mlnx_infiniband, linuxbridge

[ml2_type_vlan]
network_vlan_ranges = default:1:10

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

== Network Node==
To configure the Network node:

Prerequisites:
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.
E_IPOIB_LOAD=yes

* 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'''
[ovs]
bridge_mappings = default:br-<eIPoIB interface>
** LinuxBridge file '''/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini''':
[linux_bridge]
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
# sudo add-apt-repository http://www.mellanox.com/repository/solutions/openstack/ocata/ubuntu

* Install Mellanox RPMs:
# apt-get install -y openstack-neutron-mellanox eswitchd 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 [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

Mellanox-Neutron-Queens-Ubuntu-InfiniBand

2019-02-17T11:40:17Z

Hasanq:

=Overview=

==Mellanox Neutron ML2 Driver==

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

This driver supports Mellanaox 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.

===Prerequisites===
* A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge.
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] 2.4 or greater
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] 3.1-1.5.7 or greater.
* [https://community.mellanox.com/docs/DOC-1317 SR-IOV ]enabled on all compute nodes.
* [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] installed on all Compute nodes
* [http://www.mellanox.com/page/products_dyn?product_family=100 Mellanox UFM] greater than 5.9.5

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

==SM Node==

=== OpenSM Provisioning with SDN Mechanism Driver ===

[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically assign PKs in the IB 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]

=== 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 queens repository
sudo add-apt-repository cloud-archive:queens
sudo apt-get update

* Install prerequisites
# apt-get install -y python-ethtool python-zmq

* Install Mellanox RPMs:
# apt-get install -y openstack-neutron-mellanox 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:
[ml2]
type_drivers = vlan,flat
tenant_network_types = vlan

# OVS Configuration
mechanism_drivers = mlnx_infiniband, openvswitch
# LinuxBridge Configuration
mechanism_drivers = mlnx_infiniband, linuxbridge

[ml2_type_vlan]
network_vlan_ranges = default:1:10

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

== Network Node==
To configure the Network node:

Prerequisites:
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.
E_IPOIB_LOAD=yes

* 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'''
[ovs]
bridge_mappings = default:br-<eIPoIB interface>
** LinuxBridge file '''/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini''':
[linux_bridge]
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
# sudo add-apt-repository http://www.mellanox.com/repository/solutions/openstack/ocata/ubuntu

* Install Mellanox RPMs:
# apt-get install -y openstack-neutron-mellanox eswitchd 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 [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

Mellanox-Neutron

2019-01-27T13:25:57Z

Hasanq: /* Mellanox Neutron Plugin */

= Mellanox Neutron Plugin =
Mellanox supports the OpenStack Neutron releases with open source networking components. It delivers higher compute and storage performance and additional functionality, such as NIC based switching to provide better security and isolation for virtual cloud environments.

* [[Mellanox-Neutron-ML2-Rocky|Mellanox-Rocky]]
* [[Mellanox-Neutron-ML2-Queens|Mellanox-Queens]]
* [[Mellanox-Neutron-ML2-Pike|Mellanox-Pike]]
* [[Mellanox-Neutron-ML2-Ocata|Mellanox-Ocata]]
* [[Mellanox-Neutron-ML2-Newton|Mellanox-Newton]]
* [[Mellanox-Neutron-ML2-Mitaka|Mellanox-Mitaka]]
* [[Mellanox-Neutron-ML2-Liberty|Mellanox-Liberty]]
* [[Mellanox-Neutron-ML2-Kilo|Mellanox-Kilo]]
* [[Mellanox-Neutron-ML2-Juno|Mellanox-Juno]]
* [[Mellanox-Neutron-ML2-Icehouse|Mellanox-Icehouse]]
* [[Mellanox-Neutron-Havana-Ubuntu|Mellanox-Havana-Ubuntu]] / [[Mellanox-Neutron-Havana-Redhat|Mellanox-Havana-RedHat]]
* [[Mellanox-Neutron-Grizzly|Mellanox-Grizzly]]
 
* [[Mellanox-packages-versioning|Mellanox packages versions]]
 

= References =
1. [http://www.mellanox.com/openstack/ OpenStack solution page at Mellanox site]

2. [https://github.com/openstack/networking-mlnx Mellanox ML2 driver and associated tools source repository]

3. [https://github.com/mellanox-openstack Old/previous Mellanox source repository]

4. [http://www.mellanox.com/page/products_dyn?product_family=26 Mellanox OFED web page]

5. [http://community.mellanox.com/community/develop/cloud-developers Mellanox Cloud Developers Community]

For more details, please refer your question to [mailto:openstack@mellanox.com openstack@mellanox.com]

[[Category: Neutron]]

Mellanox-Neutron-ML2-Rocky

2018-11-25T13:39:58Z

Hasanq: Created page with "Mellanox ML2 Mechanism Driver implements the ML2 Plugin Mechanism Driver API. This driver supports Mellanox embedded switch functionality as part of the VPI (Ethernet/Infini..."

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

'''Prerequisites'''
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] 2.4 or greater
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] 3.1-1.5.7 or greater.

For '''Rocky''' release Information refer to the relevant OS as follows:

Infiniband
* [[Mellanox-Neutron-Rocky-Redhat-InfiniBand | Redhat7]]
* [[Mellanox-Neutron-Rocky-Ubuntu-InfiniBand | Ubuntu16.04]]
 
Ethernet(SR-IOV)
* [[Mellanox-Neutron-Rocky-Ethernet |Redhat7|Ubuntu]]

Mellanox-Neutron-Rocky-Ubuntu-InfiniBand

2018-11-25T13:34:32Z

Hasanq: 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 fun..."

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

===Prerequisites===
* Red Hat Installation > 7.1
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] the latest 3.X
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] the latest 3.X .
* A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge (RDO Manager or Packstack).
* [https://community.mellanox.com/docs/DOC-1317 SR-IOV] enabled on all compute nodes.
* The software package [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] installed on all Compute nodes
* [http://www.mellanox.com/page/products_dyn?product_family=100 Mellanox UFM] greater than 5.9.5
* Add the following repositories on each node
yum -y install yum-plugin-priorities
cd /etc/yum.repos.d/
sudo wget https://trunk.rdoproject.org/centos7-rocky/current/delorean.repo
yum update -y

=InfiniBand Network=
The Mellanox Neutron Plugin uses InfiniBand Partitions (PKeys) to separate Networks.

==SM Node==

=== OpenSM Provisioning with SDN Mechanism Driver ===

[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically assign PKs in the IB 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]

=== 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/ConnectX®-5 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
part_enforce off
allow_both_pkeys FALSE

4. Restart the OpenSM:
# systemctl restart opensmd.service

==Controller Node==

To configure the Controller node:

1. Install Mellanox RPMs:
# yum install -y --nogpgcheck python-networking-mlnx

===Neutron Server===
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_infiniband, openvswitch
# or mechanism_drivers = mlnx_infiniband, linuxbridge
[ml2_type_vlan]
network_vlan_ranges = default:1:10

4. Start (or restart) the Neutron server:
# systemctl restart neutron-server.service

===Nova Scheduler===
Enabling PciPassthroughFilter modify /etc/nova/nova.conf
scheduler_available_filters = nova.scheduler.filters.all_filters
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, PciPassthroughFilter

== Network Node==
To configure the Network node:

Prerequisites:
E_IPoIB port is configured and up

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 network bridge configuration according to the use of OpenVswitch or LinuxBridge
* 3.1 OpenVswitch '''/etc/neutron/plugins/ml2/openvswitch_agent.ini'''
[ovs]
bridge_mappings = default:br-<eIPoIB interface>
* 3.2 LinuxBridge file '''/etc/neutron/plugins/ml2/linuxbridge_agent.ini''':
[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 that driver name is eth_ipoib:
# ethtool -i <eIPoIB_interface>
driver: eth_ipoib
.....

4. Restart network bridge:
* 4.1 OpenVswitch
systemctl restart neutron-openvswitch-agent.service
* 4.2 LinuxBridge (if using linux bridge)
# service neutron-linuxbridge-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)===

1. Modify '''/etc/neutron/dhcp_agent.ini''' as follows and according to OVS or Linuxbridge:
dhcp_driver = networking_mlnx.dhcp.mlnx_dhcp.MlnxDnsmasq
dhcp_broadcast_reply = True

1.1 For OVS
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
1.2 For Linux Bridge
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver

2. Restart DHCP server:
# systemctl restart neutron-dhcp-agent.service

==Compute Nodes==

To configure the Compute Node:

1. Install Mellanox RPMs:
# yum install --nogpgcheck -y python-networking-mlnx

2. Create the file '''/etc/modprobe.d/mlx4_ib.conf''' and add the following:
options mlx4_ib sm_guid_assign=0

3. Restart the driver:
# /etc/init.d/openibd restart

===Nova Compute===
Nova-compute needs to know which PCI devices are allowed to be passed through to the VMs.
Also for SRIOV PCI devices it needs to know to which physical network the VF belongs.
This is done through the pci_passthrough_whitelist parameter under the default section in '''/etc/nova/nova.conf'''.
For example if we want to whitelist and tag the VFs by their PCI address we would use the following setting:
[pci]
passthrough_whitelist = {"address":"*:0a:00.*","physical_network":"default"}
This associates any VF with address that includes ':0a:00.' in its address to the physical network default.

1. add pci passthrough_whitelist to '''/etc/nova/nova.conf'''

2. Restart Nova:
# systemctl restart openstack-nova-compute

===Neutron MLNX Agent===
1. Run:
# systemctl enable neutron-mlnx-agent.service
# systemctl start neutron-mlnx-agent.service

2. Run:
# systemctl daemon-reload

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

4. Modify the file '''/etc/neutron/plugins/ml2/eswitchd.conf''' as follows:
fabrics = default:<ib_interface> (for example default:ib0)

5. Start eSwitchd:
# systemctl enable eswitchd.service
# systemctl start eswitchd.service

6. Start the Neutron agent:
# systemctl restart neutron-mlnx-agent

==Known issues and Troubleshooting==
For known issues and troubleshooting options refer to [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

Issue: Missing zmq package on all nodes (Controller/Compute)
Solution:
<pre>
# wget https://bootstrap.pypa.io/get-pip.py
# sudo python get-pip.py
# sudo pip install pyzmq
</pre>

Mellanox-Neutron-Rocky-Redhat-InfiniBand

2018-11-25T13:33:31Z

Mellanox-Neutron-Rocky-InfiniBand

2018-11-25T13:31:33Z

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 a 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 [https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking#VM_creation_flow_with_SR-IOV_vNIC configuration reference guide].
Hardware vNICs mapped to the guest VMs allow higher performance and advanced features such as Remote Direct Memory Access (RDMA).

The driver supports VLAN network type to facilitate virtual networks either on Ethernet or 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 an embedded switch port.

'''Prerequisites'''
* Mellanox ConnectX®-3/Mellanox ConnectX®-3 PRO [http://www.mellanox.com/page/products_dyn?product_family=119 Network Adapter] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED 2.4 or greater]
* Mellanox ConnectX®-4 [http://www.mellanox.com/page/products_dyn?product_family=201& Network Adapter] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX-3.1-1.5.7 or greater].

For '''Rocky''' release Information refer to the relevant OS as follows:

* [[Mellanox-Neutron-Rocky-Redhat-InfiniBand | Redhat7]]
* [[Mellanox-Neutron-Rocky-Ubuntu-InfiniBand | Ubuntu14.04]]

Mellanox-Neutron-Rocky-Ethernet

2018-11-25T13:29:58Z

Hasanq: Created page with " Search BoldItalicLinkEmbedded fileReferenceAdvancedSpecial charactersHelp ==Configuration== [https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking Configure SR-..."

Search
BoldItalicLinkEmbedded fileReferenceAdvancedSpecial charactersHelp

==Configuration==
[https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking Configure SR-IOV]

==SDN Mechanism Driver==
[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows NEO to dynamically configure VLANs on the Mellanox Switches.
Further reading:
* [http://www.mellanox.com/page/products_dyn?product_family=220&mtag=mellanox_neo NEO]
* [http://www.mellanox.com/page/ethernet_switch_overview Mellanox Switches]
* [https://community.mellanox.com/docs/DOC-2251 SDN Mechanism Driver]

==Ceilometer==
The Mellanox Ceilometer SR-IOV module allows the OpenStack Ceilometer to collect measurements of SR-IOV counters.

More details about applying Mellanox Ceilometer module can be found [https://community.mellanox.com/docs/DOC-2145 here]

Summary:
This is a minor edit Watch this page
Please note that all contributions to OpenStack are considered to be released under the Attribution 3.0 Unported (CC BY 3.0) (see OpenStack:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel
Privacy policy About OpenStack Disclaimers
Attribution 3.0 Unported (CC BY 3.0) Powered by MediaWiki

Mellanox-Neutron-Queens-InfiniBand

2018-11-25T13:27:47Z

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 a 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 [https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking#VM_creation_flow_with_SR-IOV_vNIC configuration reference guide].
Hardware vNICs mapped to the guest VMs allow higher performance and advanced features such as Remote Direct Memory Access (RDMA).

The driver supports VLAN network type to facilitate virtual networks either on Ethernet or 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 an embedded switch port.

'''Prerequisites'''
* Mellanox ConnectX®-3/Mellanox ConnectX®-3 PRO [http://www.mellanox.com/page/products_dyn?product_family=119 Network Adapter] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED 2.4 or greater]
* Mellanox ConnectX®-4 [http://www.mellanox.com/page/products_dyn?product_family=201& Network Adapter] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX-3.1-1.5.7 or greater].

For '''Queens''' release Information refer to the relevant OS as follows:

* [[Mellanox-Neutron-Queens-Redhat-InfiniBand | Redhat7]]
* [[Mellanox-Neutron-Queens-Ubuntu-InfiniBand | Ubuntu14.04]]

Mellanox-Neutron-Queens-Redhat-InfiniBand

2018-07-16T12:22:45Z

Hasanq:

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

===Prerequisites===
* Red Hat Installation > 7.1
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] the latest 3.X
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] the latest 3.X .
* A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge (RDO Manager or Packstack).
* [https://community.mellanox.com/docs/DOC-1317 SR-IOV] enabled on all compute nodes.
* The software package [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] installed on all Compute nodes
* [http://www.mellanox.com/page/products_dyn?product_family=100 Mellanox UFM] greater than 5.9.5
* Add the following repositories on each node
yum -y install yum-plugin-priorities
cd /etc/yum.repos.d/
sudo wget https://trunk.rdoproject.org/centos7-queens/current/delorean.repo
yum update -y

=InfiniBand Network=
The Mellanox Neutron Plugin uses InfiniBand Partitions (PKeys) to separate Networks.

==SM Node==

=== OpenSM Provisioning with SDN Mechanism Driver ===

[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically assign PKs in the IB 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]

=== 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/ConnectX®-5 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
part_enforce off
allow_both_pkeys FALSE

4. Restart the OpenSM:
# systemctl restart opensmd.service

==Controller Node==

To configure the Controller node:

1. Install Mellanox RPMs:
# yum install -y --nogpgcheck python-networking-mlnx

===Neutron Server===
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_infiniband, openvswitch
# or mechanism_drivers = mlnx_infiniband, linuxbridge
[ml2_type_vlan]
network_vlan_ranges = default:1:10

4. Start (or restart) the Neutron server:
# systemctl restart neutron-server.service

===Nova Scheduler===
Enabling PciPassthroughFilter modify /etc/nova/nova.conf
scheduler_available_filters = nova.scheduler.filters.all_filters
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, PciPassthroughFilter

== Network Node==
To configure the Network node:

Prerequisites:
E_IPoIB port is configured and up

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 network bridge configuration according to the use of OpenVswitch or LinuxBridge
* 3.1 OpenVswitch '''/etc/neutron/plugins/ml2/openvswitch_agent.ini'''
[ovs]
bridge_mappings = default:br-<eIPoIB interface>
* 3.2 LinuxBridge file '''/etc/neutron/plugins/ml2/linuxbridge_agent.ini''':
[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 that driver name is eth_ipoib:
# ethtool -i <eIPoIB_interface>
driver: eth_ipoib
.....

4. Restart network bridge:
* 4.1 OpenVswitch
systemctl restart neutron-openvswitch-agent.service
* 4.2 LinuxBridge (if using linux bridge)
# service neutron-linuxbridge-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)===

1. Modify '''/etc/neutron/dhcp_agent.ini''' as follows and according to OVS or Linuxbridge:
dhcp_driver = networking_mlnx.dhcp.mlnx_dhcp.MlnxDnsmasq
dhcp_broadcast_reply = True

1.1 For OVS
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
1.2 For Linux Bridge
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver

2. Restart DHCP server:
# systemctl restart neutron-dhcp-agent.service

==Compute Nodes==

To configure the Compute Node:

1. Install Mellanox RPMs:
# yum install --nogpgcheck -y python-networking-mlnx

2. Create the file '''/etc/modprobe.d/mlx4_ib.conf''' and add the following:
options mlx4_ib sm_guid_assign=0

3. Restart the driver:
# /etc/init.d/openibd restart

===Nova Compute===
Nova-compute needs to know which PCI devices are allowed to be passed through to the VMs.
Also for SRIOV PCI devices it needs to know to which physical network the VF belongs.
This is done through the pci_passthrough_whitelist parameter under the default section in '''/etc/nova/nova.conf'''.
For example if we want to whitelist and tag the VFs by their PCI address we would use the following setting:
[pci]
passthrough_whitelist = {"address":"*:0a:00.*","physical_network":"default"}
This associates any VF with address that includes ':0a:00.' in its address to the physical network default.

1. add pci passthrough_whitelist to '''/etc/nova/nova.conf'''

2. Restart Nova:
# systemctl restart openstack-nova-compute

===Neutron MLNX Agent===
1. Run:
# systemctl enable neutron-mlnx-agent.service
# systemctl start neutron-mlnx-agent.service

2. Run:
# systemctl daemon-reload

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

4. Modify the file '''/etc/neutron/plugins/ml2/eswitchd.conf''' as follows:
fabrics = default:<ib_interface> (for example default:ib0)

5. Start eSwitchd:
# systemctl enable eswitchd.service
# systemctl start eswitchd.service

6. Start the Neutron agent:
# systemctl restart neutron-mlnx-agent

==Known issues and Troubleshooting==
For known issues and troubleshooting options refer to [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

Issue: Missing zmq package on all nodes (Controller/Compute)
Solution:
<pre>
# wget https://bootstrap.pypa.io/get-pip.py
# sudo python get-pip.py
# sudo pip install pyzmq
</pre>

Mellanox-Neutron-Queens-Ubuntu-InfiniBand

2018-07-16T12:20:55Z

Hasanq:

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

===Prerequisites===
* Red Hat Installation > 7.1
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] the latest 3.X
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] the latest 3.X .
* A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge (RDO Manager or Packstack).
* [https://community.mellanox.com/docs/DOC-1317 SR-IOV] enabled on all compute nodes.
* The software package [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] installed on all Compute nodes
* [http://www.mellanox.com/page/products_dyn?product_family=100 Mellanox UFM] greater than 5.9.5
* Add the following repositories on each node
yum -y install yum-plugin-priorities
cd /etc/yum.repos.d/
sudo wget https://trunk.rdoproject.org/centos7-queens/current/delorean.repo
yum update -y

=InfiniBand Network=
The Mellanox Neutron Plugin uses InfiniBand Partitions (PKeys) to separate Networks.

==SM Node==

=== OpenSM Provisioning with SDN Mechanism Driver ===

[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically assign PKs in the IB 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]

=== 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/ConnectX®-5 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
part_enforce off
allow_both_pkeys FALSE

4. Restart the OpenSM:
# systemctl restart opensmd.service

==Controller Node==

To configure the Controller node:

1. Install Mellanox RPMs:
# yum install -y --nogpgcheck python-networking-mlnx

===Neutron Server===
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_infiniband, openvswitch
# or mechanism_drivers = mlnx_infiniband, linuxbridge
[ml2_type_vlan]
network_vlan_ranges = default:1:10

4. Start (or restart) the Neutron server:
# systemctl restart neutron-server.service

===Nova Scheduler===
Enabling PciPassthroughFilter modify /etc/nova/nova.conf
scheduler_available_filters = nova.scheduler.filters.all_filters
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, PciPassthroughFilter

== Network Node==
To configure the Network node:

Prerequisites:
E_IPoIB port is configured and up

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 network bridge configuration according to the use of OpenVswitch or LinuxBridge
* 3.1 OpenVswitch '''/etc/neutron/plugins/ml2/openvswitch_agent.ini'''
[ovs]
bridge_mappings = default:br-<eIPoIB interface>
* 3.2 LinuxBridge file '''/etc/neutron/plugins/ml2/linuxbridge_agent.ini''':
[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 that driver name is eth_ipoib:
# ethtool -i <eIPoIB_interface>
driver: eth_ipoib
.....

4. Restart network bridge:
* 4.1 OpenVswitch
systemctl restart neutron-openvswitch-agent.service
* 4.2 LinuxBridge (if using linux bridge)
# service neutron-linuxbridge-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)===

1. Modify '''/etc/neutron/dhcp_agent.ini''' as follows and according to OVS or Linuxbridge:
dhcp_driver = networking_mlnx.dhcp.mlnx_dhcp.MlnxDnsmasq
dhcp_broadcast_reply = True

1.1 For OVS
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
1.2 For Linux Bridge
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver

2. Restart DHCP server:
# systemctl restart neutron-dhcp-agent.service

==Compute Nodes==

To configure the Compute Node:

1. Install Mellanox RPMs:
# yum install --nogpgcheck -y python-networking-mlnx

2. Create the file '''/etc/modprobe.d/mlx4_ib.conf''' and add the following:
options mlx4_ib sm_guid_assign=0

3. Restart the driver:
# /etc/init.d/openibd restart

===Nova Compute===
Nova-compute needs to know which PCI devices are allowed to be passed through to the VMs.
Also for SRIOV PCI devices it needs to know to which physical network the VF belongs.
This is done through the pci_passthrough_whitelist parameter under the default section in '''/etc/nova/nova.conf'''.
For example if we want to whitelist and tag the VFs by their PCI address we would use the following setting:
[pci]
passthrough_whitelist = {"address":"*:0a:00.*","physical_network":"default"}
This associates any VF with address that includes ':0a:00.' in its address to the physical network default.

1. add pci passthrough_whitelist to '''/etc/nova/nova.conf'''

2. Restart Nova:
# systemctl restart openstack-nova-compute

===Neutron MLNX Agent===
1. Run:
# systemctl enable neutron-mlnx-agent.service
# systemctl start neutron-mlnx-agent.service

2. Run:
# systemctl daemon-reload

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

4. Modify the file '''/etc/neutron/plugins/ml2/eswitchd.conf''' as follows:
fabrics = default:<ib_interface> (for example default:ib0)

5. Start eSwitchd:
# systemctl enable eswitchd.service
# systemctl start eswitchd.service

6. Start the Neutron agent:
# systemctl restart neutron-mlnx-agent

==Known issues and Troubleshooting==
For known issues and troubleshooting options refer to [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

Issue: Missing zmq package on all nodes (Controller/Compute)
Solution:
<pre>
# wget https://bootstrap.pypa.io/get-pip.py
# sudo python get-pip.py
# sudo pip install pyzmq
</pre>

Mellanox-Neutron-ML2-Queens

2018-07-15T13:59:43Z

Hasanq:

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

'''Prerequisites'''
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] 2.4 or greater
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] 3.1-1.5.7 or greater.

For '''Queens''' release Information refer to the relevant OS as follows:

Infiniband
* [[Mellanox-Neutron-Queens-Redhat-InfiniBand | Redhat7]]
* [[Mellanox-Neutron-Queens-Ubuntu-InfiniBand | Ubuntu16.04]]
 
Ethernet(SR-IOV)
* [[Mellanox-Neutron-Queens-Ethernet |Redhat7|Ubuntu]]

Mellanox-Neutron-Queens-Redhat-InfiniBand

2018-07-15T13:57:09Z

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

===Prerequisites===
* Red Hat Installation > 7.1
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] the latest 3.X
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] the latest 3.X .
* A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge (RDO Manager or Packstack).
* [https://community.mellanox.com/docs/DOC-1317 SR-IOV] enabled on all compute nodes.
* The software package [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] installed on all Compute nodes
* [http://www.mellanox.com/page/products_dyn?product_family=100 Mellanox UFM] greater than 5.9.5
* Add the following repositories on each node
yum -y install yum-plugin-priorities
cd /etc/yum.repos.d/
sudo wget https://trunk.rdoproject.org/centos7-pike/current/delorean.repo
yum update -y

=InfiniBand Network=
The Mellanox Neutron Plugin uses InfiniBand Partitions (PKeys) to separate Networks.

==SM Node==

=== OpenSM Provisioning with SDN Mechanism Driver ===

[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically assign PKs in the IB 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]

=== 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
part_enforce off
allow_both_pkeys FALSE

4. Restart the OpenSM:
# systemctl restart opensmd.service

==Controller Node==

To configure the Controller node:

1. Install Mellanox RPMs:
# yum install -y --nogpgcheck python-networking-mlnx

===Neutron Server===
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_infiniband, openvswitch
# or mechanism_drivers = mlnx_infiniband, linuxbridge
[ml2_type_vlan]
network_vlan_ranges = default:1:10

4. Start (or restart) the Neutron server:
# systemctl restart neutron-server.service

===Nova Scheduler===
Enabling PciPassthroughFilter modify /etc/nova/nova.conf
scheduler_available_filters = nova.scheduler.filters.all_filters
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, PciPassthroughFilter

== Network Node==
To configure the Network node:

Prerequisites:
E_IPoIB port is configured and up

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 network bridge configuration according to the use of OpenVswitch or LinuxBridge
* 3.1 OpenVswitch '''/etc/neutron/plugins/ml2/openvswitch_agent.ini'''
[ovs]
bridge_mappings = default:br-<eIPoIB interface>
* 3.2 LinuxBridge file '''/etc/neutron/plugins/ml2/linuxbridge_agent.ini''':
[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 that driver name is eth_ipoib:
# ethtool -i <eIPoIB_interface>
driver: eth_ipoib
.....

4. Restart network bridge:
* 4.1 OpenVswitch
systemctl restart neutron-openvswitch-agent.service
* 4.2 LinuxBridge (if using linux bridge)
# service neutron-linuxbridge-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)===

1. Modify '''/etc/neutron/dhcp_agent.ini''' as follows and according to OVS or Linuxbridge:
dhcp_driver = networking_mlnx.dhcp.mlnx_dhcp.MlnxDnsmasq
dhcp_broadcast_reply = True

1.1 For OVS
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
1.2 For Linux Bridge
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver

2. Restart DHCP server:
# systemctl restart neutron-dhcp-agent.service

==Compute Nodes==

To configure the Compute Node:

1. Install Mellanox RPMs:
# yum install --nogpgcheck -y python-networking-mlnx

2. Create the file '''/etc/modprobe.d/mlx4_ib.conf''' and add the following:
options mlx4_ib sm_guid_assign=0

3. Restart the driver:
# /etc/init.d/openibd restart

===Nova Compute===
Nova-compute needs to know which PCI devices are allowed to be passed through to the VMs.
Also for SRIOV PCI devices it needs to know to which physical network the VF belongs.
This is done through the pci_passthrough_whitelist parameter under the default section in '''/etc/nova/nova.conf'''.
For example if we want to whitelist and tag the VFs by their PCI address we would use the following setting:
[pci]
passthrough_whitelist = {"address":"*:0a:00.*","physical_network":"default"}
This associates any VF with address that includes ':0a:00.' in its address to the physical network default.

1. add pci passthrough_whitelist to '''/etc/nova/nova.conf'''

2. Restart Nova:
# systemctl restart openstack-nova-compute

===Neutron MLNX Agent===
1. Run:
# systemctl enable neutron-mlnx-agent.service
# systemctl start neutron-mlnx-agent.service

2. Run:
# systemctl daemon-reload

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

4. Modify the file '''/etc/neutron/plugins/ml2/eswitchd.conf''' as follows:
fabrics = default:<ib_interface> (for example default:ib0)

5. Start eSwitchd:
# systemctl enable eswitchd.service
# systemctl start eswitchd.service

6. Start the Neutron agent:
# systemctl restart neutron-mlnx-agent

==Known issues and Troubleshooting==
For known issues and troubleshooting options refer to [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

Issue: Missing zmq package on all nodes (Controller/Compute)
Solution:
<pre>
# wget https://bootstrap.pypa.io/get-pip.py
# sudo python get-pip.py
# sudo pip install pyzmq
</pre>

Mellanox-Neutron-Queens-Ubuntu-InfiniBand

2018-07-15T13:53:46Z

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

===Prerequisites===
* Red Hat Installation > 7.1
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] the latest 3.X
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] the latest 3.X .
* A running OpenStack environment installed with the ML2 plugin on top of OpenVswitch or Linux Bridge (RDO Manager or Packstack).
* [https://community.mellanox.com/docs/DOC-1317 SR-IOV] enabled on all compute nodes.
* The software package [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] installed on all Compute nodes
* [http://www.mellanox.com/page/products_dyn?product_family=100 Mellanox UFM] greater than 5.9.5
* Add the following repositories on each node
yum -y install yum-plugin-priorities
cd /etc/yum.repos.d/
sudo wget https://trunk.rdoproject.org/centos7-pike/current/delorean.repo
yum update -y

=InfiniBand Network=
The Mellanox Neutron Plugin uses InfiniBand Partitions (PKeys) to separate Networks.

==SM Node==

=== OpenSM Provisioning with SDN Mechanism Driver ===

[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows OpenSM dynamically assign PKs in the IB 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]

=== 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
part_enforce off
allow_both_pkeys FALSE

4. Restart the OpenSM:
# systemctl restart opensmd.service

==Controller Node==

To configure the Controller node:

1. Install Mellanox RPMs:
# yum install -y --nogpgcheck python-networking-mlnx

===Neutron Server===
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_infiniband, openvswitch
# or mechanism_drivers = mlnx_infiniband, linuxbridge
[ml2_type_vlan]
network_vlan_ranges = default:1:10

4. Start (or restart) the Neutron server:
# systemctl restart neutron-server.service

===Nova Scheduler===
Enabling PciPassthroughFilter modify /etc/nova/nova.conf
scheduler_available_filters = nova.scheduler.filters.all_filters
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, PciPassthroughFilter

== Network Node==
To configure the Network node:

Prerequisites:
E_IPoIB port is configured and up

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 network bridge configuration according to the use of OpenVswitch or LinuxBridge
* 3.1 OpenVswitch '''/etc/neutron/plugins/ml2/openvswitch_agent.ini'''
[ovs]
bridge_mappings = default:br-<eIPoIB interface>
* 3.2 LinuxBridge file '''/etc/neutron/plugins/ml2/linuxbridge_agent.ini''':
[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 that driver name is eth_ipoib:
# ethtool -i <eIPoIB_interface>
driver: eth_ipoib
.....

4. Restart network bridge:
* 4.1 OpenVswitch
systemctl restart neutron-openvswitch-agent.service
* 4.2 LinuxBridge (if using linux bridge)
# service neutron-linuxbridge-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)===

1. Modify '''/etc/neutron/dhcp_agent.ini''' as follows and according to OVS or Linuxbridge:
dhcp_driver = networking_mlnx.dhcp.mlnx_dhcp.MlnxDnsmasq
dhcp_broadcast_reply = True

1.1 For OVS
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
1.2 For Linux Bridge
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver

2. Restart DHCP server:
# systemctl restart neutron-dhcp-agent.service

==Compute Nodes==

To configure the Compute Node:

1. Install Mellanox RPMs:
# yum install --nogpgcheck -y python-networking-mlnx

2. Create the file '''/etc/modprobe.d/mlx4_ib.conf''' and add the following:
options mlx4_ib sm_guid_assign=0

3. Restart the driver:
# /etc/init.d/openibd restart

===Nova Compute===
Nova-compute needs to know which PCI devices are allowed to be passed through to the VMs.
Also for SRIOV PCI devices it needs to know to which physical network the VF belongs.
This is done through the pci_passthrough_whitelist parameter under the default section in '''/etc/nova/nova.conf'''.
For example if we want to whitelist and tag the VFs by their PCI address we would use the following setting:
[pci]
passthrough_whitelist = {"address":"*:0a:00.*","physical_network":"default"}
This associates any VF with address that includes ':0a:00.' in its address to the physical network default.

1. add pci passthrough_whitelist to '''/etc/nova/nova.conf'''

2. Restart Nova:
# systemctl restart openstack-nova-compute

===Neutron MLNX Agent===
1. Run:
# systemctl enable neutron-mlnx-agent.service
# systemctl start neutron-mlnx-agent.service

2. Run:
# systemctl daemon-reload

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

4. Modify the file '''/etc/neutron/plugins/ml2/eswitchd.conf''' as follows:
fabrics = default:<ib_interface> (for example default:ib0)

5. Start eSwitchd:
# systemctl enable eswitchd.service
# systemctl start eswitchd.service

6. Start the Neutron agent:
# systemctl restart neutron-mlnx-agent

==Known issues and Troubleshooting==
For known issues and troubleshooting options refer to [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

Issue: Missing zmq package on all nodes (Controller/Compute)
Solution:
<pre>
# wget https://bootstrap.pypa.io/get-pip.py
# sudo python get-pip.py
# sudo pip install pyzmq
</pre>

Mellanox-Neutron-ML2-Queens

2018-07-15T13:51:23Z

Hasanq:

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

'''Prerequisites'''
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] 2.4 or greater
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] 3.1-1.5.7 or greater.

For '''Queens''' release Information refer to the relevant OS as follows:

Infiniband
* [[Mellanox-Neutron-Queens-Redhat-InfiniBand | Redhat7]]
* [[Mellanox-Neutron-Queens-Ubuntu-InfiniBand | Ubuntu16.04]]
 
Ethernet(SR-IOV)
* [[Mellanox-Neutron-Queens-Ethernet |Redhat7|Ubuntu]]

Mellanox-Neutron-Queens-Ethernet

2018-07-15T13:47:58Z

Hasanq:

==Configuration==
[https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking Configure SR-IOV]

==SDN Mechanism Driver==
[https://community.mellanox.com/docs/DOC-2155 SDN Mechanism Driver] allows NEO to dynamically configure VLANs on the Mellanox Switches.
Further reading:
* [http://www.mellanox.com/page/products_dyn?product_family=220&mtag=mellanox_neo NEO]
* [http://www.mellanox.com/page/ethernet_switch_overview Mellanox Switches]
* [https://community.mellanox.com/docs/DOC-2251 SDN Mechanism Driver]

==Ceilometer==
The Mellanox Ceilometer SR-IOV module allows the OpenStack Ceilometer to collect measurements of SR-IOV counters.

More details about applying Mellanox Ceilometer module can be found [https://community.mellanox.com/docs/DOC-2145 here]

Mellanox-Neutron-Queens-Ethernet

2018-07-15T13:47:25Z

Hasanq: Created page with "==Configuration== [https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking Configure SR-IOV]"

==Configuration==
[https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking Configure SR-IOV]

Mellanox-Neutron-ML2-Queens

2018-07-15T13:32:06Z

Hasanq:

Mellanox-Neutron

2018-07-15T13:30:55Z

Hasanq: /* Mellanox Neutron Plugin */

= Mellanox Neutron Plugin =
Mellanox supports the OpenStack Neutron releases with open source networking components. It delivers higher compute and storage performance and additional functionality, such as NIC based switching to provide better security and isolation for virtual cloud environments.

* [[Mellanox-Neutron-ML2-Queens|Mellanox-Queens]]
* [[Mellanox-Neutron-ML2-Pike|Mellanox-Pike]]
* [[Mellanox-Neutron-ML2-Ocata|Mellanox-Ocata]]
* [[Mellanox-Neutron-ML2-Newton|Mellanox-Newton]]
* [[Mellanox-Neutron-ML2-Mitaka|Mellanox-Mitaka]]
* [[Mellanox-Neutron-ML2-Liberty|Mellanox-Liberty]]
* [[Mellanox-Neutron-ML2-Kilo|Mellanox-Kilo]]
* [[Mellanox-Neutron-ML2-Juno|Mellanox-Juno]]
* [[Mellanox-Neutron-ML2-Icehouse|Mellanox-Icehouse]]
* [[Mellanox-Neutron-Havana-Ubuntu|Mellanox-Havana-Ubuntu]] / [[Mellanox-Neutron-Havana-Redhat|Mellanox-Havana-RedHat]]
* [[Mellanox-Neutron-Grizzly|Mellanox-Grizzly]]
 
* [[Mellanox-packages-versioning|Mellanox packages versions]]
 

= References =
1. [http://www.mellanox.com/openstack/ OpenStack solution page at Mellanox site]

2. [https://github.com/openstack/networking-mlnx Mellanox ML2 driver and associated tools source repository]

3. [https://github.com/mellanox-openstack Old/previous Mellanox source repository]

4. [http://www.mellanox.com/page/products_dyn?product_family=26 Mellanox OFED web page]

5. [http://community.mellanox.com/community/develop/cloud-developers Mellanox Cloud Developers Community]

For more details, please refer your question to [mailto:openstack@mellanox.com openstack@mellanox.com]

[[Category: Neutron]]

Mellanox-Neutron

2018-07-15T13:30:01Z

Hasanq: /* Mellanox Neutron Plugin */

= Mellanox Neutron Plugin =
Mellanox supports the OpenStack Neutron releases with open source networking components. It delivers higher compute and storage performance and additional functionality, such as NIC based switching to provide better security and isolation for virtual cloud environments.

For releases` Information refer to the relevant pages as follows:
* [[Mellanox-Neutron-ML2-Queens|Mellanox-Queens]]
* [[Mellanox-Neutron-ML2-Pike|Mellanox-Pike]]
* [[Mellanox-Neutron-ML2-Ocata|Mellanox-Ocata]]
* [[Mellanox-Neutron-ML2-Newton|Mellanox-Newton]]
* [[Mellanox-Neutron-ML2-Mitaka|Mellanox-Mitaka]]
* [[Mellanox-Neutron-ML2-Liberty|Mellanox-Liberty]]
* [[Mellanox-Neutron-ML2-Kilo|Mellanox-Kilo]]
* [[Mellanox-Neutron-ML2-Juno|Mellanox-Juno]]
* [[Mellanox-Neutron-ML2-Icehouse|Mellanox-Icehouse]]
* [[Mellanox-Neutron-Havana-Ubuntu|Mellanox-Havana-Ubuntu]] / [[Mellanox-Neutron-Havana-Redhat|Mellanox-Havana-RedHat]]
* [[Mellanox-Neutron-Grizzly|Mellanox-Grizzly]]
 
* [[Mellanox-packages-versioning|Mellanox packages versions]]
 

= References =
1. [http://www.mellanox.com/openstack/ OpenStack solution page at Mellanox site]

2. [https://github.com/openstack/networking-mlnx Mellanox ML2 driver and associated tools source repository]

3. [https://github.com/mellanox-openstack Old/previous Mellanox source repository]

4. [http://www.mellanox.com/page/products_dyn?product_family=26 Mellanox OFED web page]

5. [http://community.mellanox.com/community/develop/cloud-developers Mellanox Cloud Developers Community]

For more details, please refer your question to [mailto:openstack@mellanox.com openstack@mellanox.com]

[[Category: Neutron]]

Mellanox-Neutron-ML2-Queens

2018-07-15T13:29:01Z

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

'''Prerequisites'''
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=119 ConnectX®-3/Mellanox ConnectX®-3 PRO] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers Mellanox OFED] 2.4 or greater
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-4]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] 3.1-1.5.7 or greater.
* Mellanox [http://www.mellanox.com/page/products_dyn?product_family=201& ConnectX®-5]/[http://www.mellanox.com/page/products_dyn?product_family=214&mtag=connectx_4_lx_en_ic ConnectX®-4Lx]/[http://www.mellanox.com/page/products_dyn?product_family=258&mtag=connectx_5_vpi_card ConnectX®-5] with [http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers MLNX_OFED_LINUX] 4.3-1.0.1.0 or greater.