08:00:21 #startmeeting Functest weekly meeting April 5th 2016 08:00:21 Meeting started Tue Apr 5 08:00:21 2016 UTC. The chair is jose_lausuch. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:00:21 The meeting name has been set to 'functest_weekly_meeting_april_5th_2016' 08:00:27 #info Jose Lausuch 08:00:34 #info Juha Kosonen 08:00:36 #info Viktor Tikkanen 08:00:38 #info Luke Hinds 08:00:38 #info Ciprian Barbu (Enea) 08:00:42 #info CG_Nokia 08:00:43 #info Juha Haapavirta 08:01:05 viktor_nokia: now it should be right time! :) 08:01:16 OK :) 08:01:49 #link https://wiki.opnfv.org/display/functest/Functest+Meeting 08:02:10 anyone else? 08:03:20 #topic Action point follow-up (meeting on the 22th March) 08:03:37 #link http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2016/opnfv-testperf.2016-03-22-08.00.html 08:03:45 #info viktor_nokia have a look at Tempest results on ocl/compass scenario 08:03:57 jose_lausuch, may I add sec test to the agenda (if time) 08:04:09 that is the only action point from that meeting, the action points of the helsinki meetup are to be discussed later 08:04:15 yes 08:04:25 #info Viktor has contacted chenshuai 08:04:38 lhinds: well, do you want to discuss it in depth?, I will mention it during the allocations 08:04:43 #info compass+ocl is still not in troubleshooting due to floating ip issue 08:04:58 viktor_nokia: ok, thannks, something to follow up? 08:05:14 chenshuai will contact me if needed 08:05:20 ok, thanks viktor_nokia 08:05:25 #info morgan_orange submit the first proposals: done 08:05:30 jose_lausuch, just a couple of quick points, nothing that will take long 08:05:35 ok 08:06:17 #topic Outcome of the Functest meeting in Espoo 08:06:22 some info I want to share with you 08:06:28 #info minutes here: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2016/opnfv-testperf.2016-03-30-06.02.html 08:06:34 #info presentation from Morgan: http://opnfv.fr/opnfv_functest_release_C/#/ 08:06:48 #info some highlights: 08:07:39 #info decision to split the tests in different Tiers with progressive execution (if one fails, don't execute next tier or group of tests) 08:07:50 #info decision: implement a 'trust level' to not execute the long tests every time (save time). 08:08:08 #info decission: split functest_utils.py into 2 different scripts, one for openstack functions only, and the other for the rest. 08:08:19 #info automatic test reporting already in place: http://testresults.opnfv.org/reporting/index-status-apex.html 08:08:35 #info decision: add new test cases like security group, flash test, ... 08:08:44 #info decision: change the way we run tempest: remove static test list --> difficult to maintain. Have 2 separate suites: smoke-serial, and all-parallel. 08:08:51 #info decision: have some basic and quick Rally scenarios before running the whole suite we already have. 08:08:58 #info decision: move to Kibana Dashboard. 08:09:06 am I missing anything? 08:09:22 this is just for info, we will discuss now the tasks for everyone 08:11:54 ok 08:11:58 #topic Jira task allocation 08:12:03 #info new EPICS created by Morgan. 08:12:07 #link https://jira.opnfv.org/browse/FUNCTEST-178?jql=project%20%3D%20FUNCTEST%20AND%20issuetype%20%3D%20Epic%20AND%20status%20%3D%20Open 08:12:19 these are epics now, covering all the areas for Colorado 08:12:31 #info David_Orange1 - security group testing (https://jira.opnfv.org/browse/FUNCTEST-160) 08:12:36 are you ok with this? 08:13:01 jose_lausuch: ok for me 08:13:14 ok, thanks 08:13:34 maybe, something to mention is to doublecheck what is in tempest regarding security as well 08:13:44 David_Orange1 viktor_nokia can you sync on that? 08:13:47 ok, i add it as comment 08:13:52 sure 08:13:56 David_Orange1: great, thanks 08:14:00 #info jose_lausuch - Functest test management refactoring (https://jira.opnfv.org/browse/FUNCTEST-163) 08:14:15 I have to work on that refactoring 08:14:28 I hope to have it soon 08:14:40 #info enikher (Nikolas) - Introduction of Flashtest (https://jira.opnfv.org/browse/FUNCTEST-166) 08:14:44 enikher: ok? 08:15:32 quick question on this one, can I add a depended on? 08:15:58 a depended on? 08:16:01 what do you mean? 08:16:04 yes 08:16:34 I am fine with that 08:16:36 thanks, in fact second thoughts let me check some things over with you enikher 08:16:46 and then we can add a dependency 08:16:57 lhinds: what kind of dependency? 08:17:28 functional dependency, I need to connect to the infra nodes, and we discussed that flashtest may be able to enable that happening 08:17:39 ^ security scan that is 08:18:05 same as you see on jira for SDN-VPN-38 08:18:39 but different as they want VM access 08:18:40 yes in flash test that can easily done 08:19:08 you can access the controllers, or the computes easily 08:19:18 enikher, thanks! shall I raise a new jira for comments / discussions? 08:19:19 ok 08:19:36 lhinds: yes, please, start the discussion :) so we also accelerate the adoption of flash test 08:19:41 if there are more users for that 08:19:47 many thanks 08:19:58 np 08:20:01 ok, next, promise 08:20:09 but Im not sure if bertrand is here 08:20:11 #info Bertrand Souville - Study the opportunity to add new Open Source VNFs for Colorado (https://jira.opnfv.org/browse/FUNCTEST-167) 08:20:32 I guess its fine… 08:20:40 now its you lhinds 08:20:50 #info lhinds (Luke Hinds) - Study the opportunity of basic security tests (https://jira.opnfv.org/browse/FUNCTEST-168) 08:20:56 thanks jose_lausuch 08:21:17 and also https://jira.opnfv.org/browse/FUNCTEST-169 08:21:30 so we covered the connection discussion.. 08:21:32 not sure if this should be an epic, or task.. maybe we can have just 1 epic for security 08:21:57 I guess its moved beyond that now jose_lausuch 08:22:03 #action jose_lausuch merge security epics and create appropriate task 08:22:10 as an update... 08:22:19 do you want to discuss it now? or shall we do it later? 08:23:25 I have the test now connecting to the node, installing the OpenSCAP RPM, running the security tests, downloading the report...and if you put '--clean' as an argparse, it will remove all trace of the scan. 08:23:49 lhinds: nice, and where are the code for those tests? 08:23:49 so its doing quite well, just the connection specifics to work out, and making sure its a 'fit' for functest. 08:24:00 jose_lausuch, that's my next question :) 08:24:08 hehe ok 08:24:15 where to place the code... 08:24:19 where is it now? 08:25:00 I need to get this onto git, should I use functest gerrit / git and have a folder like vPing etc, or host in the security group? 08:25:28 I guess in functest makes sense, as you will call from your bash script? 08:25:40 lhinds: yes, let's create a new directory "security" under /testcases 08:25:46 sure 08:25:51 we can do it 2 ways 08:25:54 we put it in functest 08:25:55 or 08:26:02 merge? 08:26:06 we have it in a remote repository that we clone in functest and use it 08:26:12 that is up to you 08:26:17 ahh good point.. 08:26:31 if its no issue for you to clone, that would be good. 08:26:32 do you have an existing repository already in opfv? 08:26:34 opnfv 08:26:46 I can get aric to create one for me with no issues 08:27:31 lhinds: as you whish, but you can also put it in functest 08:27:44 well, let´s see how this make sense 08:27:44 so I am just getting it to work on temporary basis with Apex, until flash test becomes the de'facto connection method. 08:27:52 normally the repos in gerrit are for existing projects 08:28:02 is the security group considered as project? 08:28:26 yep, that's ok. The security group is like an umbrella project..so we have a few in there for inspector and documentation 08:28:41 ok.. 08:28:59 so if you want, we can start putting it in functest 08:29:38 jose_lausuch, I think we can start on that next week I hope. I just need to make some connection changes for Apex (heat_admin as sudo) 08:29:45 ok 08:29:52 great 08:30:04 as said that will only be a temp workaround, I will go via enikher 's flash framework 08:30:10 sure 08:30:27 anything else regarding security? 08:30:57 nope, just this is what I working on now... https://jira.opnfv.org/browse/APEX-125 08:31:03 thanks! 08:31:19 lhinds: ok, thanks ! 08:31:25 moving on 08:31:26 #info valentin_boucher - vIMS signaling tests (https://jira.opnfv.org/browse/FUNCTEST-171) 08:31:33 he is not in, but he agreed 08:31:42 #info viktor_nokia - Tempest evolution, remove customize suites (https://jira.opnfv.org/browse/FUNCTEST-172) 08:31:50 It's OK 08:31:58 viktor_nokia: some work to investigate this "full" flag :) 08:32:02 maybe not the best solution 08:32:18 the idea is to have also 2 possible ways to execute functest 08:32:24 first smoke-serial 08:32:34 and for the more complex tests cases, full-parallel 08:32:46 but we saw that "full" takes a lot of time and too many test cases 08:33:00 that was with --serial 08:33:10 maybe there are other ways to run a relatively "full" suite 08:33:32 ya , but you said something about 1000 tests? 08:33:35 or more 08:33:44 The number of test cases (~1500) is OK but we should adjust timeouts 08:33:59 enikher: you also are a tempest expert :) 08:34:20 if you have some ideas, you can align with viktor_nokia and me 08:34:46 the idea is to remove the hard coded list we already have 08:35:05 hey 08:35:10 sorry was afk 08:35:11 since that is not maintainable …test cases are changing every time 08:36:25 enikher: np, I remember you told me once something like that 08:36:31 that having a hard coded list is not a good idea 08:36:39 yes 08:37:03 may be it is better when we generate the list always and run some filters in the output 08:37:40 through that some testcase which are know to be not use fully or not working for the scenario could be excluded 08:37:44 #info may be it is better when we generate the list always and run some filters in the output 08:37:55 #info through that some testcase which are know to be not use fully or not working for the scenario could be excluded 08:38:07 sorry :-) 08:38:09 enikher: ok, that makes sense 08:38:10 thanks 08:38:30 ok, moving to rally juhak 08:38:34 #info juhak - Rally refactoring (https://jira.opnfv.org/browse/FUNCTEST-173) 08:38:44 sorry jose 08:38:50 enikher: dont be! :) 08:39:05 do we have a jira ticket for that 08:39:08 is it 172? 08:39:16 enikher: yes 08:39:18 that is the epic 08:39:26 then we can create different sub-tasks 08:40:33 juhak: ping 08:40:54 pong, refactoring task is fine for me 08:41:27 juhak: I think we should also have like 2 set of scenarios for rally 08:41:38 1 set that will be very simple and quick, for the smoke testing 08:41:42 do you agree? 08:41:47 yes 08:42:07 in run_rally we could have a flag to indicate which set of scenarios to run 08:42:14 up to you for implementation :) 08:42:29 we actually already have --smoke option to run only one iteration per test case 08:42:38 ah ok 08:42:41 maybe we can use that one 08:42:46 we haven´t so far 08:42:55 but may still something like 40mins to execute 08:42:59 need to check 08:43:00 really? 08:43:07 we need something that takes max 10 min 08:43:19 maybe iterations = 1 or something 08:43:27 like a sanity check 08:43:44 (if it makes sense) 08:44:10 ok 08:44:11 yes, we need to split current set into two 08:44:21 juhak: ok, thanks! 08:44:30 next 08:44:31 #info raghavendrachari 08:44:31 - create a web portal to add test case/projects/pods to the DB (https://jira.opnfv.org/browse/FUNCTEST-176) 08:44:57 morgan proposed you for this task, are you ok? 08:45:05 otherwise we can leave it for someone else, as you wish 08:45:22 you are also in the ODL stuff, together with others 08:46:24 raghavendrachari: ping? 08:46:34 hi 08:46:52 yes i'll do , just i want db info 08:47:16 raghavendrachari: what info do you need? 08:47:59 what ever the information we need to staore in database 08:48:16 raghavendrachari: ok, I will provide you with the wiki later 08:48:21 ok 08:48:30 there is a wiki explaining the API 08:48:37 so can i use any framework right , no issues with that 08:48:42 no 08:48:42 flask ok ? 08:48:48 flask? 08:48:59 python 's framework 08:49:36 that api we need to implement it .. 08:49:41 I would say flask is a good choice (i use it too) 08:49:45 up to you, its a simple thing to be able to talk to the DB, to put stuff in the DB, some HTML friendly webpage 08:49:59 ok 08:50:05 http://flask.pocoo.org/ ? 08:50:21 jose_lausuch, yep 08:50:36 yes this is official page 08:50:40 #info https://wiki.opnfv.org/display/functest/Collection+Of+Test+Results 08:50:46 raghavendrachari: that is the wiki you need 08:51:02 jose_lausuch: raghavendrachari: are we already using tornado for the api ? 08:51:06 yeah i gone through this page 08:51:25 it is less wepage frendly but already a web server 08:51:33 David_Orange1: I think we are, but I didn't set it up 08:52:14 yes, that was morgan that set it up on my recommendations if i remember 08:52:21 David_Orange1: could be another possibility 08:52:25 but as he said: this tasks consists in creating a web front end to allow people to administrate the DB from a web page (and not by calling the API) 08:52:38 i like flask too but it can be a good thing to have only one server, not 2 08:52:52 you are right 08:53:01 yes need to maintain one server 08:53:20 maybe a second task could be to move API from tornado to flask 08:53:24 i'll comeup with est one 08:53:24 but I think the idea of this is just the front end (web page) to create/modify/delete entries in the DB 08:53:37 making calls to the DB 08:53:49 yes 08:53:56 ok, np 08:54:12 we are running out of time 08:54:13 next 08:54:17 #info raghavendrachari & cedric & others - ODL suite evolution (https://jira.opnfv.org/browse/FUNCTEST-177) 08:54:34 raghavendrachari: I think you had questions about this, can we take them after the meeting? 08:54:44 who is going to participate in this task? 08:54:45 yeah 08:54:53 cedric is not here? 08:55:00 David_Orange1: what is his nickname? 08:55:06 I heard I'm part of "others" 08:55:18 Also I am part of others 08:55:18 JuhaHaapa: sorry! 08:55:24 #undo 08:55:24 Removing item from minutes: 08:55:39 jose_lausuch: cedric is not here 08:55:50 #info raghavendrachari & cedric & CG_Nokia & JuhaHaapa - ODL suite evolution (https://jira.opnfv.org/browse/FUNCTEST-177) 08:56:16 I was happy to be named "others" :) 08:56:18 raghavendrachari: I still have to give you the logs 08:56:20 i will ask to join the meeting next time 08:56:21 am looking into the odl /openstack specs 08:56:27 JuhaHaapa: its just that I forgot who was involved :) 08:56:34 sorry for that 08:56:35 Currently still "onboarding" myself to whole OPNFV area... 08:57:13 CG_Nokia: no problem, just ask questions to any of us 08:57:17 we are here to support 08:57:18 yeah i forgot to send u mail yesterday , please send me the logs where the odl deamon is running .. in the same directory log files are exist 08:57:23 OK , Thx. 08:57:34 raghavendrachari: ok, I will try, if the deployment is still up 08:57:41 ok, next 08:57:42 #info Serena Feng - Test API evolution (https://jira.opnfv.org/browse/FUNCTEST-178) 08:57:47 I think she is not in... 08:57:57 but we sent her an email, hopefully its ok 08:58:53 ok 08:58:55 before we close 08:58:59 #topic Rally sync meeting date/time 08:59:03 #link https://framadate.org/og8LmZ3vKgYSAT9b 08:59:22 juhak viktor_nokia is 17h bad for you? 08:59:40 I can cope with that 08:59:41 well, morgan didnt specify the timezone... 08:59:45 UTC? 08:59:54 the idea is to have Boris, the Rally PTL 09:00:04 it would be great to have you and enikher in that meeting 09:00:33 enikher: is that ok for you? 09:00:56 I will try to reach boris-42 today and propose a time not too late for you and not too early for him 09:01:02 he is based in the US 09:01:21 ok, time to close the meeting 09:01:24 thank you for today! 09:01:35 if you dont have anything else to share 09:01:42 thank you jose_lausuch 09:02:08 #endmeeting