summaryrefslogtreecommitdiffstats
path: root/docs/requirements/use_cases/georedundancy_regions_insances.rst
diff options
context:
space:
mode:
authorcsatari <gergely.csatari@nokia.com>2016-07-01 11:19:54 +0200
committercsatari <gergely.csatari@nokia.com>2016-07-05 11:22:57 +0200
commit791354a57e2e6c6e049877a95cbaecd9d27d6966 (patch)
treee835a62d984bcef2c59ad822220f7799314cd741 /docs/requirements/use_cases/georedundancy_regions_insances.rst
parentd3d984a25934207b9c181e6ce775dae0305252e4 (diff)
Polishing of georedundancy and provider network uc-s
Adding the final touch to my use cases: - Clarification of the introduction text in the general georedundancy capter - Clarification of the description of both the georedundancy and the provider networks use cases - Adding references. Change-Id: I9734154dc7fbb5f3a86af17c451b02cca839a741 Signed-off-by: csatari <gergely.csatari@nokia.com>
Diffstat (limited to 'docs/requirements/use_cases/georedundancy_regions_insances.rst')
-rw-r--r--docs/requirements/use_cases/georedundancy_regions_insances.rst60
1 files changed, 32 insertions, 28 deletions
diff --git a/docs/requirements/use_cases/georedundancy_regions_insances.rst b/docs/requirements/use_cases/georedundancy_regions_insances.rst
index 9e74f74..6683c27 100644
--- a/docs/requirements/use_cases/georedundancy_regions_insances.rst
+++ b/docs/requirements/use_cases/georedundancy_regions_insances.rst
@@ -5,38 +5,42 @@ 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.
+OpenStack regions or instances.
+
+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 neighbour.)
+
+OpenStack Neutron should provide an abstracted API for this functionality what
+calls the underlying SDN controllers API.
Derrived Requirements
-^^^^^^^^^^^^^^^^^^^^^
- - Possibility to define a remote and a local endpoint
- - Possiblity to define an overlay/segregation technology
+~~~~~~~~~~~~~~~~~~~~~
+- Possibility to define a remote and a local endpoint
+- As in case of cells the nova-api service is shared it should be possible
+ to identify the cell in the API calls
Northbound API / Workflow
-"""""""""""""""""""""""""
- - An infrastructure network management API is needed
- - When the endpoints are created neutron is configured to use the new network.
- (Note: Nova networking is not considered as it is deprecated.)
++++++++++++++++++++++++++
+- An infrastructure network management API is needed
+- API call to define the remote and local infrastructure endpoints
+- When the endpoints are created neutron is configured to use the new network.
Data model objects
-""""""""""""""""""
- - TBD
-
-Orchestration
-"""""""""""""
- - TBD
-
-Dependencies on compute services
-""""""""""""""""""""""""""""""""
- - TBD
-
-Potential implementation
-""""""""""""""""""""""""
- - TBD
+++++++++++++++++++
+- local and remote endpoint objects (Most probably IP addresses with some
+additional properties).
+
+Current implementation
+~~~~~~~~~~~~~~~~~~~~~~
+ Current OpenStack implementation provides no way to set up the underlay
+ network connection.
+ OpenStack Tricicle project [TRICICLE]_
+ has plans to build up inter datacenter L2 and L3 networks.
+
+Gaps in the current solution
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ An infrastructure management API is missing from Neutron where the local and
+ remote endpoints of the underlay network could be configured.