blob: e1673a60867d46bfd4594469cb0952cef954fa7a (
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
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
Connection between different OpenStack cells
--------------------------------------------
Description
~~~~~~~~~~~
There should be an API to manage the infrastructure networks between two
OpenStack cells. (Note: In the Mitaka release of OpenStack cells v1 are
considered as experimental, while cells v2 functionality is under
implementation). Cells are considered to be problematic from maintainability
perspective as the sub-cells are using only the internal message bus and there
is no API (and CLI) to do maintenance actions in case of a network connectivity
problem between the main cell and the sub cells.
The following figure (:numref:`cells-architecture`) shows the architecture of
the most relevant OpenStack components in multi cell OpenStack environment.
.. figure:: images/cells-architecture.png
:name: cells-architecture
:width: 50%
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 neighbor.)
OpenStack Neutron should provide an abstracted API for this functionality what
calls the underlying SDN controllers API.
Derived Requirements
~~~~~~~~~~~~~~~~~~~~~
- 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
- API call to define the remote and local infrastructure endpoints
- When the endpoints are created neutron is configured to use the new network.
Dependencies on compute services
++++++++++++++++++++++++++++++++
None.
Data model objects
++++++++++++++++++
- 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 Tricircle project [TRICIRCLE]_
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.
|
