openstack
/
dragonflow
Code Issues Proposed changes

Fix image links in README 

Change-Id: I651be6bb9f16311f50d5a95b4981c866423d97b5
This commit is contained in:
Gal Sagie 2015-03-22 17:19:07 +02:00
parent a35bf7640a
commit 932b76753b
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.rst
View File

@ -19,7 +19,7 @@ In OpenFlow these rules are called flows. To put this simply, the virtual router
Dragonflow eliminate the use of namespaces in contrast to the standard DVR, a diagram showing Dragonflow components and overall architecture can be seen here:
![Solution Overview](https://github.com/stackforge/dragonflow/tree/master/doc/images/df_components.jpg)
![Solution Overview](https://github.com/stackforge/dragonflow/blob/master/doc/images/df_components.jpg)
Perhaps the most important part of the solution is the OpenFlow pipeline which we install into the integration bridge upon bootstrap.
This is the flow that controls all traffic in the OVS integration bridge `(br-int)`.
@ -37,9 +37,9 @@ The pipeline works in the following manner:
The following diagram shows the multi-table OpenFlow pipeline installed into the OVS integration bridge `(br-int)` in order to represent the virtual router using flows only:
![Openflow pipeline](https://github.com/stackforge/dragonflow/tree/master/doc/images/df_of_pipeline.jpg)
![Openflow pipeline](https://github.com/stackforge/dragonflow/blob/master/doc/images/df_of_pipeline.jpg)
** A detailed blog post describing the solution can be found Here_.
A detailed blog post describing the solution can be found Here_.
.. _Here: http://blog.gampel.net/2015/01/neutron-dvr-sdn-way.html