diff options
Diffstat (limited to 'docs/requirements/use_cases/georedundancy.rst')
| -rw-r--r-- | docs/requirements/use_cases/georedundancy.rst | 75 |
1 files changed, 75 insertions, 0 deletions
diff --git a/docs/requirements/use_cases/georedundancy.rst b/docs/requirements/use_cases/georedundancy.rst new file mode 100644 index 0000000..513eee1 --- /dev/null +++ b/docs/requirements/use_cases/georedundancy.rst @@ -0,0 +1,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 + |