summaryrefslogtreecommitdiffstats
path: root/docs/design/specs/High-Priority-Traffic-Path.rst
diff options
context:
space:
mode:
authorChristopherPrice <christopher.price@ericsson.com>2016-08-18 11:04:38 +0200
committerChristopherPrice <christopher.price@ericsson.com>2016-08-19 14:56:07 +0200
commit33c5e8c359ed51349a3810f68886a25f6fc10f79 (patch)
treeac5022d899a729fa6eb0036d5f7c5ffdc227e1b7 /docs/design/specs/High-Priority-Traffic-Path.rst
parent55ef39e7796633029e5a3e061532e0984c2be798 (diff)
Adding ovsnfv scenario docs
Copied these docs from https://gerrit.opnfv.org/gerrit/#/c/18563/ These should be in the feature/scenarion project repo for better information control by the projects. Added some notes to the installer links indicating they need to be updated when the final URL's are available. co-author: Billy O'Mahony <billy.o.mahony@intel.com> Change-Id: I21bfca06e4a8d117bb10b7b79504eb20aa62d4b7 Signed-off-by:Christopher Price <christopher.price@ericsson.com>
Diffstat (limited to 'docs/design/specs/High-Priority-Traffic-Path.rst')
-rw-r--r--docs/design/specs/High-Priority-Traffic-Path.rst10
1 files changed, 4 insertions, 6 deletions
diff --git a/docs/design/specs/High-Priority-Traffic-Path.rst b/docs/design/specs/High-Priority-Traffic-Path.rst
index 6243cbe..4000133 100644
--- a/docs/design/specs/High-Priority-Traffic-Path.rst
+++ b/docs/design/specs/High-Priority-Traffic-Path.rst
@@ -1,8 +1,6 @@
-..
- This work is licensed under a Creative Commons Attribution 3.0 Unported
- License.
-
- http://creativecommons.org/licenses/by/3.0/legalcode
+.. This work is licensed under a Creative Commons Attribution 3.0 Unported
+.. License.
+.. http://creativecommons.org/licenses/by/3.0/legalcode
==========================================
High Priority Traffic Path
@@ -207,7 +205,7 @@ prioritization scheme that is developed.
Tests should be performed for each combination of:
* Packet Sizes in (64, 512)
-* Total Offered Rate in (80, 120, 150)
+* Total Offered Rate in (80, 120, 150)
* rate_ingress_b(n) / rate_ingress_a(n) in (0.1, 0.2, 0.5)
For each set, the following metrics should be collected for each traffic