From a973062e984d73b04f71790af4ed1fa05172ec71 Mon Sep 17 00:00:00 2001 From: Georg Kunz Date: Tue, 19 Jul 2016 14:26:16 +0200 Subject: Working on comments and document cleanup Commenting out some of my previous comments so that they are not part of the final document but remain in the source code. Added conclusion to L3VPN use cases. Change-Id: I1f51cbce1fb496d05d005cfd440cc16a52eab0d8 Signed-off-by: Georg Kunz --- docs/requirements/use_cases/georedundancy_cells.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/requirements/use_cases/georedundancy_cells.rst') diff --git a/docs/requirements/use_cases/georedundancy_cells.rst b/docs/requirements/use_cases/georedundancy_cells.rst index c71d2de..36964ac 100644 --- a/docs/requirements/use_cases/georedundancy_cells.rst +++ b/docs/requirements/use_cases/georedundancy_cells.rst @@ -15,12 +15,12 @@ problem between the main cell and the sub cells. 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 neighbour.) +(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. -Derrived Requirements +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 -- cgit 1.2.3-korg