vmware-nsx/neutron/plugins/ml2/drivers/brocade
Shiv Haris c933e80a06 Implementaion of Mechanism driver for
Brocade VDX cluster of switches

Change-Id: Ic1649f7cee73a41f286e12d8ba6ca30be6261cfe
Implements: blueprint brocade-ml2-mechanism-driver
2014-03-04 15:31:36 -08:00
..
db Implementaion of Mechanism driver for 2014-03-04 15:31:36 -08:00
nos Implementaion of Mechanism driver for 2014-03-04 15:31:36 -08:00
__init__.py Implementaion of Mechanism driver for 2014-03-04 15:31:36 -08:00
mechanism_brocade.py Implementaion of Mechanism driver for 2014-03-04 15:31:36 -08:00
README.md Implementaion of Mechanism driver for 2014-03-04 15:31:36 -08:00

Brocade ML2 Mechanism driver from ML2 plugin

ML2 plugin requires mechanism driver to support configuring of hardware switches. Brocade Mechanism for ML2 uses NETCONF at the backend to configure the Brocade switch. Currently the mechanism drivers support VLANs only.

         +------------+        +------------+          +-------------+
         |            |        |            |          |             |

Neutron | | | | | Brocade | v2.0 | Openstack | | Brocade | NETCONF | VCS Switch | ----+ Neutron +--------+ Mechanism +----------+ | | ML2 | | Driver | | VDX 67xx | | Plugin | | | | VDX 87xx | | | | | | | | | | | | | +------------+ +------------+ +-------------+

Configuration

In order to use this mechnism the brocade configuration file needs to be edited with the appropriate configuration information:

    % cat /etc/neutron/plugins/ml2/ml2_conf_brocade.ini
    [switch]
    username = admin
    password = password
    address  = <switch mgmt ip address>
    ostype   = NOS
    physical_networks = phys1

Additionally the brocade mechanism driver needs to be enabled from the ml2 config file:

   % cat /etc/neutron/plugins/ml2/ml2_conf.ini

   [ml2]
   tenant_network_types = vlan
   type_drivers = local,flat,vlan,gre,vxlan
   mechanism_drivers = openvswitch,brocade
   # OR mechanism_drivers = openvswitch,linuxbridge,hyperv,brocade
   ...
   ...
   ...

Required L2 Agent

This mechanism driver works in conjuction with an L2 Agent. The agent should be loaded as well in order for it to configure the virtual network int the host machine. Please see the configuration above. Atleast one of linuxbridge or openvswitch must be specified.