08:03:53 #startmeeting Functest weekly meeting April the 26th 08:03:53 Meeting started Tue Apr 26 08:03:53 2016 UTC. The chair is jose_lausuch. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:03:53 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:03:53 The meeting name has been set to 'functest_weekly_meeting_april_the_26th' 08:03:59 pound in your names 08:04:03 #info Jose Lausuch 08:04:10 #info Juha Kosonen 08:04:19 #info Morgan Richomme 08:04:32 he has some problems with IRC, but he is on the GTM talking 08:04:47 #info Juha Haapavirta 08:05:10 #topic action point follow-up 08:05:24 #info jose_lausuch send reminder to project test PTLs to fill the tables for release criteria DONE 08:05:29 #info Ciprian Barbu 08:05:37 #info morgan_orange prepare presentation for test meeting on test criteria done 08:05:52 #info morgan_orange contact policytest to see if they are still alive. No answer, we assume its not active 08:06:04 #info morgan_orange review new demands from feature projects and try to precise a way to work. Presentation to be done now 08:06:18 #info viktor_nokia set tempest smoke to 100% done 08:06:35 #info juhak add line Rally_smoke / rally full - done 08:07:41 #info serena-zte 08:07:52 #info Viktor Tikkanen 08:07:55 #info luke to contact intel labs / tim rozet for security test integration - jira open towards pharos. No apex 'master' running on CI. 08:08:43 #info morgan_orange viktor_nokia contact Frank to see if offline could be considered as a requirement for C-release - DONE- answer: it was already considered as a requirement by Genesis. But there might be problematic for some installers like JOID. 08:08:52 #info morgan_orange create functest cli epic. DONE 08:09:08 #info proposal: https://wiki.opnfv.org/display/functest/Functest+CLI 08:09:58 serena-zte: https://global.gotomeeting.com/join/566165845 08:10:15 #topic 5 minutes on Jira/gerrit best practices 5' 08:11:02 #info morgan_orange presents a new wiki made by Morgan and Jose: https://wiki.opnfv.org/display/functest/JIRA+management 08:11:35 oops 08:12:11 What happened? 08:12:29 it seems he finished the meeting or someone else started with the same account 08:12:34 let's wait for him to join again 08:12:53 in the meantime 08:13:44 back again 08:14:12 #info showing how to create a Task in JIRA https://wiki.opnfv.org/display/functest/JIRA+management#JIRAmanagement-HowtocreateaTASKinJIRA? 08:15:18 damn 08:15:26 someone else is using the same account 08:17:00 hey morgan_2 08:17:08 it seems we have a collision 08:17:16 seems there are 2 // meetings on the GTM... 08:18:50 yes 08:18:52 what do we do? 08:19:26 we can continue in IRC 08:19:29 sure 08:19:41 I will try to see which project is in collision with us 08:19:53 sure 08:19:56 let's continue 08:20:07 we were explaining "how to create a task" 08:20:28 I "infoed" some information 08:20:44 #info list of EPICS available on the page 08:21:00 #info EPICs correspond to the main feature we will include in C release 08:21:21 #info a priori all EPICs listed for C release, if you need a new one, we can discuss during the weekly meeting 08:21:34 ok? 08:21:39 yes 08:21:49 #topic status on ARM 08:21:59 ciprian-barbu: do you have document to share... 08:22:09 hmm ... sorry, no 08:22:17 I didn't think about that 08:22:23 I can summarize 08:22:50 we are currently trying to integrate in CI 08:22:59 ciprian-barbu: can you use #info? 08:23:07 sure 08:23:08 so it keeps recorded :) 08:23:24 the things you want to be in the minutes of meeting, 08:23:25 thanks 08:23:31 #info We at armband are currently trying to integrate our work in CI 08:24:01 #info for now we have a set of jobs at https://build.opnfv.org/ci/view/armband/ 08:24:26 #info there is a job for building and one for running functest, we are working on deploy 08:25:23 #info we currently have run functest manually for os-odl_l2-nofeature-ha, with most of the tests passing 08:25:37 just to info also some info on the installation, can we add armband deploy a Brahmaputra based on fuel solution in ANEA lab 08:25:49 #info and we are working on making the functest-fuel-arm-pod1-daily-master run when triggered 08:26:02 sounds good 08:26:15 should I type in that or? 08:26:22 when you say most of the tests passing, which ones do not pass... 08:26:44 #info currently rally heat is failing for some unknown reason 08:26:58 we also had some heat failures 08:27:26 #info also vims will not work any time soon, initial investigation showed it might take some effort to make it run on ARM 08:28:19 #info tempest fails around 20 testcases, but we tried to compare the results with the ones on an x86 deployment using VMs, and we see similar but not exactly the same errors 08:28:30 ok Valentin our MC vIMS will be back in June, assuming that we also planned to deploy an ARM based solution (machiens are ready), we shall be able to provide support 08:28:54 for Tempest do not hesitate to share your results with viktor_nokia 08:29:10 morgan_2 thanks, that's good to know 08:30:02 I wanted to share some results, but I have a few things to get straight with tempest 08:30:03 ciprian-barbu: Orange will also come back to you for the installation of the fuel based solution (joid will not support these arm64 in C release) 08:30:23 morgan_2: ok, noted 08:30:54 I don't know what more to add, we are trying to finish the integration this week 08:30:58 ok good job for the integration 08:31:06 yes, good job 08:31:15 thanks guys :) 08:31:18 ciprian-barbu: did you get enough help from yardstick guys? 08:31:20 shall it appear in CI as a scenario? 08:31:37 sorry if I wasn't so useful, my yardstick knowledge is very limited :) 08:31:52 jose_lausuch: I haven't been talking to them, we don't have that much manpower for yardstick ... 08:31:59 ok 08:33:01 arm-pod1 has been added to http://testresults.opnfv.org/dashboard/# 08:33:21 this is it for now, more updates soon, next Tuesday I will probably be in Easter vacation (Orthodox) 08:33:28 (not the target dashboard for C release, but practicale to test quickly) 08:34:20 ok 08:34:27 ok thanks ciprian-barbu 08:34:43 #topic how to functest for C release 08:34:54 the idea was to show the presentation and discuss it 08:35:12 #link http://opnfv.fr/opnfv_how_to_C_release/#/ 08:35:25 is there any people from feature project on the chan? 08:35:37 morgan_2: yes, but I'm not sure if it makes sense here, since not many people (anyone?) from feature projects joined 08:35:52 agree 08:36:01 maybe for thursday? 08:36:16 we might discuss it also during Colorado meeting today 08:36:23 at least I have to provide a template 08:36:25 :) 08:36:34 #info presentation not possible due to GTM issue and lack of feature project PTL 08:36:57 one issue will be that most of the new PTLs are based in China, the Thursday weekly meeting is not convenient for them 08:37:14 I can maybe record a shor video to explain the presentation 08:37:28 yes... 08:37:34 #action morgan_2 make video of how to functest for C release 08:37:35 that would help I think 08:37:46 it should be better coordinated 08:37:50 by release manager or someone 08:38:22 #action morgan_2 ask release manager how we can reach the PTLx of feature projects to discuss dependencies... 08:38:50 ok 08:38:58 so we will be able to split the AoB 08:39:07 can we review the Jiras? 08:39:12 and start a new sprint 08:39:32 yes, if we have time let's agree for the CLI as well 08:39:40 and assing the task/tasks 08:39:46 because it might reuqire some work :) 08:39:48 #topic CLI 08:40:17 #info proposed CLI: https://wiki.opnfv.org/display/functest/Functest+CLI 08:40:24 does everyone agrees? 08:40:30 comments/additions/suggestions? 08:40:42 serena-zte: do you like it better now? :) 08:40:48 yeah 08:40:57 It looks fine to me 08:41:02 ok, thanks 08:41:18 as a comment I mentioned in the wiki that we could add some reporting but I think a first draft with the mandaotry stuff (version, env, run) is fine 08:41:31 it will nto be a big deal to add reporting 08:41:36 anyone else? opinion from commiters? viktor_nokia juhak ? 08:41:40 looks good 08:41:42 any volunteer for the implementation? 08:41:59 I volunteer for the first template 08:42:12 and if some one can help with the development would be great 08:42:30 I can probably help 08:42:36 I will create the needed scripts templates in the proper directory, etc 08:42:37 me too 08:42:44 i too 08:42:44 I'm restructuring the directories in functest 08:42:49 and adding more consistency 08:42:58 count me in too 08:42:59 OK 08:43:02 ok 08:43:03 thanks 08:43:07 I have other two tasks, so Is it still available for new tasks? 08:43:37 yes... 08:43:50 serena-zte: as you whish, but let's have priorities, and the tasks you and everone are already working on, should have more priority 08:44:02 good transition to 08:44:04 this is not something that blocks the CI or anything 08:44:08 so it's not urgent 08:44:11 can be done more slowly 08:44:12 #topic JIRA 08:44:22 ok 08:44:25 #link https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=59&view=planning.nodetail 08:44:41 I got a question from Cedric, I would be OK to refactor ODL python script 08:44:54 yes 08:44:58 but I think raghavendrachari already intiated something 08:45:22 raghavendrachari: did you restart something or was it the first commit you made some months ago? 08:45:24 yes, now am deriving test cases as many as possible 08:45:25 shall we follow with the sprints ? 08:45:47 raghavendrachari: can you give a short update on the refactoring then? 08:46:31 that python script has done , but when we want to trigger pybot we need to use os.command() 08:46:57 raghavendrachari: is it in gerrit? 08:46:59 can we have a look? 08:47:04 ok 08:47:24 no i'll send to ur mail now 08:47:36 raghavendrachari: no, better push a commit for review 08:47:38 pyot is already in python so it shall be possible to avoid python => system => python 08:47:56 so that other can also review it :) 08:47:58 cedric is volunteer to help on this topic 08:48:05 please add him 08:48:06 so definitively, review is better than mail 08:48:22 ok i'll do it 08:48:26 ok, thanks 08:48:30 #action raghavendrachari push code odl refactoring in review 08:48:49 #action raghavendrachari sync with Cedric Ollivier for odl refactoring 08:49:03 serena-zte: any update on the API side? 08:49:28 I have study pyswagger, it is a unittest-oriented 08:49:57 something like swagger-codegen 08:50:05 but we need swagger-ui 08:50:25 and I check all swagger related projects in github 08:51:17 no one implement swagger-ui for a tornado framework 08:51:29 so i think I still need to write one 08:51:36 ok thanks 08:52:00 so...... write one by myself?? 08:52:06 #info Test API pyswagger studied but unit test oriented 08:52:25 #info swagger-ui wouldbe needed but not created for torando framework 08:53:28 I am not able to estimate the difficulty of porting swagger-ui to tornado 08:53:53 what about migrating the API in a python framework that would integrate swagger-ui 08:53:56 it is maybe easier 08:53:58 ... 08:54:24 juraj has an action point to evaluate the migration of the backend from mongo to Elastic search 08:54:33 tornado is coroutine oriented, if the coroutine is not very important, I think we can 08:54:40 it means that tornado can be challenged 08:55:30 #info tornado can be challenged to see if any other web framework supporting swagger-ui could be used 08:55:43 shall we start a new print today? 08:56:13 both flask and django have supported swagger-ui 08:56:24 #action all update your Jira status , creation of a new sprint tonight 08:57:15 #info reporting => integration of version parameter in results, issue with Brahmaputra (as the API additional parameters do not exist) 08:57:19 what is the cadence for spirnts? 08:57:21 3 weeks? 08:57:23 3 weeks 08:57:28 ok 08:57:45 we have probably 2 sprints to finalize the code for C 08:58:09 initially we announced end of May but with Openstack summit, Plugfest,... mid May seems more reasonable 08:58:32 mid june... 08:58:40 so 2 sprints of 3 weeks seem fine 08:58:52 to mee too 08:59:21 #info 2 sprints of 3 weeks for Functest before first freeze (internal feature freezeĆ  08:59:32 any other topic you want to share this morning 09:00:21 nope 09:00:23 ok jose you can close the meeting, have a good week 09:00:26 sure 09:00:30 #closemeeting 09:00:31 sorry, the conclusion of the Test API?do I still need to work on it? 09:00:35 #endmeeting