14:03:36 #startmeeting dovetai weekly meeting 14:03:36 Meeting started Fri Dec 9 14:03:36 2016 UTC. The chair is hongbo123. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:03:36 The meeting name has been set to 'dovetai_weekly_meeting' 14:04:08 #info roll 14:04:12 #info hongbo 14:04:19 #info leo_wnag 14:04:26 #info leo_wang 14:07:45 #info dneary 14:08:32 #info we have about four people in this dovetail meeting, we will start the discussion of dovetail release. this topic will be discussed next week 14:08:47 #topic dovetail release plan 14:09:02 #chair dneary 14:09:02 Current chairs: dneary hongbo123 14:11:50 #info Larry Lamers 14:23:57 #chair ChrisPriceAB 14:23:57 Current chairs: ChrisPriceAB dneary hongbo123 14:24:35 #topic Dovetail test tool requirements 14:24:57 #info Leo gives a current status - takes a test case, and runs test cases from upstream test projects 14:25:16 #info Most functionality is ready. Jira tasks created for the tool already 14:25:45 #info Most important is to add new tests 14:27:19 #info Dave says that 2 potential requirements have been raised in recent weeks: 14:27:37 #info 1. Ability to run test tool independent of OPNFV infrastructure 14:29:47 #info 2. Cryptographic verification of test results 14:30:07 #info Leo says for 1st, we are not ready today to support commercial vendors in this way 14:32:50 #info For the 2nd, verifying test results has not been a priority for now. Hongbo believes that we can do this quickly, potentially for the first release 14:34:23 #info Leo asks if this is a requirement for the first release. Dave says that if we award marks based on test results, that there will be resistance if there is no verification trail 14:35:02 #info Leo asks if it is really a requirement, Chris agrees that we need to list requirements and ask for feedback from other groups like CVP on the priorities 14:35:48 #info Dave says it's about expectation management about what we can and cannot do for 1st release, and if we don't do result verification, then it probably will not be used to award trademark usage. 14:38:44 #info Leo says that outside of these, there are no major features which could be required for a first release 14:38:58 #info (bearing in mind that these could also be optional) 14:39:30 #topic Dovetail test case release criteria 14:46:26 #info Hongbo points out there are many candidate tests for consideration, and we should add more to the compliance test suite 14:47:05 #info Dave points out that we have finalised a proposal for test case criteria this week 14:47:38 #info Chris points out that there is some political context we need to consider when adding tests, and it is important that we work closely with the other test projects 14:49:35 #info Hongbo proposes that we engage with the community on test cases to add so that we can add more 14:50:40 #info Dave asks whether an arbitrary number of tests makes sense, and proposed that we focus instead on what functional areas we require test coverage for in the C release 14:51:28 #info We discussed which functional areas made sense for the first release 14:53:51 #info Target functional areas from C&C: 14:54:36 #info Basic VIM operations 14:54:46 #info NFV services (VPN, SFC, ...) 14:55:01 #info Fault management/Localization, Audit 14:55:21 #info Create scenarios/stacks (IPv6, FDS, ...) 14:55:40 #info System testing (Functest, Yardstick) 14:56:32 Can anybody hear me? 14:57:02 no 14:57:42 I was talking away 14:57:49 Now I can hear you again 15:00:07 I hear ye fine 15:00:14 I could not hear ye for a while 15:02:43 #info start email to continue discussion 15:03:15 #endmeeting