13:02:03 #startmeeting Test&Performance Ops Meeting 13:02:03 Meeting started Fri Oct 2 13:02:03 2015 UTC. The chair is anac1. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:02:03 The meeting name has been set to 'test_performance_ops_meeting' 13:02:15 #chair morgan_orange 13:02:15 Current chairs: anac1 morgan_orange 13:02:33 #info Morgan Richomme 13:02:41 #info Ana Cunha 13:02:59 shall we review the pad 13:03:04 the new demands 13:03:14 #topic test requests 13:03:45 #info last time we initiated an answer for IPv6 and ArmBand 13:03:54 #info and Promise 13:03:54 #link https://etherpad.opnfv.org/p/testing_requests_for_b_release 13:04:03 #info pending Copper and Doctor 13:04:16 #info for Doctor I exchanged via the backlog of Jira 13:04:21 is this only for PTLs ? :) 13:04:35 no 13:04:50 #info they developped Rally Script 13:04:51 will add functest to doctor's request? 13:04:59 #info so easiest way is to integate these scripts in Functest 13:05:10 #info only dependencies is the need for ceilometer 13:05:29 #agreed doctor - functest support 13:05:37 what about copper? 13:06:45 bryan is not on the IRC but it looks a little bit similar, except that they also need Congress 13:06:49 functest, i think, or? 13:07:15 the same than for Doctor, they have to see with genesis if the additional OpenStack module will be integrated 13:07:26 if so, Ok to put the test in functest 13:07:39 #agreed copper - functest support 13:08:10 jose_lausuch: do you confirm than ceilometer was not available in SR1? 13:08:32 #info OK I will update the Matrix and put a link between Copper/Promise and Functest 13:08:41 morgan_orange: yes, I confirm 13:09:28 Ok so there is a dependency towards the installers, the feature tests will need the modules 13:09:41 #info requests processed, all handled, so far 13:09:53 #action morgan_orange update wiki page 13:10:06 #link https://wiki.opnfv.org/feature_test_project_matrix 13:10:30 BTW anac1 I will probably copy your wiki project page, I found it very clear : 13:10:55 thanks for feedack 13:11:01 feedback 13:11:40 #topic pods for testing 13:11:49 oh yes... 13:11:52 good one 13:12:16 will not be possible to verify everything in LF POD2 13:12:18 will be the intel one available soon? 13:12:38 we discussed on the chan this morning 13:12:46 yep 13:13:06 I took the point to send a mail to pharos cc tech opnfv to discuss the availability of PODS for testing after SR1 13:13:11 LF POD2 is not enough for us 13:13:24 ok 13:13:30 so we need to have at least 2 or 3 PODS for our tests / integration in CI / .. 13:13:50 can we propose something like: feature x to be tested in pod y 13:14:09 a list with the requests we have and the pods? 13:14:16 anac1: +1 if we have enough pods 13:14:24 but in the end we should test everything in all the pods 13:14:31 it shoudl be managed in Pharos JIRA I think 13:14:43 and we should have a clear view of the available PODs + available tooling 13:15:00 we should have PODs to CI and automatic testing 13:15:02 not clear to me, though 13:15:08 and some to prepare/tune the test suites 13:15:33 we should automate as much as possible...but everything could not be automated 13:15:53 if you see VSPerf they are using IXia loader, it not present in all the PODs 13:16:26 how's the best way to organize a list? testing wiki? 13:16:50 in a first step wiki could be OK but we need a portal at the end 13:17:19 portal will show the testbed, the OPNFV solutions installed on it, the availability for test campaigns, the list of automated tests, the requests pending... 13:17:34 I think someone from LF suggests the idea of a portal.. 13:17:53 long term sounds good, we need to get started 13:17:58 but in short term a wiki and at least 2 or 3 POD to work on the tests + N PODs for automated testing 13:18:06 agree 13:18:36 #info POD test groups need to reference request/test/PoD in the wiki in short term 13:18:48 do we need approval for this way of working? 13:18:49 #info need at least 2 or 3 POD to work on the tests + N PODs for automated testing 13:18:59 I think we can prepare a mail 13:19:06 exchange with the testing community and Pharos 13:19:15 and vote during the next thursday meeting 13:19:25 ok 13:19:44 #info long term we need a Pharos portal providing all the informations (version, availability, tooling, test history,...) 13:20:00 morgan_orange: arent they working on that already? 13:20:18 #info suggestion 1) mail to exchange with community 2) discussion and vote next thursday during weekly test meeting 13:20:36 jose_lausuch: for the moment I think they try to get resources 13:20:43 morgan_orange: will you start 1)? 13:20:57 #action morgan_orange prepare mail 13:21:06 ok 13:21:20 shall we add a page in testing wiki? 13:21:25 the expectations towards Pharos are very high and they are lacking resources 13:21:42 I am even not sure that there iis 1 representative per declared paltform today 13:21:54 anac1: yes can I action this to you? 13:21:57 yes 13:22:21 #action anac1 create wiki page to give the overview of tesbeds versus test project requests 13:23:02 shall we speak about the pres for the Summit 13:23:15 I did not start looking at that 13:23:34 ok, we need to get a presentation ready be oct 30 13:23:38 i hope the Sprint #3 of LF will share a nice dashboard 13:23:43 that give us 1 month 13:23:54 you have a presentation together, right? 13:23:59 morgan, we have another one we 2 13:24:23 yes ...I will be in vacations on week 43 13:24:39 jose_lausuch: yes 13:24:46 and I will be in the summit week 42 13:24:56 sdn openflow congress 13:24:58 jose_lausuch: the one we have is about test collection and dashboard 13:25:06 yes 13:25:12 relatively easy 13:25:18 I already made some slides and a wiki page 13:25:21 well, its 20 min 13:25:22 just need to refator 13:25:24 so 5-6 slides max 13:25:26 with last status 13:25:37 morgan_orange: i will book a meeting in week 42, you, trevor and i for discussing the presentation, ok? 13:25:42 what format should we use for the slides, anac1? 13:25:43 ok 13:25:52 jose_lausuch: anac1 sent us the template 13:26:05 powerpoint 13:26:17 jose_lausuch: yes, i sent the template, upload in pdf 13:26:52 jose_lausuch: we will work on it on week 44 13:27:09 because power point is fine , but not for everyone who has a linux machine 13:27:12 the person who sent the presentation proposal has to upload the final presentation in pdf format 13:27:25 usually I can open powerpoint with impress 13:27:29 and at the end pdf 13:27:37 there are other ways 13:27:37 http://slides.com/jose_lausuch/functest-in-depth#/4 13:27:43 I started some days ago a template 13:27:45 or a js framework 13:28:03 reveal... 13:28:07 guys, i have to go, can we end the meeting? 13:28:15 yes 13:28:19 #endmeeting