Features/Ryu

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Scope)
(Migrated to Changes/Ryu)
 
(22 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
  
= Feature Name <!-- The name of your feature --> =
+
= Ryu Network Operating System <!-- The name of your feature --> =
Ryu Network Operating System
+
http://www.osrg.net/ryu/
+
  
 
== Summary ==
 
== Summary ==
 
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
 
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
Ryu Network Operating System
+
Ryu Network Operating System http://osrg.github.com/ryu/
  
 
== Owner ==
 
== Owner ==
Line 20: Line 18:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/18 | Fedora 18 ]]  
+
* Targeted release: [[Releases/20 | Fedora 20 ]]  
* Last updated: 2013-Jan-08
+
* Last updated: 2013-03-18
 
* Percentage of completion: 90%
 
* Percentage of completion: 90%
  
Line 28: Line 26:
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 +
Ryu is an Operating System for Software Defined Networking.
 +
 +
Ryu aims to provide a logically centralized control and well defined
 +
API that make it easy for operators to create new network management
 +
and control applications. Currently, Ryu manages network devices by
 +
using OpenFlow. You can say that Ryu is an OpenFlow Controller.
 +
 +
For Software Defined Networking or OpenFlow, please refer to
 +
[https://www.opennetworking.org/ Open Networking Foundation]
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 35: Line 42:
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
* ryu vlan support: 90%
+
task:
 +
Ryu development:
 +
* vlan support: 100% DONE
 +
* Ryu plugin support for Openstack Qauntum: keeping update for its development
 +
 
 +
packaging:
 +
* rpm package: available at [http://sourceforge.net/projects/ryu/files/Packages/Fedora/]
 +
* rpm package review [https://bugzilla.redhat.com/show_bug.cgi?id=909674] Work In Progress
 +
* make sure that it works with dependent Fedora package. Especially OpenStack and Open vSwitch
  
 
== How To Test ==
 
== How To Test ==
Line 51: Line 66:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
Typical usecase is with OpenStack.
 +
* Install OpenStack package with Quantum enabled and configure them.
 +
* install Ryu from package
 +
* [https://github.com/osrg/ryu/wiki/RYU-OpenStack-Grizzly-environment-VM-image-file-HOWTO Ryu Openstack Grizzly environment HOWTO] explains how to configure Ryu and Grizzly release of OpenStack and expected results
 +
* [https://github.com/osrg/ryu/wiki/RYU-Openstack-Folsom-environment-HOWTO RYU Openstack Folsom environment HOWTO] explains how to configure Ryu and Folsom release of OpenStack and expected results
  
 
== User Experience ==
 
== User Experience ==
Line 64: Line 84:
 
== Contingency Plan ==
 
== Contingency Plan ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 +
 +
This feature can be removed entirely as contingency plan because no other package depends on this.
 +
OpenStack can work without Ryu.(With Ryu, it can provide better features.)
  
 
== Documentation ==
 
== Documentation ==
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
* http://www.osrg.net/ryu
+
* http://osrg.github.com/ryu/
 +
* https://github.com/osrg/ryu/wiki
 +
* http://osrg.github.com/ryu/doc/index.html
  
 
== Release Notes ==
 
== Release Notes ==
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*
+
* Ryu is added for building block as OpenFlow controller for Software Defined Networking. It provides L2-isolated network with OpenStack.
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==

Latest revision as of 13:39, 3 July 2013


Contents

[edit] Ryu Network Operating System

[edit] Summary

Ryu Network Operating System http://osrg.github.com/ryu/

[edit] Owner

  • Email: yamahata at private email ne jp

[edit] Current status

  • Targeted release: Fedora 20
  • Last updated: 2013-03-18
  • Percentage of completion: 90%


[edit] Detailed Description

Ryu is an Operating System for Software Defined Networking.

Ryu aims to provide a logically centralized control and well defined API that make it easy for operators to create new network management and control applications. Currently, Ryu manages network devices by using OpenFlow. You can say that Ryu is an OpenFlow Controller.

For Software Defined Networking or OpenFlow, please refer to Open Networking Foundation

[edit] Benefit to Fedora

Now Fedora (Fedora 17) includes OpenStack (and Open vSwitch). Ryu brings open source openflow controller which can cooperates well with OpenStack.

[edit] Scope

task: Ryu development:

  • vlan support: 100% DONE
  • Ryu plugin support for Openstack Qauntum: keeping update for its development

packaging:

  • rpm package: available at [1]
  • rpm package review [2] Work In Progress
  • make sure that it works with dependent Fedora package. Especially OpenStack and Open vSwitch

[edit] How To Test

Typical usecase is with OpenStack.

[edit] User Experience

With openstack nova/quantum, users can build cloud system with multi tenant network support with open vswitch.

[edit] Dependencies

openstack nova openstack quantum openvswitch

[edit] Contingency Plan

This feature can be removed entirely as contingency plan because no other package depends on this. OpenStack can work without Ryu.(With Ryu, it can provide better features.)

[edit] Documentation

[edit] Release Notes

  • Ryu is added for building block as OpenFlow controller for Software Defined Networking. It provides L2-isolated network with OpenStack.

[edit] Comments and Discussion