OpenStack - User contributions [en]

Neutron/ML2/LenovoML2Mechanism

2015-08-19T17:20:28Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [http://publib.boulder.ibm.com/infocenter/systemx/documentation/topic/com.lenovo.switchmgt.openstack_neutron_plugin.doc/Lenovo_Openstack_Neutron_Plugin_UG.pdf Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver with Lenovo Switches, the Openstack launchpad application is a good tool for opening a bug against it and Lenovo may address this on a best effort basis.

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-19T17:19:25Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [http://publib.boulder.ibm.com/infocenter/systemx/documentation/topic/com.lenovo.switchmgt.openstack_neutron_plugin.doc/Lenovo_Openstack_Neutron_Plugin_UG.pdf/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver with Lenovo Switches, the Openstack launchpad application is a good tool for opening a bug against it and Lenovo may address this on a best effort basis.

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-19T16:37:42Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running on the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver with Lenovo Switches, the Openstack launchpad application is a good tool for opening a bug against it and Lenovo may address this on a best effort basis.

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-19T16:36:24Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Lenovo Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver with Lenovo Switches, the Openstack launchpad application is a good tool for opening a bug against it and Lenovo may address this on a best effort basis.

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-14T19:55:49Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver with Lenovo Switches, the Openstack launchpad application is a good tool for opening a bug against it and Lenovo may address this on a best effort basis.

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-14T19:55:19Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

[[File:RH certified technology partner logo v1 1214clean rgb reverse.png|thumbnail|center|Certified]]

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver with Lenovo Switches, the Openstack launchpad application is a good tool for opening a bug against it and Lenovo may address this on a best effort basis.

[[category:neutron]]

File:RH certified technology partner logo v1 1214clean rgb reverse.png

2015-08-14T19:53:08Z

Larkland Morley:

Neutron/ML2/LenovoML2Mechanism

2015-08-13T00:36:36Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver with Lenovo Switches, the Openstack launchpad application is a good tool for opening a bug against it and Lenovo may address this on a best effort basis.

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-13T00:34:31Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

'''4. Support Policy'''

This software is provided as Open source code therefore, Lenovo does not provide any support entitlements for this product. If any issues occur while using this driver, the open launchpad application is a good tool for opening a bug against it and Lenovo may address this by best effort.

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-13T00:10:27Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The following are prerequisites for using the plug-in:

* Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-13T00:06:26Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: https://github.com/lenovo-network/networking-lenovo
* Source: https://github.com/lenovo-network/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-13T00:00:09Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:57:41Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

When network redundancy is required, Lenovo VLAG is recommended as shown below

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:55:21Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

-----
'''Recommended Network Configurations'''
----
The following is an example of Single Port Server attachments where no redundancy is required

[[File:Single nic servers1.gif|frameless|Single Server Attachment]]

The following is an example with Lenovo VLAG attachments to Servers

[[File:Vlag layout1.gif|frameless|Lenovo VLAG Configuration]]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

File:Single nic servers1.gif

2015-08-12T23:49:56Z

Larkland Morley:

File:Vlag layout1.gif

2015-08-12T23:47:47Z

Larkland Morley:

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:39:53Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
--------
The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking ML2 User Guide is provided to assist with installation and setup of this driver - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:38:28Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''

The following is an important support matrix for this driver

{| class="wikitable"
|-
! Component !! Requirements
|-
| Supported Lenovo Switches || G8272, G8332, G8052 and G8264
|-
| Supported Lenovo NOS || 7.9, 8.x
|-
| Supported OS Platforms || Redhat, Ubuntu
|-
| Openstack Version || Kilo
|-
| VLAN Range || 2-4094
|-
| Redhat Linux || RHEL Openstack 7
|-
|}

'''User Guide'''

The Lenovo Networking Openstack User Guide is provided to assist with installation and setup of this plugin - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:31:46Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''General Requirements'''
{| class="wikitable"
|-
! Component !! Requirements
|-
| Example || Example
|-
| Example || Example
|-
| Example || Example
|-
| Example || Example
|-
| Example || Example
|-
| Example || Example
|-
| Example || Example
|}

'''User Guide'''

The Lenovo Networking Openstack User Guide is provided to assist with installation and setup of this plugin - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:25:33Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''User Guide'''

The Lenovo Networking Openstack User Guide is provided to assist with installation and setup of this plugin - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:13:53Z

Larkland Morley: /* Lenovo Networking Openstack Neutron Plug-in */

==Lenovo Networking Openstack Neutron Plug-in==

Here you will find details on the Lenovo vendor code Neutron ML2 Driver for Kilo or later

* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/networking-lenovo
* Source: http://git.openstack.org/cgit/stackforge/networking-lenovo
* Bugs: http://bugs.launchpad.net/networking-lenovo

'''Overview'''
--------

Openstack is an open source infrastructure initiative for creating and managing large groups of virtual private servers in a cloud computing environment. Lenovo’s Networking Neutron ML2 Driver provides a means to orchestrate VLANs on Lenovo’s physical switches. In cloud environments where VMs are hosted by physical servers, the VMs see a new virtual access layer provided by the host machine.

This new access layer can be typically created via many mechanisms e.g. Linux Bridges or a Virtual Switches. The policies of the virtual access layer (virtual network), when set must now be coordinated with the policies set in the hardware switches. Lenovo’s Neutron Plugin helps in coordinating this behavior automatically without any intervention from the administrator. The illustration below provides an architectural overview of how Lenovo’s ML2 Plugin and switches fits into an Openstack deployment.

[[File:Lenovo openstack driver.gif|none|center|Lenovo ML2 Plugin Architecture]]
------------

'''User Guide'''

The Lenovo Networking Openstack User Guide is provided to assist with installation and setup of this plugin - [https://www.dropbox.com/s/ctfd8mxud4r84cj/Openstack_Neutron_Plugin_UG.pdf?dl=0/ Download User Guide]

'''Download Lenovo ML2 Driver Code'''

The Lenovo Networking ML2 Driver code is located on [https://github.com/lenovo-network/networking-lenovo Github].

'''Lenovo Networking Products'''

Learn more about Lenovo Data Center Switches on [http://shop.lenovo.com/us/en/systems/networking/ Lenovo Networking Website]

----------
'''Using the Lenovo Openstack ML2 Driver'''
-------------

'''1. Lenovo Plug-in Installation'''

The following are the detailed steps to setup your Openstack deployment with Lenovo Neutron Plugin managing Lenovo Switches.

'''1.1 Lenovo Plug-in Prerequisites'''

The Lenovo Plug-in will provide dynamic VLAN configuration on access layer switches server facing ports that maps Openstack networks into the physical infrastructure.

The following are prerequisites for using the plug-in:

- Install python pip and git to allow the downloading of files from Github

For Redhat, use the following:

<pre><nowiki>
% sudo yum install python-pip git
</nowiki></pre>

For Ubuntu, use the following:

<pre><nowiki>
% sudo apt-get install python-pip git
</nowiki></pre>

* Install the ncclient v0.4.2 Python library for NETCONF clients. For more information on ncclient, see http://ncclient.grnet.gr/.

* Install with the ncclient library by using the pip package manager at your shell prompt:

<pre><nowiki>
% sudo pip install ncclient == 0.4.2
</nowiki></pre>

* Determine the VLAN pool for your Openstack Deployment, for example 1001-2001. This will be required for configuring the uplink ports and the plugin.

* Configure physical network topology; add the assigned VLAN pool to uplink ports and aggregation switches as required. Other protocols such as ACLs, switch access credential should be configured as needed.

* SSH needs to be enabled on all Openstack Managed switches. This is required for the NETCONF protocol.

* In VLAG mode, the ISL and Portchannel/LACP trunk should be created on the relevant switches as the plugin does not configure these attributes.

* Server NICs connected to VLAG Switches needs to have NIC bonding configured (see Network topology section for examples).

* Install Openstack Controller and Network nodes. Openstack needs to be running before installing the Lenovo Neutron driver.

'''1.2 ML2 Installation Procedure'''

This section will cover the installation procedure for Lenovo Networking Openstack ML2 Driver plug-in in a Multi Node environment with Redhat Enterprise Linux 7 Openstack or Ubuntu 14.04 LTS:

'''Download Lenovo ML2 driver'''

The ML2 installation files can be downloaded from Lenovo Stackforge Github site with “git clone” as shown below

<pre><nowiki>
% sudo git clone git.openstack.org/cgit/openstack/networking-lenovo
</nowiki></pre>

'''Setup Lenovo ML2 Plug-in'''

The next step is to install the plug-in
<pre><nowiki>
% cd networking-lenovo
% sudo python setup.py install
</nowiki></pre>

This concludes the Lenovo ML2 driver (vendor code) installation step.

'''1.2.1 Redhat Openstack Setup'''

The following steps are required for Kilo based installations such as Redhat Openstack Release 7 Environments.

Sttep 1 is to uninstall the current neutron on the system as follows:

<pre><nowiki>
% sudo pip uninstall neutron;
</nowiki></pre>

Once the current neutron has been uninstalled, the next step is to download the kilo neutron code for Lenovo from Github as follows

<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron.git
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron driver as follows

<pre><nowiki>
% cd neutron
% sudo git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>

change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo systemctl start neutron-server.service
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''1.2.2 Ubuntu Openstack Setup'''

The following steps are required for Kilo based installations in Ubuntu 14.x Environments. The first step is to uninstall the current neutron on the system as follows:
<pre><nowiki>
% sudo pip uninstall neutron
</nowiki></pre>

Once the current neutron has been uninstalled, we need to download the kilo neutron code for Lenovo from Github as follows
<pre><nowiki>
% sudo git clone https://github.com/lenovo-network/neutron
</nowiki></pre>

Once the files are downloaded, install the Lenovo Neutron code as follows
<pre><nowiki>
% cd neutron
% git checkout staging/kiloplus
% sudo python setup.py install
</nowiki></pre>

At this point the Lenovo ML2 driver has been installed and Neutron for Kilo Replaced.

'''Update ML2 Configuration'''

Now it is time to edit the ml2 configuration files with some basic information on the use of VLANs for networking and add local switch information.

<pre><nowiki>
% cd /etc/neutron/plugins/ml2
</nowiki></pre>

Change the file ml2_conf.ini as follows

<pre><nowiki>
% sudo vi ml2_conf.ini,
* change tenant_network_types = vlan
* change mechanism_drivers = openvswitch,lenovo
* copy everything in ml2_conf_lenovo.ino, and concatenate to ml2_conf.ini,
</nowiki></pre>
change this section according to network setup requirements, add the IP address of switch(es), Connection details and change the hostname for servers

(See more details on this step in section '''2. Plugin Configuration''')

'''Neutron Database Migration'''

<pre><nowiki>
% sudo neutron-db-manage –config-file /etc/neutron/neutron.conf –config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head
</nowiki></pre>

Start the Neutron Server – Exiting the mysql is required for this step:

<pre><nowiki>
% sudo service neutron-server restart
</nowiki></pre>

If any issues are observed please check the section “3. Troubleshooting the Installation”.

'''2. Lenovo Plug-in Configuration'''

Two sections of the configuration file will need to be modified manually in /etc/neutron/plugins/ml2/ml2_conf.ini

The first section is in [ml2[ to have Lenovo included in mechanism_drivers, and network_vlan_ranges need to be defined as in ml2_type_vlan section.

<pre><nowiki>
[ml2]
tenant_network_types = vlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,lenovo
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# But provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2
network_vlan_ranges = default:1000:1999
</nowiki></pre>

The second section is to add Lenovo switch information to the section [ml2_mech_lenovo] of this configuration file.

Include the following information (see the example below):

* The Hostname/IP address of the Switch
* The hostname and port of the server(s) that is connected to the switch
* The Lenovo switch credential username and password
* Portchannel or LACP number for Host connected with VLAG
* SSH Port number for Netconf (Typically 830)

The expectation is that there could be several servers to switch port mapping per switch only limited by number of available ports.

<pre><nowiki>
[ml2_mech_lenovo:10.240.179.65]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-1 = portchannel:64
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port = 830
# Provide the Nexus log in information
username = admin
password = admin

[ml2_mech_lenovo:10.240.179.54]
# Hostname and port used on the switch for this compute host.
nova-node-2 = 17
# Port number where the SSH will be running at the Nexus Switch. Default is 22 so this variable
# only needs to be configured if different.
ssh_port=830
# Provide the Nexus log in information
username = admin
password = admin
</nowiki></pre>

As more switches and servers are added to the network, the above file would need to be updated with these details.
Once this configuration is done, it is now time to create networks from the Horizon dashboard or Openstack command line.

'''3. Troubleshooting the Installation'''

If the server Neutron server does not start, you can check the

1. Neutron log file, the log is located at /var/log/neutron/server.log.

2. Verify that Lenovo Plugin details are in the mysql database:

<pre><nowiki>
% sudo mysql –u root –p –h [your IP]

mysql> use neutron;

mysql> show tables;
</nowiki></pre>

(Verify that the following table is present lenovo_ml2_nosport_bindings)

[[category:neutron]]

Neutron/ML2/LenovoML2Mechanism

2015-08-12T23:09:24Z