openstack/openstack-manuals
Code Issues Proposed changes

Mark the Ryu plug-in for Neutron as deprecated as of Juno

Browse Source 
Also remove the Ryu plug-in in the list of available network plugin-ins
in the new networking guide to not document a deprecated plug-in.

Change-Id: I289c96b2aa691ccdd7197c2ecdee7697b2428ab5
Closes-Bug: #1356664
This commit is contained in:
Christian Berendt 2014-09-09 17:13:51 +02:00
parent 304e8f39c2
commit 9d897ac399
3 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/admin-guide-cloud/networking/section_networking_config-agents.xml
View File

@ -152,6 +152,12 @@
</section> </section>
<section xml:id="install_neutron_agent_ryu"> <section xml:id="install_neutron_agent_ryu">
<title>Node set up: Ryu plug-in</title> <title>Node set up: Ryu plug-in</title>
<warning>
<para>
The Ryu plug-in is deprecated as of the Juno release and might be removed in Kilo
or a subsequent release.
</para>
</warning>
<para>If you use the Ryu plug-in, you must install <para>If you use the Ryu plug-in, you must install
both Open vSwitch and Ryu, in addition to the Ryu both Open vSwitch and Ryu, in addition to the Ryu
agent package.</para> agent package.</para>

6
doc/admin-guide-cloud/networking/section_networking_config-plugins.xml
View File

@ -319,6 +319,12 @@ password = "PLUMgrid-director-admin-password"</programlisting>
</section> </section>
<section xml:id="ryu_plugin"> <section xml:id="ryu_plugin">
<title>Configure Ryu plug-in</title> <title>Configure Ryu plug-in</title>
<warning>
<para>
The Ryu plug-in is deprecated as of the Juno release and might be removed in Kilo or
a subsequent release.
</para>
</warning>
<procedure> <procedure>
<title>To use the Ryu plug-in with OpenStack Networking</title> <title>To use the Ryu plug-in with OpenStack Networking</title>
<step> <step>

1
doc/networking-guide/section_architecture-plug-in.xml
View File

@ -35,7 +35,6 @@ ML2 (Modular Layer 2) Plug-in https://wiki.openstack.org/wiki/Neutron/ML2
NEC OpenFlow Plug-in https://wiki.openstack.org/wiki/Neutron/NEC_OpenFlow_Plugin NEC OpenFlow Plug-in https://wiki.openstack.org/wiki/Neutron/NEC_OpenFlow_Plugin
Open vSwitch Plug-in This guide. Open vSwitch Plug-in This guide.
PLUMgrid This guide and https://https://wiki.openstack.org/wiki/PLUMgrid-Neutron PLUMgrid This guide and https://https://wiki.openstack.org/wiki/PLUMgrid-Neutron
Ryu Plug-in This guide and https://github.com/osrg/ryu/wiki/OpenStack
VMware NSX Plug-in This guide and NSX Product Overview, NSX Product Support VMware NSX Plug-in This guide and NSX Product Overview, NSX Product Support
Plug-ins can have different properties for hardware requirements, features, performance, scale, or operator tools. Because Networking supports a large number of plug-ins, the cloud administrator can weigh options to decide on the right networking technology for the deployment. Plug-ins can have different properties for hardware requirements, features, performance, scale, or operator tools. Because Networking supports a large number of plug-ins, the cloud administrator can weigh options to decide on the right networking technology for the deployment.
In the Havana release, OpenStack Networking introduces the Modular Layer 2 (ML2) plug-in that enables the use of multiple concurrent mechanism drivers. This capability aligns with the complex requirements typically found in large heterogeneous environments. It currently works with the existing Open vSwitch, Linux Bridge, and Hyper-v L2 agents. The ML2 framework simplifies the addition of support for new L2 technologies and reduces the effort that is required to add and maintain them compared to earlier large plug-ins. In the Havana release, OpenStack Networking introduces the Modular Layer 2 (ML2) plug-in that enables the use of multiple concurrent mechanism drivers. This capability aligns with the complex requirements typically found in large heterogeneous environments. It currently works with the existing Open vSwitch, Linux Bridge, and Hyper-v L2 agents. The ML2 framework simplifies the addition of support for new L2 technologies and reduces the effort that is required to add and maintain them compared to earlier large plug-ins.