From d95a132d3c768e8f25c93ad6e90ea94f94cdbddc Mon Sep 17 00:00:00 2001 From: csatari Date: Fri, 10 Feb 2017 10:01:22 +0100 Subject: Correction of comments to Georedundancy This change contains the corrections to the comments of Prakash to change 28243. Change-Id: I80f2767815c6d1507b133368c4638a0733a64636 Signed-off-by: csatari --- .../requirements/use_cases/georedundancy.rst | 2 +- .../use_cases/georedundancy_regions_insances.rst | 54 ---------------------- .../use_cases/georedundancy_regions_instances.rst | 54 ++++++++++++++++++++++ 3 files changed, 55 insertions(+), 55 deletions(-) delete mode 100644 docs/development/requirements/use_cases/georedundancy_regions_insances.rst create mode 100644 docs/development/requirements/use_cases/georedundancy_regions_instances.rst diff --git a/docs/development/requirements/use_cases/georedundancy.rst b/docs/development/requirements/use_cases/georedundancy.rst index 35336bd..183b8d1 100644 --- a/docs/development/requirements/use_cases/georedundancy.rst +++ b/docs/development/requirements/use_cases/georedundancy.rst @@ -62,7 +62,7 @@ The result of the deployment is shown in the following figure .. toctree:: georedundancy_cells.rst - georedundancy_regions_insances.rst + georedundancy_regions_instances.rst Conclusion ---------- diff --git a/docs/development/requirements/use_cases/georedundancy_regions_insances.rst b/docs/development/requirements/use_cases/georedundancy_regions_insances.rst deleted file mode 100644 index c2550eb..0000000 --- a/docs/development/requirements/use_cases/georedundancy_regions_insances.rst +++ /dev/null @@ -1,54 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -Connection between different OpenStack regions or cloud instances ------------------------------------------------------------------ - -Description -~~~~~~~~~~~ -There should be an API to manage the infrastructure networks between two -OpenStack regions or instances. - -The following figure (:numref:`instances-architecture`) shows the architecture -of the most relevant OpenStack components in multi instance OpenStack -environment. - -.. figure:: images/instances-architecture.png - :name: instances-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. - -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. diff --git a/docs/development/requirements/use_cases/georedundancy_regions_instances.rst b/docs/development/requirements/use_cases/georedundancy_regions_instances.rst new file mode 100644 index 0000000..679f4bb --- /dev/null +++ b/docs/development/requirements/use_cases/georedundancy_regions_instances.rst @@ -0,0 +1,54 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + +Connection between different OpenStack regions or cloud instances +----------------------------------------------------------------- + +Description +~~~~~~~~~~~ +There should be an API to manage the infrastructure networks between two +OpenStack regions or instances. + +The following figure (:numref:`instances-architecture`) shows the architecture +of the most relevant OpenStack components in multi instance OpenStack +environment. + +.. figure:: images/instances-architecture.png + :name: instances-architecture + :width: 50% + +The functionality behind the API depends on the underlying network providers (SDN +controllers) and the networking setup. +(For example both OpenDaylight and ONOS have an API to add new BGP neighbors.) + +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. + +Data model objects +++++++++++++++++++ +- local and remote endpoint objects (Most probably IP addresses with some + additional properties, like local or remote Autonomus Systems (AS)). + +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. -- cgit 1.2.3-korg