summaryrefslogtreecommitdiffstats
path: root/docs/requirements/use_cases/georedundancy.rst
blob: 513eee19e92b6a93b5119ac659d6963730cc2f59 (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
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0

Georedundancy Use cases (Draft)
===============================
Connection between different OpenStack cells
--------------------------------------------
Description
~~~~~~~~~~~
There should be an API to manage the infrastructure-s networks between two OpenStack cells.
(Note: In the Mitaka release of OpenStack cells v1 are considered as, cells v2 functionaity is under implementation)

Derrived Requirements
~~~~~~~~~~~~~~~~~~~~~
   - Possibility to define a remote and a local endpoint
   - Possiblity to define an overlay/segregation technology
   - 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.)


Data model objects
++++++++++++++++++
   - TBD

Orchestration
+++++++++++++
   - TBD

Dependencies on compute services
++++++++++++++++++++++++++++++++
   - TBD

Potential implementation
++++++++++++++++++++++++
   - TBD

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)

Derrived 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