summaryrefslogtreecommitdiffstats
path: root/docs/requirements/use_cases/l3vpn_ecmp.rst
diff options
context:
space:
mode:
authorGeorg Kunz <georg.kunz@ericsson.com>2016-10-31 22:24:52 +0100
committerGeorg Kunz <georg.kunz@ericsson.com>2016-11-11 09:19:30 +0000
commit7e922675b35bab185ccf99a68637dbfdf877cdf4 (patch)
tree5ddb71cd91bdc654a50dd987262d15b735928c6e /docs/requirements/use_cases/l3vpn_ecmp.rst
parent01b644db5e301278aa4ab8863f8d439eb5a75b90 (diff)
Formatting changes and fixing of build warnings
Applying a different sphinx rendering theme to make the document more readable (in my opinion). The Sphinx config file is based on the config file of the Copper project. Moreover, this change fixes a few build-time warnings. Change-Id: I78f5268436edcfa8c71b8e85a99c7caa54a0e099 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com> (cherry picked from commit 12542964182af4da4daeb58219377a5d1f697ecf)
Diffstat (limited to 'docs/requirements/use_cases/l3vpn_ecmp.rst')
-rw-r--r--docs/requirements/use_cases/l3vpn_ecmp.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/requirements/use_cases/l3vpn_ecmp.rst b/docs/requirements/use_cases/l3vpn_ecmp.rst
index 7bcb64f..93f5234 100644
--- a/docs/requirements/use_cases/l3vpn_ecmp.rst
+++ b/docs/requirements/use_cases/l3vpn_ecmp.rst
@@ -135,14 +135,14 @@ Gaps in the current solution
Given the use case description and the currently available implementation in
OpenStack provided by BGPVPN project, we identify the following gaps:
-* [L3VPN-ECMP-GAP1] Static routes are not yet supported by the BGPVPN project.
+* **[L3VPN-ECMP-GAP1] Static routes are not yet supported by the BGPVPN project.**
Currently, no API for configuring static routes is available in the BGPVPN
project. This feature is on the road map, however.
-* [L3VPN-ECMP-GAP2] Behavior not defined for multiple Neutron ports of the same
- IP
+* **[L3VPN-ECMP-GAP2] Behavior not defined for multiple Neutron ports of the same
+ IP**
The Neutron and BGPVPN API allow for creating multiple ports with the same
IP in different networks and associating the networks with the same VPN. The
@@ -151,8 +151,8 @@ OpenStack provided by BGPVPN project, we identify the following gaps:
of this feature is on the road map of the project, however.
-* [L3VPN-ECMP-GAP3] It is not possible to assign the same IP to multiple Neutron
- ports within the same Neutron subnet.
+* **[L3VPN-ECMP-GAP3] It is not possible to assign the same IP to multiple Neutron
+ ports within the same Neutron subnet.**
This is due to the fundamental requirement of avoiding IP collisions within
the L2 domain which is a Neutron network.