aboutsummaryrefslogtreecommitdiffstats
path: root/docs/development/design/architecture.rst
diff options
context:
space:
mode:
authorMiguel Lavalle <malavall@us.ibm.com>2017-05-31 14:58:39 -0500
committerBrady Johnson <brady.allen.johnson@ericsson.com>2017-06-28 15:47:43 +0000
commita40da17faa6c0d2c7d2dcf43076c6a5b8491df4a (patch)
treeaa044efd65c906986d96075c74fd60f53cfbad15 /docs/development/design/architecture.rst
parent483a4c6862a56a183a61e61f7dcec6bd574e89b2 (diff)
Fix typos and other errors in documentation
While reading the documentation, I found typos and other errors. This patchset fixes them. Change-Id: I2bf83a26da58845337dd77e56a8c77aa63084f2f Signed-off-by: Miguel Lavalle <malavall@us.ibm.com>
Diffstat (limited to 'docs/development/design/architecture.rst')
-rw-r--r--docs/development/design/architecture.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/development/design/architecture.rst b/docs/development/design/architecture.rst
index 98520ecf..b190a18f 100644
--- a/docs/development/design/architecture.rst
+++ b/docs/development/design/architecture.rst
@@ -65,8 +65,8 @@ NSP (NSH Path)
NSI (NSH Index)
The NSI is the Hop in the Service Chain. The NSI starts at 255 and is
- decremented by every SF. If the NSI reaches 0, then the packet is dropped
- which avoids loop detections.
+ decremented by every SF. If the NSI reaches 0, then the packet is dropped,
+ which avoids loops.
NSH also has metadata fields, but that's beyond the scope of this architecture.
@@ -88,7 +88,7 @@ VNF Manager
In OPNFV SFC, a VNF Manager is needed to spin-up VMs for Service Functions.
It has been decided to use the OpenStack Tacker VNF Mgr to spin-up and manage
-the life cylcle of the SFs. Tacker will receive the ODL SFC configuration,
+the life cycle of the SFs. Tacker will receive the ODL SFC configuration,
manage the SF VMs, and forward the configuration to ODL SFC. The following
sequence diagram details the interactions with the VNF Mgr:
@@ -105,7 +105,7 @@ The following image details the Network Topology used in OPNFV Danube SFC:
OVS NSH patch workaround
++++++++++++++++++++++++
-When using NSH with VXLAN tunnels, its important that the VXLAN tunnel is
+When using NSH with VXLAN tunnels, it is important that the VXLAN tunnel is
terminated in the SF VM. This allows the SF to see the NSH header, allowing
it to decrement the NSI and also to use the NSH metadata. When using VXLAN with
OpenStack, the tunnels are not terminated in the VM, but in the "br-int" OVS