Jump to: navigation, search

Difference between revisions of "Mellanox-Neutron-Icehouse-Ubuntu-Ethernet"

(Compute Nodes)
(Network Node)
 
(8 intermediate revisions by the same user not shown)
Line 16: Line 16:
 
== Controller Node ==  
 
== Controller Node ==  
  
In /etc/nova/nova.conf ensure you have the following line:  
+
In /etc/nova/nova.conf, ensure you have the following line:  
 
   security_group_api=nova
 
   security_group_api=nova
  
Line 25: Line 25:
 
NOTE: The Neutron Server can sometimes be part of the Controller node.
 
NOTE: The Neutron Server can sometimes be part of the Controller node.
  
To configure Neutron-Server node:
+
To configure the Neutron-Server node:
  
 
1. Edit /etc/neutron/neutron.conf, and make sure Neutron is using ML2 plugin:
 
1. Edit /etc/neutron/neutron.conf, and make sure Neutron is using ML2 plugin:
Line 59: Line 59:
 
== Compute Nodes ==
 
== Compute Nodes ==
  
To configure Compute nodes:  
+
To configure the Compute node:  
  
 
1. Download mlnxvif and eSwitch Daemon (eSwitchd) from the following link:
 
1. Download mlnxvif and eSwitch Daemon (eSwitchd) from the following link:
Line 89: Line 89:
 
== Network Node ==
 
== Network Node ==
  
1. Install the Neutron Linux bridge plugin, the Neutron DHCP agent and the Neutron L3 agent:
+
To configure the Network node:
  
  # apt-get install neutron-plugin-linuxbridge-agent neutron-dhcp-agent neutron-l3-agent
+
1. Configure eIPoIB (for Linux bridge plugin), and edit the file /etc/infiniband/openib.conf as follows:
 +
E_IPOIB_LOAD=yes
 +
2. Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini as follows:
 +
physical_interface_mappings = <physical_network>:<eth-interface>
 +
//(i.e. default:eth2)
 +
3. Restart Open vSwitch agent:
 +
service neutron-openvswitch-agent restart
 +
4. Copy /etc/neutron/neutron.conf from the Compute node to the same path on the Network node.
  
2. Copy /etc/neutron/neutron.conf from the Compute node.
+
5. Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini as follows:
 
+
physical_interface_mappings = <physical_network>:<eth interface>
3. Change the following configuration of the ini file (/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini). The "default" in the example is the name of the physical network as configured in /etc/neutron/plugins/mlnx/mlnx_conf.ini .  
+
//(i.e. default:eth2)
  [linux_bridge] 
+
6. Edit /etc/neutron/dhcp_agent.ini and /etc/neutron/l3_agent.ini as follows:
  physical_interface_mappings = default:eth2  
+
[DEFAULT]  
 
+
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
4. Configure the DHCP agent according to the following guidelines
+
7. Restart the following services:
 
+
service neutron-plugin-linuxbridge-agent restart
Update the following file: /etc/neutron/dhcp_agent.ini with:
+
service neutron-dhcp-agent restart
  [DEFAULT]
+
service neutron-l3-agent restart
  interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
 
 
 
