aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorYujun Zhang <zhang.yujunz@zte.com.cn>2016-06-17 13:56:39 +0800
committerYujun Zhang <zhang.yujunz@zte.com.cn>2016-06-18 12:22:27 +0800
commit64506868480cf7333be6ce59377a6a0bac7c5e97 (patch)
tree73f243562c8b38c5dd0422fa5549d8782f30b149 /docs
parentc4c3bba1136388d2357c160e9750ae4008b55b82 (diff)
add slides for qtip
Change-Id: I020a296a64ffb2b10b0772e0f971fd8732f0f2d7 Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
Diffstat (limited to 'docs')
-rwxr-xr-xdocs/com/pres/conversation.html44
1 files changed, 29 insertions, 15 deletions
diff --git a/docs/com/pres/conversation.html b/docs/com/pres/conversation.html
index 7d5de28e..9c8c4aff 100755
--- a/docs/com/pres/conversation.html
+++ b/docs/com/pres/conversation.html
@@ -84,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>
@@ -102,9 +102,9 @@
<td>Detect possible bottlenecks</td>
</tr>
<tr>
- <td>QTip</td>
- <td>Harware benchmarking</td>
- </tr>
+ <td>QTIP</td>
+ <td>Benchmark to boost performance</td>
+ </tr>
</tbody>
</table>
</section>
@@ -144,23 +144,37 @@
# Bottlenecks
</section>
<section data-markdown>
- # QTip
- </section>
+ # 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>
@@ -170,20 +184,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>