summaryrefslogtreecommitdiffstats
path: root/docs/development/design/architecture.rst
diff options
context:
space:
mode:
authorroot <juan.vidal.allende@ericsson.com>2017-03-30 09:42:19 +0000
committerroot <juan.vidal.allende@ericsson.com>2017-03-30 13:03:12 +0000
commite61239dbb4f96bb4b798cd3c6e6d6c953d4fcee4 (patch)
tree39374f192a83aaa7c19c29b6e6ba2c0afd5e90ba /docs/development/design/architecture.rst
parent89b68dcce2e79251e38e6231a3556b1bdc5fea79 (diff)
Remove references to older releases on documentation
- Rename all Brahmaputra/Colorado links to Danube - Bumped OvS version from 2.5.90 to 2.6.1 - Bumped ODL version from Boron to Boron SR2 - Changed release date Change-Id: I4286cbd074b377b4b33e25f33646bb05075f10f5 Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
Diffstat (limited to 'docs/development/design/architecture.rst')
-rw-r--r--docs/development/design/architecture.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/development/design/architecture.rst b/docs/development/design/architecture.rst
index 679bb2f9..98520ecf 100644
--- a/docs/development/design/architecture.rst
+++ b/docs/development/design/architecture.rst
@@ -5,7 +5,7 @@ Architecture
------------
This section describes the architectural approach to incorporating the upstream
-OpenDaylight (ODL) SFC project into the OPNFV Colorado platform.
+OpenDaylight (ODL) SFC project into the OPNFV Danube platform.
Service Functions
+++++++++++++++++
@@ -97,7 +97,7 @@ sequence diagram details the interactions with the VNF Mgr:
OPNFV SFC Network Topology
++++++++++++++++++++++++++
-The following image details the Network Topology used in OPNFV Colorado SFC:
+The following image details the Network Topology used in OPNFV Danube SFC:
.. image:: ./images/OPNFV_SFC_Brahmaputra_NW_Topology.jpg
@@ -113,7 +113,7 @@ bridge. There is work ongoing in the upstream OVS community to implemement NSH
encapsulation. To get around the way OpenStack handles VXLAN tunnels, the OVS
work will also include the ability to encapsulate/decapsulate VXLAN tunnels from
OpenFlow rules, instead of relying on the Vtep ports. The ongoing upstream OVS
-work will not be finished by the time OPNFV Colorado is released, so
+work will not be finished by the time OPNFV Danube is released, so
a work-around has been created. This work-around will use a private branch of
OVS that has a preliminary version of NSH implemented.