Jump to: navigation, search

Difference between revisions of "Neutron/NEC OpenFlow Plugin"

(Introduction)
Line 14: Line 14:
 
network slice on an OpenFlow enabled network. The interface between the Neutron plugin and OpenFlow
 
network slice on an OpenFlow enabled network. The interface between the Neutron plugin and OpenFlow
 
Controller is RESTful API. This API is supported by two implementations:
 
Controller is RESTful API. This API is supported by two implementations:
 
+
[http://www.necam.com/SDN/ NEC ProgrammableFlow Networking Controller] and
* Trema Sliceable Switch (OSS)
+
[https://github.com/trema/apps/tree/master/sliceable_switch Trema Sliceable Switch].
* NEC ProgrammableFlow Controller (NEC Commercial Product).
+
More detail is available in [https://github.com/stackforge/networking-nec/blob/master/doc/source/readme.rst networking-nec repository].
 
 
More detail is available at https://github.com/stackforge/networking-nec/blob/master/doc/source/readme.rst
 
  
 
== Using NEC OpenFlow plugin ==
 
== Using NEC OpenFlow plugin ==

Revision as of 00:18, 25 September 2015

[Note] In Kilo development cycle, Neutron community decides to move vendor specific codes into separate repositories. NEC OpenFlow plugin is now available at https://git.openstack.org/stackforge/networking-nec.

Project Links

Introduction

NEC OpenFlow plugin talks to OpenFlow Controller and each Neutron would be mapped to an virtual layer-2 network slice on an OpenFlow enabled network. The interface between the Neutron plugin and OpenFlow Controller is RESTful API. This API is supported by two implementations: NEC ProgrammableFlow Networking Controller and Trema Sliceable Switch. More detail is available in networking-nec repository.

Using NEC OpenFlow plugin

Note for Juno DevStack users: