summaryrefslogtreecommitdiffstats
path: root/docs/com/pres/summit-Berlin.html
blob: f3df25051935fe23e45d3e37ab12165b41a14e60 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
<!doctype html>
<html lang="en">

	<head>
		<meta charset="utf-8">

		<title>OPNFV presentation</title>

		<meta name="description" content="Functest: Many rivers to cross">
		<meta name="author" content="Morgan Richomme and Functest contributors">

		<meta name="apple-mobile-web-app-capable" content="yes" />
		<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />

		<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">

		<!-- Code syntax highlighting -->
		<link rel="stylesheet" href="../lib/css/zenburn.css">

		<!-- Printing and PDF exports -->
		<script>
			var link = document.createElement( 'link' );
			link.rel = 'stylesheet';
			link.type = 'text/css';
			link.href = window.location.search.match( /print-pdf/gi ) ? '../css/print/pdf.css' : '../css/print/paper.css';
			document.getElementsByTagName( 'head' )[0].appendChild( link );
		</script>

		<!--[if lt IE 9]>
		<script src="lib/js/html5shiv.js"></script>
		<![endif]-->
	</head>

	<body>

		<div class="reveal">
			<!-- 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>
                     <h1>From Arno to Colorado</h1>
                     <h3>Functest: Many rivers to cross</h3>
                     <br><br>
					 <h4>Functest contributors</h4>
					 <h5>OPNFV Design Summit, 20/6/2016, Berlin</h5>
					 <br>

				</section>

				<section>
					<blockquote>
						&ldquo;Bad programmers have all the answers. Good testers have all the questions. Gil Zilberfeld - &rdquo;
					</blockquote>
				</section>

				<section data-markdown>
					# Agenda
					* Functest
					* Arno
					* Brahmaputra
					* Colorado
					* D, E, F rivers and beyond
				</section>

				<section data-markdown>
					# The dream team
					![team](../img/teamSummitBerlin.png)
				</section>

				<section>
					<section data-markdown>
						# Functest: what for?
					</section>
					<section data-markdown>
						## Our goals
						### make sure OPNFV works......
					</section>
					<section data-markdown>
						## so concretely...
						* Validate scenarios for the release	
						* Give confidence on OPNFV fresh releases
						* Ensure consistancy towards installers
						* Ensure End to End interoperability
					</section>
					<section data-markdown>
						## and also
						* Provide functional test suites to be replayed
						  * ~ post install sanity check
						  * usable for plugfests
						  * coherent with ETSI and Telco needs
						* Provide test tools
						  * run tests
						  * collect info
						  * create dashboard
					</section>
                    <section data-markdown>
						## Our goals are not....
						* Performance testing (yardstick, Xperf )
						* Re-do tests done in specific projects
						  * storage/storeperf
						  * infra audit/qtip
						* Compare results
					</section>

                    <section data-markdown>
						## Our rules
						* Re-use as much as possible upstream suites (Rally, Tempest, Robot, testOn..)
						* Keep it simple...
						* Automate (if not it is not a test...)
						* Create new suites only if tests not covered
						* Consider fields not addressed by existing test projects
					</section>

                    <section data-markdown>
						## Our rules
						* Installer neutral
						* Controller neutral
						* Black box approach
					</section>

				</section>

                <section>
                    <section data-markdown>
						# Arno
					</section>
                    <section data-markdown>
						## Proof of concept
						* 4 Testcases: vPing (userdata), Tempest, Rally, ODL
						* 1 scenario: os-odl_l2-nofeature-ha
						* 2 installers: Foreman/Fuel
						* Lots of manual operations (reporting, documentation)
					</section>
                </section>				
				<section>
                    <section data-markdown>
						# Brahmaputra
					</section>
                    <section data-markdown>
						## More everything....
						* 7 Testcases: vPing (ssh), ONOS, vIMS, Tempest and Rally extended
						* 3 feature projects: doctor, promise, sdnvpn
						* 13 Scenarios
						* 4 Installers (Apex, Compass, Fuel, Joid)
						* Test result collection 
						* Automatic dashboard 
					</section>
				<section>
					<h3>Jiras</h3>
					<img height="200"  data-src="../img/jiras.png" alt="Jiras">
					<img height="200"  data-src="../img/jiras2.png" alt="Jiras">
				</section>

				<section>
					<h3>Brahmaputra Scenario matrix</h3>
					<img width="800"  data-src="../img/matrix.png" alt="Jiras">
				</section>

				<section>
					Comparison odl_l2-nofeature-noha scenario
					<table>
						<thead>
							<tr>
								<th>Project</th>
								<th>Apex</th>
								<th>Compass</th>
								<th>Fuel</th>
								<th>Joid</th>
							</tr>
						</thead>
						<tbody>
							<tr>
								<td>POD</td>
								<td>LF POD1</td>
								<td>Huawei US</td>
								<td>Ericsson POD2</td>
								<td>Orange POD2</td>
							</tr>
							<tr>
								<td>Functest</td>
								<td>2h50</td>
								<td>1h45</td>
								<td>2h35</td>
								<td>2h30</td>
							</tr>
							<tr>
								<td>Yardstick</td>
								<td>1h05</td>
								<td>1h00</td>
								<td>1h00</td>
								<td>0h55</td>
							</tr>
						</tbody>
					</table>
                   * difference of duration due to POD and test suites 
				</section>

				<section data-markdown>
					## Lessons learned
					* Tempest: harmonizing installer related OpenStack configuration differences, creating customized test lists, main challenge was resolving SDN controller interworking problems 
					* Rally:
					* vIMS: complete but complex test case, very interesting to automate (pre MANO, most of Telco needs met there)
				</section>

				</section>

				<section>				
					<section data-markdown>
						# Colorado
					</section>

					<section data-markdown>
						## What's new?
						* Slicing of the tests (healthcheck / Smoke / SDN controllers / Features / VNFs)
						* Test duration management
						* New test cases: healthcheck, security
						* Refactoring (API, structure)
						* ARM Support 
						* Automatic reporting
						* Dashboard evolution to ELK
						* CLI
					</section>

				<section>
					<h3>Automatic reporting</h3>
					<img height="400"  data-src="../img/reporting.png" alt="Reporting">
					<br><a href="http://testresults.opnfv.org/reporting/functest/release/master/index-status-fuel.html">Validated scenarios for Colorado</a>
				</section>

				</section>

                <section>
					<section data-markdown>
						# Many rivers to cross
						## Functest beyond Colorado
					</section>
					<section data-markdown>
						## More test cases
						* New controler: OpenContrail
						* New feature projects
						* New VNFs (vEPC, vCDN, vWhatever...)
						* Multi sites (e.g bgpvpn with different back ends)
					</section>					
					<section data-markdown>
						## A Functional testing As a Service framework
						* Scenarios can select their relevant test cases
						* Test duration estimation
						* Agile dashboarding
						* Analytics
					</section>	
                    <section data-markdown>
						## Upstream
						* Rally
						* Functest description for ETSI?   
					</section>					
                </section>

				<section>
					<h3>Thank you</h3>
					<img width="600"  data-src="../img/colorado.png" alt="tests">
				</section>

			</div>
            <div class='footer'>
				 <img src="../img/logo-OPNFV.png" alt="OPNFV logo"> 
	        </div>
		</div>

		<script src="../lib/js/head.min.js"></script>
		<script src="../js/reveal.js"></script>

		<script>

			// Full list of configuration options available at:
			// https://github.com/hakimel/reveal.js#configuration
			Reveal.initialize({
				controls: true,
				progress: true,
				history: true,
				center: true,

				transition: 'slide', // none/fade/slide/convex/concave/zoom

				// Optional reveal.js plugins
				dependencies: [
					{ src: '../lib/js/classList.js', condition: function() { return !document.body.classList; } },
					{ src: '../plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
					{ src: '../plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
					{ src: '../plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
					{ src: '../plugin/zoom-js/zoom.js', async: true },
					{ src: '../plugin/notes/notes.js', async: true }
				]
			});

		</script>

	</body>
</html>