09:00:31 #startmeeting Functest weekly meeting october, 13th 09:00:31 Meeting started Tue Oct 13 09:00:31 2015 UTC. The chair is morgan_orange. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic. 09:00:31 The meeting name has been set to 'functest_weekly_meeting_october__13th' 09:00:36 Guten Tag 09:00:38 just on time :) 09:00:42 #info Jose Lausuch 09:00:43 päivää 09:00:45 Gooooooooooooooooooooooooooood Morning Düsseldorf 09:00:47 #info Viktor Tikkanen 09:00:50 #info Morgan Richomme 09:00:51 :) 09:00:53 #info Qinglong Lan 09:00:56 #info Juha Kosonen 09:00:58 #info Peter Bandzi 09:01:30 lot of participants today :) 09:01:37 agenda 09:01:39 #link https://wiki.opnfv.org/functest_meeting 09:01:53 #topic follow up of the action points 09:02:01 This is a goo time .. 09:02:03 #info Guy Rodrigue Koffi 09:02:05 #link http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2015/opnfv-testperf.2015-10-06-16.00.html 09:02:24 there was a point for you Qinglong 09:02:37 did you find an Onos compatible lab? 09:02:46 connected to CI? 09:03:22 for the other points 09:03:41 #info wiki page on ODL testcases to be integrated created 09:03:51 #link https://wiki.opnfv.org/odl_new_test_suites 09:03:56 I need to leave over for the next time , OK ? 09:03:59 we will rediscuss later witj R2 09:04:16 great mornga 09:04:18 morgan 09:04:20 #info huhao 09:05:04 #info next action item was new time, seems that it is more confortable for Asian contributors 09:05:26 pbandzi: which one did we use in opnfv? 09:05:26 #info last action item => refactoring of contributors (removing ghost) in progress 09:05:32 from these https://github.com/opendaylight/integration-test/tree/master/csit/suites 09:06:05 jose_lausuch: https://github.com/opendaylight/integration-test/tree/master/csit/suites/openstack/neutron 09:06:18 ah yes, I see 09:06:19 thanks 09:06:28 #topic R2 09:06:43 morgan_orange: how are we gonna remove ghosts? 09:06:48 jose_lauisch: and some othe basic restconf - i have to find 09:06:59 People already volunteered to be removed 09:07:05 then I will follow the procedure 09:07:08 jose_lausuch: i think this https://github.com/opendaylight/integration-test/blob/master/csit/suites/iotdm/basic/010_Restconf_OK.robot 09:07:11 unactive contributors will be reoved 09:07:14 ok 09:07:31 pbandzi: ok, thats the first tests testing the rest api, thanks 09:07:31 #info Sprint 1 finishes at the end of the week 09:07:36 #link https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=59 09:08:05 #info FUNCTEST-49 could be delayed (no ONOS lab available so far) 09:08:29 yep, the installer still can't work well 09:08:36 pbandzi: jose_lausuch morgan_orange OK to select a pre-list of ODL testcase (FUNCTEST-54) before the end of the week.... 09:08:56 ok pbandzi 09:08:59 ok 09:09:00 sorry, morgan_orange 09:09:15 the rest of the tasks are related to the use of the test collection API 09:09:19 for FUNCTEST 49, we can do something ugly, but it wont be 100% tested 09:09:41 #info guy_rodrigue committed a new version of the API end of last week 09:09:56 for FUNCTEST 37, it is possible to finish it or at least to merge the first version of it 09:10:06 #info I started some doc on the API 09:10:08 #link https://wiki.opnfv.org/collection_of_test_results 09:10:44 i've started to test swagger integration for the API 09:11:00 morgan_orange: what you have written is at the end, right? 09:11:06 #info integration of swagger to generate accurate doc 09:11:07 https://wiki.opnfv.org/collection_of_test_results#rest_api 09:11:13 jose_lausuch: yes 09:11:14 maybe you can info that link instead :) 09:11:26 #undo 09:11:26 Removing item from minutes: 09:11:29 #undo 09:11:29 Removing item from minutes: 09:11:37 #link https://wiki.opnfv.org/collection_of_test_results#rest_api 09:11:45 #info integration of swagger to generate accurate doc 09:11:50 thanks 09:11:55 so if summarize for the JIRA 09:12:17 #info FUNCTEST-49 possibility to commit something, but could be tested only when solution including ONOS will be available 09:12:37 #info FUNCTEST-56 shall be possible 09:12:57 pbandzi: you could integrate a call to the API from ODL test (not very critical... :)) 09:13:15 ? 09:13:18 morgan-orange yes 09:13:28 #info FUNCTEST-57 shall be OK as well 09:13:36 OK for Sprint 1 09:13:46 jose_lausuch: already finished tasks of Sprint 3 I think 09:13:49 dockerization is ready 09:13:56 jose_lausuch: could you give the status 09:14:03 yes 09:14:12 shall I info? 09:14:15 yes 09:14:50 #info Dockerization (which is a task in sprint 3) is already done, just attached to some future improvements, like installting needed libraries in the dockerfile and so on 09:15:04 #info to be done: CI automatic build and push to dockerhub 09:15:40 this is actually important, we want to build and push, but I need to talk to Fatih (who is here in Dusseldorf) about that) 09:16:05 #info regarding FUNCTEST-38 (vIMS), Valentin committed also the code, Integration tests in progress (SSH error on KF POD2) 09:16:39 we started looking into that and that ssh error was strange 09:16:48 #info for next Sprint, I think we should add a task on the refactoring of Rally and Tempest 09:16:54 #info ssh error could be due to a bad configuration in the jumphost 09:17:09 morgan_orange: agreed 09:17:09 #info due to new version of Rally and fix to be done (we where testing some modules that were not deployed...) 09:17:17 we need to make the most out of Rally 09:17:41 yes, I will create new task for Sprint 2 and attribute them to juhak and viktor_nokia, ok? 09:17:51 ok 09:18:00 ok 09:18:23 we need to understand what makes sense to test from Rally 09:18:32 #info refactoring of Tempest and Rally tests to be planned from Sprint 2 assigned to viktor_nokia and juhak 09:18:35 what do we need to change from R1 rally tests 09:19:09 I think, boris-42 would also be very helpful for that task :) 09:19:29 yep 09:19:54 #info tets dashboard convergence: I think we are now in line with LF web team 09:20:08 whats the latests status, morgan_orange? 09:20:16 (I havent had time to read emails yet) 09:20:17 #info guy_rodrigue API shall be extended to include a dashboard method that will build the dashboard ready json 09:20:29 ok 09:20:34 #info last status we forget about recoding in PHP on teh web side 09:20:46 #info we add a new method in the test_collection_api 09:21:13 #info we put the script producing the dashboard ready json in Releng and we use them for this new method 09:21:23 ok 09:21:39 guy_rodrigue: I will come back to you for that 09:21:44 so who is responsible to generate the json-ready ? 09:21:47 no problem 09:21:48 each test case owner? 09:22:07 #action guy_rodrigue add dashboard method in the APi + script per testcase to provide dashboard ready results 09:22:31 jose_lausuch: yes the test case owner are responsible for that 09:22:37 but we will have samples 09:22:58 basically they are the only ones able to say what they want to show... 09:22:59 ok 09:23:04 we could have put an overall status 09:23:16 but that was planned from the beginning like that 09:23:20 we will be able to illustrate it with the functest2Dashboard 09:23:24 whats the difference ? 09:23:25 jose_lausuch: yes..... 09:23:30 no comment 09:23:33 we dont push the entire json to the DB, right? 09:23:43 in the DB only the raw results 09:23:52 we build on demand the ready for dashboard json 09:24:12 ok let's move to the next topics 09:24:14 ok 09:24:15 thanks 09:24:29 #topic Onos 09:24:41 Qinglong: could you give us a status? 09:24:47 Ok 09:25:14 #info ONOS functest include 2 cases,and it already can run well 09:25:34 Now the pushing DB is under working 09:26:03 you described the testcases in a wiki page? 09:26:13 Qinglong: can you specify what the testcases do ? 09:26:26 #not yet , I can do this later 09:26:30 ok 09:26:47 jose_lausuch: Düsseldorf connectivity not as good as the one from Brittany :) 09:26:48 The first one is northbound test of onos 09:27:02 morgan_orange: you are always quicker :p 09:27:18 Qinglong: testing rest api? 09:27:22 include network/subnets/ports post/update/delete 09:27:25 #action Qinglong provide high level description of ONOS testcases on the wiki 09:27:45 ok so it is closed to the suite created by pbandzi for ODl and Neutron 09:27:48 cool 09:27:50 yes 09:28:03 The 2nd one is vm getonline and have a ping to each other 09:28:18 mmmm 09:28:26 #info Onos test cases consistent with previous ODL test 09:28:34 dont we alraedy have that? 09:28:59 the controller shall be transparent through the existing vPing 09:29:13 if we run vPing on a installation with ODL or ONOS, we are alraedy have that test case 09:29:19 I saw that Rally was also able to run vPing like tests.. 09:29:22 yes 09:29:23 so Im wondering if it will make a difference 09:29:46 vping is a end to end test 09:30:09 the onos test may aim to ONOS more 09:30:28 but does it create any SDN special stuff? 09:30:30 ok let's describe it on the wiki, we could disucss later 09:30:31 each case has about 10 cases 09:30:52 ok,thank you 09:30:55 ok 09:31:45 for the wiki on R1 we created the following page https://wiki.opnfv.org/r1_vping, https://wiki.opnfv.org/r1_odl_suite, https://wiki.opnfv.org/r1_rally_bench, https://wiki.opnfv.org/r1_tempest 09:32:02 we could create new page fro R2 from https://wiki.opnfv.org/functextnexttaks 09:32:10 ok let's move to next topics 09:32:18 #topic synchro with Doctor 09:32:39 sure 09:32:56 I know that they have their meeting at the same time..so Ryu was not sure to be available 09:33:06 abyone from Doctor on the Chan 09:33:07 ? 09:33:23 Ildiko is at the summit :) 09:33:31 i'm sorry morgan_orange, i will have to leave 09:33:36 Ericsson dream tema is here... 09:33:41 hehe 09:33:48 I can talk to her 09:33:48 is there any action to discuss about collection api ? 09:34:00 what shall I bring up for discussion? 09:34:09 guy_rodrigue: I closed some Jira and recreated some for Bugs I found 09:34:23 okay, 09:34:30 maybe a jira for unit tests as well 09:34:42 I think there is already one:) 09:34:48 but I will check 09:34:52 :) 09:35:07 #action check Jira for unit tests on test collection API 09:35:10 thanks guy_rodrigue 09:35:19 thanks morgan_orange 09:35:23 bye folks ! 09:35:25 so no one from Doctor but we can share the cross matrix page 09:35:29 #link https://wiki.opnfv.org/feature_test_project_matrix 09:35:53 we can see that many feature projects already identified somme dependencies with us 09:36:29 morgan_orange: it's in progress https://review.openstack.org/#/q/status:open+project:openstack/rally+branch:master+topic:bp/vm-workloads-framework,n,z 09:36:34 morgan_orange: not done yet 09:36:40 #info severla projects identified needs on functest: Copper, Doctor, ONOS, OVNO (Open Contraiol) PolicyTest, Promise) 09:36:56 boris-42: thanks 09:37:03 I can grab someone from Docotor here and ask 09:37:19 #info OpenContrail scenario shall follow the default test suite 09:37:28 jose_lausuch: I think they are attending their own meeting 09:37:45 I mean, later today 09:37:53 we may organize an ad hoc meeting 09:37:58 you can discuss with them 09:38:21 basically their main dependencies would be towards installer projects as they need additional components 09:38:43 we can install some 3rd party element e.g. cloudify for vIMS) but not OpenStack Component 09:38:44 ok 09:38:51 that is my view.. 09:39:05 thats for sure, we can install testing tooling 09:39:14 Tacker for example has been requested by SFC, it shall be available, Functest would not install tacker 09:39:19 but not stuff in the infrastructure, thats for genesis reqs 09:39:25 yes 09:39:29 but SFC has to install it 09:40:16 #info ad-hoc IRC meeting with the different projects to be plan to anticipate their needs and see if we can help them (or not) 09:40:28 #topic AoB 09:40:36 any other topic you want to discuss? 09:40:39 need to say that this time (9 UTC) is much more suitable for us early birds too :) 09:40:54 not from my side 09:41:00 I see :) 09:41:11 no, sorry, it was an answer to morgan 09:41:18 9UTC is also good for me :) 09:41:35 #info consensus to adopt this slot...convenient for Asian and European contributors.. 09:41:50 #info we keep the second one for our US contributors 09:41:58 what about our US contributors? 09:42:04 heheh, always quicker! 09:42:24 jose_lausuch: any feedback from "The place to be" without network connectivity? 09:42:53 well, we had our mini summit yesterday 09:42:53 not too much vendor brainwashing on NFV/SDN ? :) 09:43:02 well, it is sometimes 09:43:29 as feedback, maybe we have to document how to run individual tests frmo the docker 09:43:38 not only the full functest suite 09:43:53 but since docker is there, its about adding some steps in the documentation 09:44:01 yep, we will have to rewrite the doc anyway 09:44:23 and for future demos as well, if we can manage to have an offline functest it would be nicer :) 09:44:34 but I followed your doc and it was simple.. 09:44:50 what doc? 09:44:53 I am still waiting for creds on.. Orange testbed to do it as well on this lab 09:44:54 ah, the wiki 09:44:59 ok 09:45:13 yes 09:45:17 great 09:45:37 and the dependency on having an interface on the management network is a pain 09:45:37 #info docker doc to be updated to be able to launch test case one by one 09:45:41 #link https://wiki.opnfv.org/functest_docker?s[]=docker 09:46:23 boris-42: we might need your help for rally/tempest 09:46:32 but thats another discussion, no for now 09:46:40 BTW, I'm still waiting for LF POD VPN profile 09:46:55 so until now can use our local setup (Foreman based Arno SR1 with 6 nodes) only 09:47:20 mmm it is very long 09:47:58 I will contact aric 09:48:06 i think you got the green light 09:48:13 ok 09:48:43 Does nokia plan to connect some PODs to CI? 09:48:54 not sure... 09:49:01 ok 09:49:02 need to check 09:49:23 we will lack lab regarding the different config, and releng is also looking for resources 09:49:27 we will see.. 09:49:36 so if no other question, we can close the meeting now 09:49:48 thanks for attending 09:49:54 ok 09:50:14 thanks all 09:50:20 let' try to finish our Sprint (it is my first one, what happens if we do not finish the tasks....) 09:50:28 :) 09:50:39 #endmeeting