Explanatory figures

Based on the comments of Fathemeh I've added 3 explanatory figures.

Change-Id: Ica4a373ab88979162f064740c6020d0789b20cfe
Signed-off-by: csatari <gergely.csatari@nokia.com>

6 files changed, 23 insertions, 0 deletions

diff --git a/docs/requirements/use_cases/georedundancy_cells.rst b/docs/requirements/use_cases/georedundancy_cells.rst
index 36964ac..ad664e8 100644
--- a/docs/requirements/use_cases/georedundancy_cells.rst
+++ b/docs/requirements/use_cases/georedundancy_cells.rst
@@ -13,6 +13,13 @@ perspective as the sub-cells are using only the internal message bus and there
 is no API (and CLI) to do maintenance actions in case of a network connectivity
 problem between the main cell and the sub cells.
 
+The following figure (:numref:`cells-architecture`) shows the architecture of
+the most relevant OpenStack components in multi cell OpenStack environment.
+
+.. figure:: images/cells-architecture.png
+    :name:  cells-architecture
+    :width: 50%
+
 The functionality behind the API depends on the underlying network providers (SDN
 controllers) and the networking setup.
 (For example OpenDaylight has an API to add new BGP neighbor.)
diff --git a/docs/requirements/use_cases/georedundancy_regions_insances.rst b/docs/requirements/use_cases/georedundancy_regions_insances.rst
index 27eae65..995eb49 100644
--- a/docs/requirements/use_cases/georedundancy_regions_insances.rst
+++ b/docs/requirements/use_cases/georedundancy_regions_insances.rst
@@ -9,6 +9,14 @@ Description
 There should be an API to manage the infrastructure-s networks between two
 OpenStack regions or instances.
 
+The following figure (:numref:`instances-architecture`) shows the architecture
+of the most relevant OpenStack components in multi instance OpenStack
+environment.
+
+.. figure:: images/instances-architecture.png
+    :name:  instances-architecture
+    :width: 50%
+
 The functionality behind the API depends on the underlying network providers (SDN
 controllers) and the networking setup.
 (For example OpenDaylight has an API to add new BGP neighbor.)
diff --git a/docs/requirements/use_cases/images/api-users.png b/docs/requirements/use_cases/images/api-users.png
new file mode 100644
index 0000000..1f08812
--- /dev/null
+++ b/docs/requirements/use_cases/images/api-users.png
diff --git a/docs/requirements/use_cases/images/cells-architecture.png b/docs/requirements/use_cases/images/cells-architecture.png
new file mode 100644
index 0000000..476cf90
--- /dev/null
+++ b/docs/requirements/use_cases/images/cells-architecture.png
diff --git a/docs/requirements/use_cases/images/instances-architecture.png b/docs/requirements/use_cases/images/instances-architecture.png
new file mode 100644
index 0000000..d70de02
--- /dev/null
+++ b/docs/requirements/use_cases/images/instances-architecture.png
diff --git a/docs/requirements/use_cases/programmable_provisioning.rst b/docs/requirements/use_cases/programmable_provisioning.rst
index d66a54c..963451d 100644
--- a/docs/requirements/use_cases/programmable_provisioning.rst
+++ b/docs/requirements/use_cases/programmable_provisioning.rst
@@ -15,6 +15,14 @@ requires additional manual configuration work.  It shall be possible to
 configure provider networks without administrative rights.  It should be
 possible to assign the capability to create provider networks to any roles.
 
+The following figure (:numref:`api-users`) shows the possible users of an
+OpenStack API and the relation of OpenStack and ETSI NFV components. Boxes with
+solid line are the ETSI NFV components while the boxes with broken line are the
+OpenStack components.
+
+.. figure:: images/api-users.png
+    :name:  api-users
+    :width: 50%
 
 Derived Requirements
 ~~~~~~~~~~~~~~~~~~~~~