summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorcsatari <gergely.csatari@nokia.com>2016-06-17 13:09:19 +0200
committercsatari <gergely.csatari@nokia.com>2016-06-21 14:51:08 +0200
commit9b92f2199892ce418c0a769110900e0acbbd64c1 (patch)
tree7c100b612c467fa3390c8e690115c5b3cb1d8f7b
parenta6bdd13709870b864d57454200798a3a028012fa (diff)
Adding explanatory images to the introduction.
Adding the images and separating the usecases to separate files. Change-Id: Ic45a5d3f15bf3a2b38695e94b6910ec60455727d Signed-off-by: csatari <gergely.csatari@nokia.com>
-rw-r--r--docs/requirements/use_cases/georedundancy_cells.rst18
-rw-r--r--docs/requirements/use_cases/images/georedundancy-after.pngbin0 -> 9122 bytes
-rw-r--r--docs/requirements/use_cases/images/georedundancy-before.pngbin0 -> 7695 bytes
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
Binary files differ
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
Binary files differ