summaryrefslogtreecommitdiffstats
path: root/docs/requirements/use_cases/georedundancy_regions_insances.rst
blob: 408b42529f933d5b9a2e0e2d41b941fe2da90f38 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
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