Test results for apex and joid

Adds test results for apex-odl-l2 and joid-odl-l2 scenarios.

Change-Id: I76869112a8225ff33d19cde179b2e6ca7e988fd4
Signed-off-by: Ana C <ana.cunha@ericsson.com>
(cherry picked from commit 19e624d300a77f4176aa465bda34f63012bb199d)

diff --git a/docs/results/apex-os-odl_l2-nofeature-ha.rst b/docs/results/apex-os-odl_l2-nofeature-ha.rst
index c7aef3e..1477e2a 100644 (file)
--- a/docs/results/apex-os-odl_l2-nofeature-ha.rst
+++ b/docs/results/apex-os-odl_l2-nofeature-ha.rst
@@ -14,25 +14,93 @@ Test Results for apex-os-odl_l2-nofeature-ha
 Details
 =======
 
-.. after this doc is filled, remove all comments and include the scenario in
-.. results.rst by removing the comment on the file name.
-
+.. _Dashboard: http://130.211.154.108/grafana/dashboard/db/yardstick-main
+.. _POD1: https://wiki.opnfv.org/pharos_rls_b_labs
 
 Overview of test results
 ------------------------
 
-.. general on metrics collected, number of iterations
+See Dashboard_ for viewing test result metrics for each respective test case.
+
+All of the test case results below are based on scenario test runs on the
+LF POD1, between February 19 and February 24.
+
+TC002
+-----
+
+The round-trip-time (RTT) between 2 VMs on different blades is measured using
+ping.
+
+The results for the observed period show minimum 0.37ms, maximum 0.49ms,
+average 0.45ms.
+SLA set to 10 ms, only used as a reference; no value has yet been defined by
+OPNFV.
+
+TC005
+-----
+
+The IO read bandwidth for the observed period show average between 124KB/s and
+129 KB/s, with a minimum 372KB/s and maximum 448KB/s.
+
+SLA set to 400KB/s, only used as a reference; no value has yet been defined by
+OPNFV.
+
+TC010
+-----
+
+The measurements for memory latency for various sizes and strides are shown in
+Dashboard_. For 48MB, the minimum is 22.75 and maximum 30.77 ns.
+
+SLA set to 30 ns, only used as a reference; no value has yet been defined by
+OPNFV.
+
+TC011
+-----
+
+Packet delay variation between 2 VMs on different blades is measured using
+Iperf3.
+
+The mimimum packet delay variation measured is 2.5us and the maximum 8.6us.
+
+TC012
+-----
+
+See Dashboard_ for results.
+
+SLA set to 15 GB/s, only used as a reference, no value has yet been defined by
+OPNFV.
+
+TC014
+-----
+
+The Unixbench processor single and parallel speed scores show scores between
+3625 and 3660.
+
+No SLA set.
+
+TC037
+-----
+
+See Dashboard_ for results.
 
 Detailed test results
 ---------------------
 
-.. info on lab, installer, scenario
+The scenario was run on LF POD1_ with:
+Apex
+ODL Beryllium
+
 
 Rationale for decisions
 -----------------------
-.. result analysis, pass/fail
+
+Pass
+
+Tests were successfully executed and metrics collected.
+No SLA was verified. To be decided on in next release of OPNFV.
 
 Conclusions and recommendations
 -------------------------------
 
-.. did the expected behavior occured?
+Execute tests over a longer period of time, with time reference to versions of
+components, for allowing better understanding of the behavior of the system.

diff --git a/docs/results/joid-os-odl_l2-nofeature-ha.rst b/docs/results/joid-os-odl_l2-nofeature-ha.rst
index 782950b..ff28908 100644 (file)
--- a/docs/results/joid-os-odl_l2-nofeature-ha.rst
+++ b/docs/results/joid-os-odl_l2-nofeature-ha.rst
@@ -14,25 +14,84 @@ Test Results for joid-os-odl_l2-nofeature-ha
 Details
 =======
 
-.. after this doc is filled, remove all comments and include the scenario in
-.. results.rst by removing the comment on the file name.
+.. _Dashboard: http://130.211.154.108/grafana/dashboard/db/yardstick-main
+.. _POD2: https://wiki.opnfv.org/pharos_rls_b_labs
 
 
 Overview of test results
 ------------------------
 
-.. general on metrics collected, number of iterations
+See Dashboard_ for viewing test result metrics for each respective test case.
+
+All of the test case results below are based on scenario test runs on the
+Orange POD2, between February 23 and February 24.
+
+TC002
+-----
+
+See Dashboard_ for results.
+SLA set to 10 ms, only used as a reference; no value has yet been defined by
+OPNFV.
+
+TC005
+-----
+
+See Dashboard_ for results.
+SLA set to 400KB/s, only used as a reference; no value has yet been defined by
+OPNFV.
+
+TC010
+-----
+
+Not executed, missing in the test suite used in the POD during the observed
+period.
+
+TC011
+-----
+
+Not executed, missing in the test suite used in the POD during the observed
+period.
+
+
+TC012
+-----
+
+Not executed, missing in the test suite used in the POD during the observed
+period.
+
+
+TC014
+-----
+
+Not executed, missing in the test suite used in the POD during the observed
+period.
+
+
+TC037
+-----
+
+See Dashboard_ for results.
+
 
 Detailed test results
 ---------------------
 
-.. info on lab, installer, scenario
+The scenario was run on Orange POD2_ with:
+Joid
+ODL Beryllium
 
 Rationale for decisions
 -----------------------
-.. result analysis, pass/fail
+
+Pass
+
+Most tests were successfully executed and metrics collected, the non-execution
+of above-mentioned tests was due to test cases missing in the Jenkins Job used
+in the POD, during the observed period.
+No SLA was verified. To be decided on in next release of OPNFV.
 
 Conclusions and recommendations
 -------------------------------
 
-.. did the expected behavior occured?
+Execute tests over a longer period of time, with time reference to versions of
+components, for allowing better understanding of the behavior of the system.