Separating the georedundancy use cases to separate files.

Small corrections to both georedundancy and progamable provisioning.

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

1 files changed, 39 insertions, 0 deletions

diff --git a/docs/requirements/use_cases/georedundancy_regions_insances.rst b/docs/requirements/use_cases/georedundancy_regions_insances.rst
new file mode 100644
index 0000000..408b425
--- /dev/null
+++ b/docs/requirements/use_cases/georedundancy_regions_insances.rst
@@ -0,0 +1,39 @@
+.. 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
+--------------------------------------------------------------------------------
+
+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)
+
+Requirements
+^^^^^^^^^^^^
+   - Possibility to define a remote and a local endpoint
+   - Possiblity to define an overlay/segregation technology
+
+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.)
+
+
+Data model objects
+""""""""""""""""""
+   - TBD
+
+Orchestration
+"""""""""""""
+   - TBD
+
+Dependencies on compute services
+""""""""""""""""""""""""""""""""
+   - TBD
+
+Potential implementation
+""""""""""""""""""""""""
+   - TBD