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.rst13
1 files changed, 8 insertions, 5 deletions
diff --git a/docs/requirements/use_cases/georedundancy_regions_insances.rst b/docs/requirements/use_cases/georedundancy_regions_insances.rst
index 408b425..9e74f74 100644
--- a/docs/requirements/use_cases/georedundancy_regions_insances.rst
+++ b/docs/requirements/use_cases/georedundancy_regions_insances.rst
@@ -1,17 +1,21 @@
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
-Georedundancy: Connection between different OpenStack regions or cloud instances
---------------------------------------------------------------------------------
+Connection between different OpenStack regions or cloud instances
+-----------------------------------------------------------------
Description
^^^^^^^^^^^
There should be an API to manage the infrastructure-s networks between two
OpenStack regions or between two OpenStack cloud instances.
(The only difference is the shared keystone in case of a region)
+This capability exists in the different SDN controllers, like the Add New BGP
+neighbour API of OpenDaylight. OpenStack Neutron should provide and abstracted
+API for this functionality what later calls the given SDN controllers related
+API.
-Requirements
-^^^^^^^^^^^^
+Derrived Requirements
+^^^^^^^^^^^^^^^^^^^^^
- Possibility to define a remote and a local endpoint
- Possiblity to define an overlay/segregation technology
@@ -21,7 +25,6 @@ Northbound API / Workflow
- When the endpoints are created neutron is configured to use the new network.
(Note: Nova networking is not considered as it is deprecated.)
-
Data model objects
""""""""""""""""""
- TBD