3 files changed, 18 insertions, 0 deletions

diff --git a/docs/requirements/use_cases/georedundancy_cells.rst b/docs/requirements/use_cases/georedundancy_cells.rst
index 23fcb8d..95ffc6f 100644
--- a/docs/requirements/use_cases/georedundancy_cells.rst
+++ b/docs/requirements/use_cases/georedundancy_cells.rst
@@ -25,6 +25,24 @@ This set of georedundancy use cases is about enabling the possiblity to select a
 backup datacenter and build the connectivity between the NFVI-s in the
 different datacenters in a programmable way.
 
+As an example the following picture (:numref:`georedundancy-before`) shows a
+multicell cloud setup where the underlay network is not fully mashed.
+
+.. figure:: images/georedundancy-before.png
+    :name:  georedundancy-before
+    :width: 25%
+
+Each datacenter (DC) is a separate OpenStack cell, region or instance. Let's
+assume that a new VNF is started in DC b with a Redundant VNF in DC d. In this
+case a direct underlay network connection is needed between DC b and DC d. The
+configuration of this connection should be programable in both DC b and DC d.
+The result of the deployment is shown in the following figure
+(:numref:`georedundancy-after`):
+
+.. figure:: images/georedundancy-after.png
+   :name:  georedundancy-after
+   :width: 25%
+
 Description
 ^^^^^^^^^^^
 There should be an API to manage the infrastructure-s networks between two
diff --git a/docs/requirements/use_cases/images/georedundancy-after.png b/docs/requirements/use_cases/images/georedundancy-after.png
new file mode 100644
index 0000000..e02c7cd
--- /dev/null
+++ b/docs/requirements/use_cases/images/georedundancy-after.png
diff --git a/docs/requirements/use_cases/images/georedundancy-before.png b/docs/requirements/use_cases/images/georedundancy-before.png
new file mode 100644
index 0000000..3efbbe6
--- /dev/null
+++ b/docs/requirements/use_cases/images/georedundancy-before.png