17:50:38 #startmeeting DoveTail f2f and IRC 17:50:38 Meeting started Thu Sep 29 17:50:38 2016 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:50:38 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:50:38 The meeting name has been set to 'dovetail_f2f_and_irc' 17:50:49 #topic Roll Call 17:50:56 #info Chris Price 17:50:58 #info Trevor Cooper 17:51:06 #info Jack Morgan 17:51:31 #info Bryan Sullivan 17:53:14 #topic dovetail overview 17:53:32 #link https://wiki.opnfv.org/display/dovetail/Dovetail+Home dovetail wiki page 17:53:34 #info Docker based test framework for running a selection of test cases is being worked on 17:53:58 #info Test specifications are being worked on 17:54:42 #link https://wiki.opnfv.org/display/dovetail/Dovetail+test+use+cases use cases under discussion for doevtail 17:59:35 #link https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269 test case structure and requirements 18:12:53 It's my understanding that we will develop a first compliance test suite definition for Colorado, and that will include granular tests of OpenStack functions and related NBIs; application (VNF) tests such as vIMS, vPing, and maybe the tests I have developed for Models (vHello - simple python web server, vLamp - mult-VM lampstack from OpenStack Interop 18:12:53 Challenge). 18:15:17 #info Bryan: It's my understanding that we will develop a first compliance test suite definition for Colorado, and that will include granular tests of OpenStack functions and related NBIs; application (VNF) tests such as vIMS, vPing, and ... 18:15:37 #info ... maybe the tests I have developed for Models (vHello - simple python web server, vLamp - mult-VM lampstack from OpenStack Interop Challenge). 18:19:59 #info We will enable products to be certified only against those features that they know are supported and should be successfully validated. 18:20:52 #info dneary 18:20:54 (sorry, lost this off my calendar, not in Seattle) 18:23:33 #info For that, as part of getting your implementation verified through a 3rd-party, e.g. CableLabs or some other test house, we need to define a model for how the implementer will scope the tests done by the test house, e.g. something simple as a YAMLfile. 18:24:35 bryan_att, Are you in the room in Seattle? 18:24:48 dneary: we're discussing what we expect out of the dovetail program for Colorado, specifically the CVT proposal document from the C&C committee, and the practical aspects of the tests that Dovetail will support for this release. 18:25:08 dneary: Yes, I'm there. Please pass any questions you want me to ask etc. 18:25:57 bryan_att, I do want to point out tyhat we should not be planning as if the CVP document is finished - it is an in-progress draft without board review at this point 18:26:37 #info dneary: I do want to point out tyhat we should not be planning as if the CVP document is finished - it is an in-progress draft without board review at this point 18:26:57 #info dneary, that's agreed in the meeting here; this is a work in progress 18:27:12 Thanks 18:28:11 #info For Colorado, we do not expect detailed feature tests or performance testing to be in scope. 18:30:08 #info IPV6 overlap, SFC, L3VPN were the scope for this release, beyond basic platform feature tests 18:32:31 #info wrapping up that topic and transitioning to the CVP document 18:33:05 #info chrispriceab adds that everyone should add and participate in the test use case dialog at https://wiki.opnfv.org/display/dovetail/Dovetail+test+use+cases 18:33:33 #info the meeting closes and we will now review the C&C document. 18:34:10 anyone feel the need for a goto meeting for this? 18:34:22 #endmeeting