diff options
| author |   csatari <gergely.csatari@nokia.com> | 2016-06-23 10:06:33 +0200 |
|---|---|---|
| committer | csatari <gergely.csatari@nokia.com> | 2016-06-23 10:06:33 +0200 |
| commit | 8a300e0a93a2b2f49710fafb9959a9dc8ae2fff8 (patch) | |
| tree | 274303e5eb45ea1d23243904f77e3c8cc33ab43f /docs/requirements/use_cases/georedundancy_regions_insances.rst | |
| parent | 9b92f2199892ce418c0a769110900e0acbbd64c1 (diff) | |
Georedundancy reorganization and enhancement to the introduction
- Use case structure reorganized again
- A new, georedundancy.rst has been created (as in L3VPN case)
- Parent chapter (2.4) for all geuredundancy usecases added (as in L3VPN case)
- Introduction moved to the parent chapter (2.4)
- Learnings of the OPNFV Summit netready breakout added to the intro of the use cases
Change-Id: I8260269f6a2b981e9a0f226e11bed5f3cecf8b3b
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.rst | 13 |
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 |