diff options
| -rwxr-xr-x | docs/com/pres/conversation.html | 58 |
1 files changed, 33 insertions, 25 deletions
diff --git a/docs/com/pres/conversation.html b/docs/com/pres/conversation.html index bba5e672b..0fab448a2 100755 --- a/docs/com/pres/conversation.html +++ b/docs/com/pres/conversation.html @@ -15,7 +15,7 @@ <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui"> <link rel="stylesheet" href="../css/reveal.css"> - <link rel="stylesheet" href="../css/theme/OPNFV.css" id="theme"> + <link rel="stylesheet" href="../css/theme/OPNFV-Berlin.css" id="theme"> <!-- Code syntax highlighting --> <link rel="stylesheet" href="../lib/css/zenburn.css"> @@ -40,8 +40,8 @@ <!-- Any section element inside of this container is displayed as a slide --> <div class="slides"> - <section data-background="../img/title-bg.png" data-background-transition="none"> - <br> + <section data-background="../img/title-bg-berlin.png" data-background-transition="none"> + <br><br><br><br><br> <h1>Conversation with the Testing Community</h1> <br><br> <h4>OPNFV testing community</h4> @@ -108,26 +108,26 @@ # Functest * Functional testing to validate scenarios * Contributors (raise your hands) - * Functest presentation (here...1h ago :)) slide available here + * Functest presentation (here...1h ago :)) * breakout sessions - * Today 4PM (feature project integration), 5PM (Colorado status) + * Today 3.10PM-3.40PM (vIMS evolution) 4PM (feature project integration), 5PM (Colorado status) * tomorrow 11AM (API, test collection), 1PM (work Upstream), 3.15PM (D Release)(to be confirmed...) </section> <section data-markdown> # Yardstick - * 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 - * breakout sessions - * Tomorrow 2PM (Yardstick in C) + * 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 + * breakout sessions + * Tomorrow 2PM (Yardstick in C) </section> <section data-markdown> # CPerf - * SDN Controller Performance Testing - * Upstream test experts + standards/metrics experts - * Goal: Cross-controller perf tests in CI against realistic deployments + * SDN Controller Performance Testing + * Upstream test experts + standards/metrics experts + * Goal: Cross-controller perf tests in CI against realistic deployments </section> <section data-markdown> # StorPerf @@ -147,33 +147,41 @@ ## We are on the shoulders of the giants * Rally (OpenStack) * ODL, ONOS, ... - * RobotFramework, teston + * RobotFramework, Teston * ..... </section> <section data-markdown> ## Time to give back - </section> - - <section data-markdown> - ## How to improve work with testing upstream community + ### How to improve work with testing upstream community </section> </section> <section> + <section data-markdown> - # Towards telco Cloud API... + # 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, .. + * Identify testing domains + * 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 </section> </section> - <section> - <h3>Thank you</h3> - <img width="600" data-src="../img/colorado.png" alt="tests"> + <section data-markdown> + # Thank you </section> </div> |