summaryrefslogtreecommitdiffstats
path: root/docs/results/overview.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/results/overview.rst')
-rw-r--r--docs/results/overview.rst36
1 files changed, 33 insertions, 3 deletions
diff --git a/docs/results/overview.rst b/docs/results/overview.rst
index 30834d7f6..2515703bf 100644
--- a/docs/results/overview.rst
+++ b/docs/results/overview.rst
@@ -21,6 +21,10 @@ This document is part of deliverables of the OPNFV release brahmaputra.1.0
Scope
-----
+.. _Dashboard: http://130.211.154.108/grafana/dashboard/db/yardstick-main
+.. _Jenkins: https://build.opnfv.org/ci/view/yardstick/
+.. _Scenarios: http://130.211.154.108/grafana/dashboard/db/yardstick-scenarios
+
This document provides an overview of the results of test cases developed by
the OPNFV Yardstick Project, executed on OPNFV community labs.
@@ -30,8 +34,8 @@ automated via Jenkins Jobs.
Test results are visible in the following dashboard:
-* *Yardstick Dashboard*: uses influx DB to store test results and Grafana for
- visualization
+* *Yardstick* Dashboard_: uses influx DB to store test results and Grafana for
+ visualization (user: opnfv/ password: opnfv)
References
@@ -42,9 +46,35 @@ References
* OPNFV Brahamputra release note for Yardstick.
+
General
=======
+Yardstick Test Cases have been executed for scenarios and features defined in
+this OPNFV release.
+
+The test environments were installed by one of the following: Apex, Compass,
+Fuel or Joid; one single installer per POD.
+
+The results of executed tests are available in Dashboard_ and all logs stored
+in Jenkins_.
+
+After one week of measurments, in general, SDN ONOS showed lower latency than
+SDN ODL, which showed lower latency than an environment installed with pure
+OpenStack. Additional time and PODs make this a non-conclusive statement, see
+Scenarios_ for a snapshot and Dashboard_ for complete results.
+
+It was not possible to execute the entire Yardstick test cases suite on the
+PODs assigned for release verification over a longer period of time, due to
+continuous work on the software components and blocking faults either on
+environment, feature or test framework.
+
+Four consecutive successful runs was defined as criteria for release.
+It is a recommendation to run Yardstick test cases over a longer period
+of time in order to better understand the behavior of the system.
+
+
+
Document change procedures and history
--------------------------------------
@@ -58,7 +88,7 @@ Document change procedures and history
| **Release designation** | Brahmaputra |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | 2016-02-25 |
+| **Release date** | Feb 25th, 2016 |
| | |
+--------------------------------------+--------------------------------------+
| **Purpose of the delivery** | OPNFV Brahmaputra release test |