summaryrefslogtreecommitdiffstats
path: root/docs/requirements/use_cases/georedundancy_regions_insances.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/requirements/use_cases/georedundancy_regions_insances.rst')
-rw-r--r--docs/requirements/use_cases/georedundancy_regions_insances.rst8
1 files changed, 8 insertions, 0 deletions
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.)