Difference between revisions of "Neutron/NEC OpenFlow Plugin"
< Neutron
(→Introduction) |
m (→Using NEC OpenFlow plugin) |
||
| Line 23: | Line 23: | ||
* [https://github.com/stackforge/networking-nec/blob/master/doc/source/installation.rst Manual installation] | * [https://github.com/stackforge/networking-nec/blob/master/doc/source/installation.rst Manual installation] | ||
* [https://github.com/stackforge/networking-nec/blob/master/doc/source/contributing.rst Configuration Guide] | * [https://github.com/stackforge/networking-nec/blob/master/doc/source/contributing.rst Configuration Guide] | ||
| + | |||
| + | ---- | ||
Note for Juno DevStack users: | Note for Juno DevStack users: | ||
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
- Git: https://github.com/stackforge/networking-nec
- Launchpad: https://launchpad.net/networking-nec
- PyPI: https://pypi.python.org/pypi/networking-nec
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
- DevStack (with Kilo or later)
- Manual installation
- Configuration Guide
Note for Juno DevStack users:
- Devstack support of NEC OpenFlow plugin is a part of the official devstack (http://github.com/openstack-dev/devstack) from Grizzly.
- Detail instruction and sample devstack configuration examples (localrc) are available at https://github.com/nec-openstack/devstack-neutron-nec-openflow/wiki .
