Jump to: navigation, search

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

(Controller Node)
(Network Node)
 
(17 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 22: Line 22:
 
   # for i in $(initctl list | grep '^nova' | awk '{print $1}'); do service $i restart; done
 
   # for i in $(initctl list | grep '^nova' | awk '{print $1}'); do service $i restart; done
  
== Neutron Server Node ==
+
=== Neutron Server Node ===
=== Installation ===
+
NOTE: The Neutron Server can sometimes be part of the Controller node.
  
1. Neutron server uses MySQL database. Make sure you have running MySQL database for neutron.
+
To configure the Neutron-Server node:
  
If Neutron server is already running, you should stop it.  
+
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
  
  #/etc/init.d/neutron-server stop
+
5. Restart neutron-server:  
 
+
  /etc/init.d/neutron-server start
If you want to use a database that was created you have to drop it and create another one. For example:
 
 
 
  mysql -u root -ppassword <<EOF
 
  drop database if exists neutron;
 
  create database neutron;
 
  EOF
 
 
 
If you want to create a new one:
 
 
 
  mysql -u root -ppassword <<EOF
 
  drop database if exists neutron;
 
  create database neutron;
 
  GRANT ALL PRIVILEGES ON neutron.* TO 'neutron'@'localhost' IDENTIFIED BY 'password';
 
  GRANT ALL PRIVILEGES ON neutron.* TO 'neutron' IDENTIFIED BY 'password';
 
  FLUSH PRIVILEGES;
 
  EOF
 
 
 
2. Install the required Deb for the Mellanox Neutron plugin:
 
 
 
  apt-get install -y neutron-plugin-mlnx-agent
 
 
 
3. Modify the /etc/neutron/plugins/mlnx/mlnx_conf.ini file to reflect your environment.
 
 
 
4. Change /etc/default/neutron-server :
 
 
 
  NEUTRON_PLUGIN_CONFIG="/etc/neutron/plugins/mlnx/mlnx_conf.ini"
 
 
 
=== Configuration ===
 
 
 
1. Make the Mellanox plugin the current Neutron plugin by editing neutron.conf and changing core_plugin.
 
 
 
  core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin
 
 
 
2. Plugin configuration: Edit the configuration file: /etc/neutron/plugins/mlnx/mlnx_conf.ini
 
 
 
  [MLNX]
 
  tenant_network_type - must be set on of supported tenant network types.  
 
                        Possible values: 'vlan' for Ethernet or 'ib' for Infiniband.'vlan' is the default.
 
  network_vlan_ranges - must be configured to specify the names of the  physical   
 
 
  networks managed by the mellanox plugin,
 
  along with the ranges of VLAN IDs available on each physical network for allocation to virtual networks. 
 
  Possible range is vlan range is 1-4093.
 
  The default  is "default:1:100"
 
  <fabric name >:<vlan range start>:<vlan end range>
 
 
 
  [agent]
 
  rpc_support_old_agents = True
 
  Note: rpc_support_old_agents should be set to 'True' (non default).
 
 
 
=== Start Services ===
 
 
 
Start (or restart) the Neutron server
 
  #/etc/init.d/neutron-server start
 
  
 
== Compute Nodes ==
 
== Compute Nodes ==
  
=== Installation ===
+
To configure the Compute node:  
 
 
1. If you didn't download Mellanox OpenStack debian files download it :
 
 
 
http://www.mellanox.com/downloads/solutions/openstack/
 
 
 
2. Install the eswitchd debian files:  
 
  dpkg -i eswitchd_0.8-1_amd64.deb
 
  dpkg -i python-mlnxvif_0.6-1_all.deb
 
  apt-get install -f # fix dependencies
 
  apt-get install -y neutron-plugin-mlnx-agent
 
 
 
3. In case you would like to use Ethernet in para-virtualized mode the VIF driver is already included in Nova package. Otherwise, Install Mellanox VIF driver (Make sure nova is installed on your server)
 
 
 
=== Configuration ===
 
 
 
1. Configure /etc/eswitchd/eswitchd.conf if needed
 
  
Please Refer to Mellanox Community for the eSwitchd installation notes ( click [http://community.mellanox.com/docs/DOC-1126 here])
+
1. Download mlnxvif and eSwitch Daemon (eSwitchd) from the following link:
 
+
http://www.mellanox.com/downloads/solutions/openstack/icehouse/debian/
2. Modify /etc/nova/nova.conf
+
2. Install the Mellanox plugin services mlnxvif and eSwitchd:
 
+
dpkg –i python-mlnxvif_2014.1.1-1_all.deb
  compute_driver=nova.virt.libvirt.driver.LibvirtDriver
+
dpkg –i python-eswitchd_0.10-1_all.deb
  libvirt_vif_driver=mlnxvif.vif.MlxEthVIFDriver
+
3. Edit /etc/eswitchd/eswitchd.conf as follows:
  security_group_api=nova
+
[DAEMON]
  connection_type=libvirt
+
fabrics=<physical_network>:<eth-interface> //(i.e. default:eth0)
 
+
4. Edit /etc/nova/nova.conf as follows:
In case you didn't install the Mellanox VIF driver, and you plan to use Ethernet only in paravirtualized ,mode: change the following:  
+
[DEFAULT]
 
+
compute_driver = libvirt.LibvirtDriver
  libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver
+
libvirt_vif_driver = mlnxvif.vif.MlxEthVIFDriver
 
+
security_group_api = nova
3. Modify the /etc/neutron/plugins/mlnx/mlnx_conf.ini file to reflect your environment.  
+
5. Check if “ebrctl” appears in one of Nova’s rootwrap files:
  [AGENT]
+
grep 'ebrctl' /etc/nova/rootwrap.d/*
  rpc_support_old_agents = True
+
If “ebrctl” does not appear in one of Nova’s rootwrap files, edit the file /etc/nova/rootwrap.d/compute.filters as follows:
  [ESWITCH]
+
[Filters]
  physical_interface_mapping -  the network_interface_mappings maps each physical network name to the physical interface (on top of Mellanox Adapter) connecting the node to that physical network. The format of this paramter is:    <fabric name>:< PF name> (Only releavant on Compute node). PF Name can either be the PF (Physical Function) Name or 'autoeth' for automatic Ethernet configuration,'autoib' for automatic Infiniband configuration.The default is  "default:autoeth". 
+
ebrctl: CommandFilter, ebrctl, root
  vnic_type - type of VM network interface: 'mlnx_direct' or 'hostdev'  according to libvirt terminology.
+
6. Install the Neutron Mellanox agent (from Ubuntu repository):
        hostdev: this is the traditional method of assigning any generic PCI device to a guest (SR-IOV).
+
apt-get install neutron-plugin-mlnx-agent
        mlnx_direct: this is a method to provide macvtap device on top of the PCI device (default).
+
7. Copy /etc/neutron/plugins/mlnx/mlnx_conf.ini from the Neutron Server node to the same path on each Compute node.
        bridge:  - When using Linux Bridge Plugin on top of eIPoIB device
+
8. Restart the following services:
  daemon_endpoint - 'tcp://127.0.0.1:60001'
+
/etc/init.d/nova-compute restart
 
+
/etc/init.d/eswitchd start
For a plugin configuration file example (Havana), please refer to Mellanox config *ini file (click [https://github.com/openstack/neutron/blob/stable/havana/etc/neutron/plugins/mlnx/mlnx_conf.ini here])
+
/etc/init.d/neutron-plugin-mlnx-agent start
 
 
4. (Optional) Modify /etc/init/neutron-plugin-mlnx-agent.conf as described in LP bug #[https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1257732 1257732]
 
 
 
5. Check that ebrctl is listed somewhere in /etc/nova/rootwrap.d/*, otherwise add this to /etc/nova/rootwrap.d/compute.filters file in the [Filters] section.
 
  ebrctl: CommandFilter, ebrctl, root
 
 
 
=== Start Services ===
 
 
 
1. Restart Nova.
 
 
 
  #/etc/init.d/nova-compute restart
 
 
 
2. Start eswitch Daemon
 
 
 
  #/etc/init.d/eswitchd start
 
 
 
3. Start the Neutron agent
 
 
 
  #/etc/init.d/neutron-plugin-mlnx-agent start
 
 
 
Note: eswitch Daemon should be running before the Neutron Agent is started.
 
  
 
== 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
 
 
 
2. Copy /etc/neutron/neutron.conf from the Compute node.
 
 
 
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 .
 
  [linux_bridge] 
 
  physical_interface_mappings = default:eth2
 
 
 
4. Configure the DHCP agent according to the following guidelines
 
 
 
Update the following file: /etc/neutron/dhcp_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_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]
+
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.
  
7. Start the Neutron Linux Bridge, DHCP and L3 agents
+
5. Edit /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini as follows:
  # restart neutron-plugin-linuxbridge-agent
+
physical_interface_mappings = <physical_network>:<eth interface>
  # restart neutron-dhcp-agent
+
//(i.e. default:eth2)
  # restart neutron-l3-agent
+
6. Edit /etc/neutron/dhcp_agent.ini and /etc/neutron/l3_agent.ini as follows:
  # restart neutron-metadata-agent
+
[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 ==
 
== 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.