summaryrefslogtreecommitdiffstats
path: root/docs/com/pres
diff options
context:
space:
mode:
Diffstat (limited to 'docs/com/pres')
-rwxr-xr-xdocs/com/pres/conversation.html61
-rwxr-xr-xdocs/com/pres/testapi.html26
2 files changed, 58 insertions, 29 deletions
diff --git a/docs/com/pres/conversation.html b/docs/com/pres/conversation.html
index 0fab448a2..df14f5142 100755
--- a/docs/com/pres/conversation.html
+++ b/docs/com/pres/conversation.html
@@ -63,7 +63,8 @@
<section data-markdown>
# Who are we?
- ![alt text](https://wiki.opnfv.org/download/attachments/2926690/Testing.png "OPNFV testing group")
+ ![team](../img/OPNFV_testing_group.png)
+ This is a representation...not a governance!
</section>
<section>
<section>
@@ -83,7 +84,7 @@
<tr>
<td>Yardstick</td>
<td>Umbrella project for performance/qualification testing</td>
- </tr>
+ </tr>
<tr>
<td>CPerf</td>
<td>SDN controller performance testing</td>
@@ -98,7 +99,11 @@
</tr>
<tr>
<td>Bottlenecks</td>
- <td>Detect possible bottlenecks </td>
+ <td>Detect possible bottlenecks</td>
+ </tr>
+ <tr>
+ <td>QTIP</td>
+ <td>Benchmark to boost performance</td>
</tr>
</tbody>
</table>
@@ -118,10 +123,10 @@
* Performance testing framework and NFVI Validation
* [Contributors](https://wiki.opnfv.org/display/yardstick/People)
* Yardstick presentation
- * How to Do a Pre-deployment NFVI Validation Quickly and Efficiently? Wednesday, June 22, 4:00 PM - 4:30 PM
- * Yardstick: A Pre-deployment NFVI Validation Tool. Thursday, June 23, 3:10 PM - 3:30 PM
+ * How to Do a Pre-deployment NFVI Validation Quickly and Efficiently? Wednesday, June 22, 4:00 PM - 4:30 PM
+ * Yardstick: A Pre-deployment NFVI Validation Tool. Thursday, June 23, 3:10 PM - 3:30 PM
* breakout sessions
- * Tomorrow 2PM (Yardstick in C)
+ * Tomorrow 2PM (Yardstick in C)
</section>
<section data-markdown>
# CPerf
@@ -131,6 +136,13 @@
</section>
<section data-markdown>
# StorPerf
+ * Cinder Volume Performance Testing
+ * Based on SNIA's SSD Test Specification
+ * Presentation
+ * StorPerf: Cinder Storage Performance Measurement.
+ Wednesday, June 22, 3:40 PM - 3:55 PM
+ * Breakout Session
+ * Tomorrow 10:15 (StorPerf Test Results Working Session)
</section>
<section data-markdown>
# VSPerf
@@ -138,21 +150,38 @@
<section data-markdown>
# Bottlenecks
</section>
+ <section data-markdown>
+ # QTIP
+
+ ## OPNFV Platform Benchmark
+
+ - Bottom up
+ - testing baremetal components first
+ - More than result
+ - comparing against reference
+ - Setup-Test-Diagnose-Improve
+ - a closed loop to boost platform performance
+
+ ## Breakout session
+
+ - 14:30~15:45, June 21st/Tuesday
+ - Room Tegel
+ </section>
</section>
<section>
<section data-markdown>
- # Upstream, upstream, upstream..
+ # Upstream, upstream, upstream..
</section>
<section data-markdown>
## We are on the shoulders of the giants
* Rally (OpenStack)
* ODL, ONOS, ...
* RobotFramework, Teston
- * .....
+ * .....
</section>
<section data-markdown>
- ## Time to give back
- ### How to improve work with testing upstream community
+ ## Time to give back
+ ### How to improve work with testing upstream community
</section>
</section>
@@ -162,20 +191,20 @@
<section data-markdown>
# Towards Telco Cloud KPI?
</section>
-
+
<section data-markdown>
# Testing group goals
* Define common needs (naming, rules, tools...)
- * Unify result collection, reporting, dashboarding, documentation
- * Share best practice: docker, CLI, ..
+ * Unify result collection, reporting, dashboarding, documentation
+ * Share best practice: docker, CLI, ..
* Identify testing domains
- * Encourage testing in poorly covered areas
+ * Encourage testing in poorly covered areas
</section>
<section data-markdown>
# The ultimate goal: define Telco Cloud KPIs
* Provide methodology and test suites to qualify a Telco Cloud
- * Provide reference benchs for plugfest/third party integration: compare apple with apple
+ * Provide reference benchs for plugfest/third party integration: compare apple with apple
</section>
</section>
@@ -186,7 +215,7 @@
</div>
<div class='footer'>
- <img src="../img/logo-OPNFV.png" alt="OPNFV logo">
+ <img src="../img/logo-OPNFV-Berlin.png" alt="OPNFV logo">
</div>
</div>
diff --git a/docs/com/pres/testapi.html b/docs/com/pres/testapi.html
index 37a8ea356..a0e266a19 100755
--- a/docs/com/pres/testapi.html
+++ b/docs/com/pres/testapi.html
@@ -62,9 +62,9 @@
</section>
<section data-markdown>
## Give a consistant view for
+ * Test resources (Pods)
* Test projects
* Test cases
- * Test resources (Pods)
* Test results
</section>
@@ -87,17 +87,9 @@
# API overview
</section>
<section data-markdown>
- ## API in Brahmaputra
- * Tornado + MongoDB
- * Simple data models aggreed with the testing group
- * No unit tests
- * Wiki and rst documentation
- </section>
-
- <section data-markdown>
- ## API in Brahmaputra
+ ## API storage structure
![testapi](https://wiki.opnfv.org/download/attachments/2926452/results_collection_structure.png?version=1&modificationDate=1459196347000&api=v2 "OPNFV API page")
- </section>
+ </section>
<section data-markdown>
## API in Brahmaputra
![testapi](../img/testapi0.png)
@@ -105,6 +97,14 @@
</section>
<section data-markdown>
+ ## API in Brahmaputra
+ * Tornado + MongoDB
+ * Simple data models aggreed with the testing group
+ * No unit tests
+ * Wiki and rst documentation
+ </section>
+
+ <section data-markdown>
## Lessons learned in B.
* Wiki documentation is painful
* Result model too simple
@@ -137,8 +137,8 @@
testresults.opnfv.org/test/testapi => testresults.opnfv.org/test/api/v1
http://testresults.opnfv.org/test/api/v1/projects
- http://testresults.opnfv.org/test/api/v1/projects/yardstick/cases
- http://testresults.opnfv.org/test/api/v1/results?case=Tempest&period=1
+ http://testresults.opnfv.org/test/api/v1/projects/qtip/cases
+ http://testresults.opnfv.org/test/api/v1/results?case=Tempest&period=1
</section>
<section>
<h3>One new field for pods</h3>