For additional information refer to the [http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html#section_adv_cfg_dhcp_agent OpenStack documentation]
 
 
 
5. Configure the L3 agent according to the following guidelines
 
 
 
Update the following file: /etc/neutron/l3_agent.ini with:
 
  [DEFAULT]  
 
  interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
 
 
 
For additional information refer to the [http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html#section_adv_cfg_l3_agent OpenStack documentation]
 
 
 
6. Configure the Metadata agent according to the [http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html#nova_config_metadata OpenStack documentation]
 
 
 
7. Start the Neutron Linux Bridge, DHCP and L3 agents
 
  # restart neutron-plugin-linuxbridge-agent
 
  # restart neutron-dhcp-agent
 
  # restart neutron-l3-agent
 
  # restart neutron-metadata-agent
 
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
 
* If you're seeing request timeout errors in the plugin's logs, make sure that the eswitchd service is started and try to increase the request_timeout value in the plugin configuration file.
 
* If you're seeing request timeout errors in the plugin's logs, make sure that the eswitchd service is started and try to increase the request_timeout value in the plugin configuration file.

Latest revision as of 16:30, 26 November 2014

Overview

This wiki page describes how to tune Mellanox OpenStack on Ubuntu 12.04 servers

Prerequisites

Ethernet Network

Controller Node

In /etc/nova/nova.conf, ensure you have the following line:

  security_group_api=nova

If the value is changed, restart the Nova services:

  # for i in $(initctl list | grep '^nova' | awk '{print $1}'); do service $i restart; done

Neutron Server Node

NOTE: The Neutron Server can sometimes be part of the Controller node.

To configure the Neutron-Server node:

1. Edit /etc/neutron/neutron.conf, and make sure Neutron is using ML2 plugin:

[DEFAULT]
core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin

2. Modify the ML2 configuration file (/etc/neutron/plugins/ml2/ml2_conf.ini) as follows:

[ml2]
type_drivers = vlan,flat
tenant_network_types = vlan
mechanism_drivers = openvswitch,mlnx  
[ml2_type_vlan]
network_vlan_ranges=<physical_network>:<min_vlan>:<max_vlan> //(i.e. default:2:10)   
[securitygroup]
enable_security_group = True   
[eswitch]
vnic_type = hostdev
apply_profile_patch = True

3. Install the required Deb for the Mellanox Neutron plugin (from Ubuntu’s repository):

apt-get install neutron-plugin-mlnx-agent

4. Edit /etc/neutron/plugins/mlnx/mlnx_conf.ini to match your environment:

[mlnx]
network_vlan_ranges = <physical_network>:<min_vlan:<max_vlan> //(i.e. default:2:10)
tenant_network_type = vlan 
[eswitch]
physical_interface_mappings = <physical_network>:<eth interface> //(i.e. default:eth0)
vnic_type = hostdev
[agent]
support_old_agents = True

5. Restart neutron-server:

/etc/init.d/neutron-server start

Compute Nodes

To configure the Compute node:

1. Download mlnxvif and eSwitch Daemon (eSwitchd) from the following link:

http://www.mellanox.com/downloads/solutions/openstack/icehouse/debian/

2. Install the Mellanox plugin services mlnxvif and eSwitchd:

dpkg –i python-mlnxvif_2014.1.1-1_all.deb
dpkg –i python-eswitchd_0.10-1_all.deb

3. Edit /etc/eswitchd/eswitchd.conf as follows:

[DAEMON]
fabrics=<physical_network>:<eth-interface> //(i.e. default:eth0)

4. Edit /etc/nova/nova.conf as follows:

[DEFAULT]
compute_driver = libvirt.LibvirtDriver
libvirt_vif_driver = mlnxvif.vif.MlxEthVIFDriver
security_group_api = nova

5. Check if “ebrctl” appears in one of Nova’s rootwrap files:

grep 'ebrctl' /etc/nova/rootwrap.d/*

If “ebrctl” does not appear in one of Nova’s rootwrap files, edit the file /etc/nova/rootwrap.d/compute.filters as follows:

[Filters]
ebrctl: CommandFilter, ebrctl, root

6. Install the Neutron Mellanox agent (from Ubuntu repository):

apt-get install neutron-plugin-mlnx-agent

7. Copy /etc/neutron/plugins/mlnx/mlnx_conf.ini from the Neutron Server node to the same path on each Compute node. 8. Restart the following services:

/etc/init.d/nova-compute restart
/etc/init.d/eswitchd start
/etc/init.d/neutron-plugin-mlnx-agent start

Network Node

To configure the Network node:

1. Configure eIPoIB (for Linux bridge plugin), and edit the file /etc/infiniband/openib.conf as follows:

E_IPOIB_LOAD=yes

2. Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini as follows:

physical_interface_mappings = <physical_network>:<eth-interface> 
//(i.e. default:eth2)

3. Restart Open vSwitch agent:

service neutron-openvswitch-agent restart

4. Copy /etc/neutron/neutron.conf from the Compute node to the same path on the Network node.

5. Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini as follows:

physical_interface_mappings = <physical_network>:<eth interface> 
//(i.e. default:eth2)

6. Edit /etc/neutron/dhcp_agent.ini and /etc/neutron/l3_agent.ini as follows:

[DEFAULT] 
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver

7. Restart the following services:

service neutron-plugin-linuxbridge-agent restart 
service neutron-dhcp-agent restart
service neutron-l3-agent restart

Troubleshooting

  • If you're seeing request timeout errors in the plugin's logs, make sure that the eswitchd service is started and try to increase the request_timeout value in the plugin configuration file.