FDS DVR doc - Updated flow diagram for LISP

Change-Id: I2e792f1695327ab59af8f7afa0ffcfb8caecd5e4
Signed-off-by: Lorand Jakab <lojakab@cisco.com>

diff --git a/docs/scenarios/os-odl-fdio-dvr-noha/FDS-simple-callflow.png b/docs/scenarios/os-odl-fdio-dvr-noha/FDS-simple-callflow.png
old mode 100755 (executable)
new mode 100644 (file)
index 04546aa..ffba720
Binary files a/docs/scenarios/os-odl-fdio-dvr-noha/FDS-simple-callflow.png and b/docs/scenarios/os-odl-fdio-dvr-noha/FDS-simple-callflow.png differ

diff --git a/docs/scenarios/os-odl-fdio-dvr-noha/scenario.description.rst b/docs/scenarios/os-odl-fdio-dvr-noha/scenario.description.rst
index 53969bb..30a6f7a 100755 (executable)
--- a/docs/scenarios/os-odl-fdio-dvr-noha/scenario.description.rst
+++ b/docs/scenarios/os-odl-fdio-dvr-noha/scenario.description.rst
@@ -234,8 +234,6 @@ To provide a better understanding how the above mentioned components interact
 with each other, the following diagram shows how the example of creating a
 vhost-user port on VPP through Openstack Neutron:
 
-TODO: Add LISP components to diagram
-
 .. image:: FDS-simple-callflow.png
 
 DHCP Packet Flow