08:00:53 #startmeeting Functest weekly meeting october 18th 08:00:53 Meeting started Tue Oct 18 08:00:53 2016 UTC. The chair is jose_lausuch. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:53 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:00:53 The meeting name has been set to 'functest_weekly_meeting_october_18th' 08:01:11 #topic role call 08:01:17 #info Cristina Pauna (ENEA) 08:01:22 #info Luke Hinds 08:01:25 #info Juha Kosonen 08:01:27 #info Morgan Richomme 08:01:27 #info Hideyasu_ool 08:01:34 #info SerenaFeng 08:01:50 #info HelenYao 08:02:36 #info agenda for today here: https://wiki.opnfv.org/display/functest/Functest+Meeting#FunctestMeeting-18/10(8UTC) 08:02:46 #info previous minutes: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-functest/2016/opnfv-functest.2016-10-11-08.01.html 08:02:52 #info Jose Lausuch 08:03:15 #topic Action point follow-up 08:03:33 #info initiate presentation with proposals for the - and -- alreday referenced. Not ready yet. 08:03:52 morgan_orange: we still need to work onthat 08:03:57 we have this week left :) 08:04:15 jose_lausuch: yep, I will initiate something this afternoon and tomorrow 08:04:16 #action: morgan_orange jose_lausuch initiate presentation with proposals for the - and -- alreday referenced 08:04:25 let's sync on that 08:04:49 #info morgan_orange modify Info in repo + inform TSC. Done. 08:04:55 right? 08:04:58 yes 08:05:11 #info morgan_orange see how to trigger unit testing on commit on master 08:05:14 status? 08:05:28 #info I think we can use storperf as best practice 08:05:37 #link https://build.opnfv.org/ci/view/storperf/job/storperf-verify-master/81/testReport/ 08:06:01 #info creation of a dedicated tests dir submitted: https://gerrit.opnfv.org/gerrit/#/c/23233/ 08:06:06 ok, that sounds and looks good 08:06:19 #info with an illustration with unit test for CLI (I let utilities for the internship) 08:06:35 #info I will submit a patch in releng to follow stroperf view to trigger unittests 08:06:39 I'll have a look later 08:06:44 ok 08:07:05 #info SerenaFeng jose_lausuch review proposal from morgan_orange. 08:07:15 well, everyone is welcome to review it 08:07:23 I already sent comments 08:07:42 it was a nice reading yesterday evening during a flight :) 08:07:50 https://gerrit.opnfv.org/gerrit/#/c/23233/ this submit? 08:08:29 #info I sent some comments to the email thread but I agree on the idea exposed in the presentation 08:08:40 SerenaFeng: needs merge 08:08:40 i think it was the ppt proposal on impact on CI evolution on tests 08:08:47 yes 08:08:58 you huge slides :) 08:09:07 Ok, please give me a link? 08:09:12 it took a while to get all the small boxes 08:09:22 SerenaFeng: it was sent by email last week 08:09:34 ok, maybe I ignore it 08:09:35 SerenaFeng: I put it on the wiki and give you the link 08:09:45 I will find and review it 08:10:22 #action SerenaFeng and others review CI proposal from Morgan 08:10:38 #info jose_lausuch identify which packages are installed in the docker build process and for what reason. Done. https://wiki.opnfv.org/display/functest/Docker+images+slicing 08:10:40 jose_lausuch: just saw your feedback, i will have a look 08:10:58 morgan_orange: ok, not much, I agree with everything 08:11:11 #info HelenYao SerenaFeng jose_lausuch study impact on a massive dockerization of feature. 08:11:22 #info Ongoing. Some important impacts detected. https://wiki.opnfv.org/display/functest/Docker+images+slicing 08:11:33 we will have a section later to discuss a bit 08:11:55 #info morgan_orange create a JIRA_epic on docker topic 08:11:57 ? 08:12:32 morgan_orange: I think it is created,right? 08:12:46 jose_lausuch: yes 08:12:47 morgan_orange: I looked at your slide and the whole process seems great. it may need to collabrate closely with docker slicing to make each other aligned 08:13:08 #info Done https://jira.opnfv.org/browse/FUNCTEST-509 08:13:40 HelenYao: sure, it has to be correlated 08:14:00 HelenYao: feel free to provide you comments in the email thread 08:14:10 SerenaFeng: https://wiki.opnfv.org/display/testing/Testing+Danube+discussions 08:14:13 jose_lausuch: sure 08:14:13 we will discuss it again next week I guess 08:14:29 #info morgan_orange ask for functest gerrit alias. Done. We have alias for contributors and commiters 08:14:32 I think I will move from the ppt to the wiki after barcelona 08:15:02 https://gerrit.opnfv.org/gerrit/#/groups/self 08:15:16 oops someone deleted the functest-contributors group! 08:16:03 I'll create later again 08:16:12 the group is there 08:16:18 i can see my name in the group 08:16:20 sorry 08:16:23 #link https://gerrit.opnfv.org/gerrit/#/admin/groups/ 08:16:30 it is not there 08:16:55 do you see it? 08:17:05 yes 08:17:12 CLA Accepted - Individual 08:17:12 functest-contributors 08:17:15 ah ok, I know what happens 08:17:27 functest-contributors is not visible to all 08:17:32 I removed myself from the group and I can't longer seee it 08:17:34 haha 08:17:39 oops 08:17:44 can you add me? do you have rights? 08:17:50 let me try 08:18:03 done 08:18:08 thanks 08:18:16 same for me, I can see functest-committers but not contributors 08:18:21 I'll include the commiters also to that group 08:18:21 only the people in the group can see it? 08:18:26 yes 08:18:27 me too 08:18:50 morgan_orange: you should be able to see it 08:18:52 only in functest-committers group 08:19:00 there is only five people in the contributors group 08:19:08 ok 08:19:15 I'll do it later 08:19:16 back 08:19:16 #info morgan_orange check copyright stuff with Ray. 08:19:22 Colum Gaynor 08:19:22 colum.gaynor@nokia.com 08:19:22 David Blaisonneau 08:19:22 david.blaisonneau@orange.com 08:19:22 Helen Yao 08:19:22 yaohelan@huawei.com 08:19:22 Jose Lausuch 08:19:23 jose.lausuch@ericsson.com 08:19:23 Juha Haapavirta 08:19:24 juha.haapavirta@nokia.com 08:19:28 the whole list 08:20:04 ok let's fix it offline, we have more people.. 08:20:20 #info I checked with Ray and we should include the license header in all the files 08:20:34 #info disucssion in progress between Ray and Cedric 08:20:58 #info jose_lausuch: ollivier morgan_orange SerenaFeng final decision on patch https://gerrit.opnfv.org/gerrit/#/c/22487/ 08:21:26 I would like to merge today all pending patches 08:21:33 we have too many dependencies alreaduy 08:22:01 can we discuss later about this patch as well? 08:22:27 let;s move to the first topic, its getting late :) 08:22:33 a lot of actions 08:22:34 ok 08:22:36 #topic JIRA best practices 08:22:38 discuss it later 08:22:57 I'd like to share my view about JIRA and gerrit management 08:23:06 #info Recommendation is to create an EPIC for a bug story or activity and create tasks within that epic. 08:23:29 #info The tasks must be broken down so that it doesn't require a tremendous amount of work. Something that be achieved in a couple of days. 08:23:46 #info a JIRA Task does not correspond to 1 commit. 1 task can be completed with 1 or more commits. The idea is not to create JIRA tasks for small changes. 08:24:14 #info If sometimes, the change is obvious, it might not include a JIRA reference at all. It is not a mandatory, just optional. 08:24:34 #info However, for important changes, we must have JIRA epic/tasks created for it. 08:24:45 Do you agree? Shall we vote on this? 08:24:49 agree 08:24:54 I came across a page about JIRA mgmt which is quite useful and it was created by jose_lausuch this Apr. 08:25:04 yes 08:25:06 https://wiki.opnfv.org/display/functest/JIRA+management 08:25:28 i agree on the new points here 08:25:36 #info https://wiki.opnfv.org/display/functest/JIRA+management 08:25:42 we many consolidate all into the page 08:25:46 many = may 08:25:49 #action jose_lausuch include new points in that wiki 08:25:59 #agreed 08:26:03 agree 08:26:09 we can create some usual epic for usual tasks 08:26:20 such as a code refactor epic 08:26:37 will we go thru all the epics of D release sometime? 08:26:37 or else theses have no epic to relate to 08:26:41 but a code refactor could be related to anything 08:26:55 HelenYao: after Barcelona 08:27:03 once we have all clear 08:27:20 sounds good 08:27:21 we also need to know available resources, people , ... 08:27:44 anyway we are refactoring the framework, let's see after that 08:27:49 SerenaFeng: if its a test api refactor, we could have an epic for it 08:27:55 ya 08:28:04 maybe, we should have framework refactor 08:28:14 I'll think about it 08:28:17 I think we have one 08:28:26 but we should have everything clear after barcelona 08:28:26 yes.. 08:28:28 one small point to add about task, the description should be of enough information so that the one w/o background info can understand the task 08:28:36 who is gonna work on what 08:28:44 https://jira.opnfv.org/browse/FUNCTEST-332 08:29:02 SerenaFeng: yes, thanks 08:29:14 I think this one is used to the framework refactor 08:29:21 HelenYao: yes, description is important 08:29:21 we just need to rename it 08:29:35 After Barcelona, we should be able to allocate people to tasks and start the sprints... 08:29:52 and see what we will be able to achieve and what will be for E, F, .. 08:30:09 we also have interns :) 08:30:10 need to plan a JIRA funny session 08:30:24 aka as "triage" 08:30:33 yes 08:30:51 it sounds more "release management" 08:30:59 ok, next topic 08:31:08 #info Testcase class refactoring 08:31:32 #link https://gerrit.opnfv.org/gerrit/#/c/22921/ 08:31:39 cedric is not here.... mmmm 08:31:47 shall we postpone this? 08:31:59 #info with illustration on odl test 08:32:05 #info Cedric proposed a way to converge all the test cases created in functest. 08:32:18 #info this will help consolidating the framework being more robust and structured. 08:32:26 I think we just need to agree and maybe start allocating adaptation for the existing cases 08:32:38 I'd like to have a short discussion about if we change the current test cases to adopt this 08:32:39 yes 08:32:51 #info all the new test cases should be implemented the same way 08:32:52 #info refactoring is usefull to manage feature project in a consistent way by imposing methods 08:32:59 its a good exercise 08:33:20 yes 08:33:39 would it make sense for example to adapt vping ort tempest to this classes? 08:33:43 and fortunately the number of cases is finite.. 08:34:06 I think so, I do not think it is so difficult 08:34:18 ok 08:34:38 and it is easier to do it now than later... 08:34:45 yeah, agreed 08:34:48 also the feature test cases (promise, doctor, ..) 08:34:55 SerenaFeng: ? 08:35:01 agreed 08:35:03 you refactored vping 08:35:06 ok 08:35:07 will be hard for me before Barcelona, but you can action me for some cases 08:35:11 new refactor :) 08:35:22 there is no rush, we can do it progressively 08:35:27 refactor it before Barcelona? 08:35:29 morgan_orange: no need to have it before barcelona 08:35:30 but for any new case, we should do it 08:35:36 vRouter for example is a good example :) 08:35:44 of vEPC 08:35:50 i'd like to be part of refactoring 08:35:59 #info agree on refactor the existing test cases to thenew Testcase class 08:36:05 moreover this refactoring is a good way to jump into the project 08:36:15 HelenYao: ok, thanks 08:36:44 yes 08:36:53 its a bit of work, but not complex 08:37:02 ok, good 08:37:16 Yes 08:37:17 we will distribute the tasks sonn 08:37:20 #topic Colorado 2.0: what do we have to do (release notes, doc, ...) 08:37:24 soon* 08:37:31 morgan_orange ? 08:37:42 I think we need to update the release notes and let render the documentation for C2.0 08:37:45 I should admit I did not attend the release meeting recently... 08:37:54 I do not think we have new features 08:37:59 but the scenarios changes a little bit 08:38:04 scores changes 08:38:07 yes 08:38:08 and onos is back in Apex 08:38:31 so as far as I can see, only work => new release note 08:38:34 we need to update the release notes before the release 08:38:34 other docs OK 08:38:42 and have a snapshot of the scoring 08:38:48 we may check also the JIRA related to Colorado 1 08:39:27 #action morgan_orange jose_lausuch review scenario changes for the release notes, and check jira 08:39:54 #info release date Colroado 2.0: doc and test complete 24/10 08:39:56 #action jose_lausuch tag stable branch next week 08:40:06 #info release date COlorado 2.0: 27/10 08:40:11 we will be in barcelona... 08:40:16 yes 08:40:27 maybe we can spend 10 minutes on that 08:40:50 looks like evening tasks....not sure we could visit the Sagrada Familia 08:41:01 let's say 1h... 08:41:05 :) 08:41:06 ok 08:41:14 I visited it last year 08:41:22 I do not think there are new features 08:41:26 a side question, when will u arrive in Barcelona 08:41:27 nope 08:41:28 just new scenarios 08:41:35 Monday evening for me 08:41:42 ok, let's jump 1 topic 08:41:43 #topic OpenStack summit 08:41:50 good transition 08:41:50 who will be there? 08:41:59 +1 08:42:01 +1 08:42:02 +1 08:42:06 +1 08:42:07 Cedric +1 08:42:10 David +1 08:42:13 I will be there on Oct.23 08:42:19 Valentin still do not know 08:42:29 Sagrada Familia is my target visit 08:42:31 #info people in Barcelona: SerenaFeng morgan_orange HelenYao juhak Cedric David jose_lausuch (Valentin) 08:42:47 when is planned our meetup? 08:42:57 HelenYao: if you have time do not miss other Gaudi building 08:43:01 morgan_orange: can you link the wiki? 08:43:24 morgan_orange: i did a rough search, Gaudi is everywhere in Barcelona 08:43:25 you should visit the gothic block 08:43:45 #link https://wiki.opnfv.org/display/EVNT/OPNFV+at+OpenStack-Barcelona 08:43:53 and the Born area 08:44:01 #info Functest Meetup planned on Wednesday morning 9-13h 08:44:01 jose_lausuch: u may drop us a tour guide for reference :) 08:44:15 HelenYao: maybe, but we might get lost :p 08:44:26 I've been there only twice 08:44:48 better than me. i've been there 0 08:44:59 #info Functest meeting planned for Wednesday 26th , 9:00-13:00 08:45:14 HelenYao: if you have time to prepare your travel, you may watch https://en.wikipedia.org/wiki/L%27Auberge_Espagnole, it happens in Barcelona and it is funny .. 08:45:28 nice movie :) 08:45:40 morgan_orange: i will check it out, thx 08:46:21 #info discussion with Bitergia about testing dashboard on Thursday at 14:00-1:00 08:46:37 we may plan a Functest social within one of the several OpenStack socials.... 08:46:45 yes 08:46:57 #undo 08:47:04 ok, let's move on 08:47:07 #info discussion with Bitergia about testing dashboard on Thursday at 14:00-16:00 08:47:17 oops sorry :) 08:47:19 thanks 08:47:22 #topic Docker discussion 08:47:28 the idea of the meetup is to have a good view for task allocation 08:47:33 yes 08:47:43 I hope its enough time... 08:47:43 and be reasonable on what we can achieve.. 08:47:52 release is in march 08:47:57 it is on Wednesday, I leave on Friday afternoon 08:48:09 we may have additional slots if needed 08:48:12 I leve thursday evening 08:48:21 leave* 08:48:25 #info Proposal for slicing our docker image: https://wiki.opnfv.org/display/functest/Docker+images+slicing 08:48:26 I leave on Sat. 08:48:28 I leave on Sunday evening 08:48:37 #info the idea is to have 1 image for Functest core testcases, 1 for feature feature, 1 for sdn controllers, 1 per each vnf (vIMS, vRouter, ...) 08:48:47 #info in the comments section there are already some proposals about how to orchestrate all the containers from a central one 08:48:56 #info However, this change increases the complexity of the Docker containers management in CI ==> is it worth it? 08:49:09 do we need 1 for sdn, are they not part of the core? 08:49:11 SerenaFeng: HelenYao I tested yesterday the docker api 08:49:15 1 for features and 1 per vnf 08:49:28 well 08:49:31 the multiplication of dockers will lead to complexity 08:49:38 we could consider sdn core yes 08:49:43 the idea is "just" to keep the size under control, no? 08:49:43 I dont mind 08:49:49 yes 08:49:58 in the CI evolution, I suggets to merged smoke and sdn 08:50:06 sdn tests take 5 minutes 08:50:11 HelenYao proposed initially 1 image / feature test 08:50:14 and are part of the core tests for a scenario 08:50:43 it depends of the feature but sometimes it is a bit overkill 08:50:47 shall we start with minimum? 08:50:53 it depends if we want to have a systematicall approach 08:51:09 there is one benefit about 1 image/feature, we can monitor the code change of the feature and rebuild the image accordingly 08:51:12 I think we can merge sdn to core, since there's no much extra sdn to be added now 08:51:34 still keep one image for all features 08:51:37 1 core(functest+odl), 1(feature tests), 1(vims), 1(vnfX),.. 08:51:38 sometimes some features are very light... 08:51:55 jose_lausuch agree 08:52:06 jose_lausuch: agree too (at least in first steps) 08:52:14 sdn is not only odl, onos as well right? 08:52:18 yes 08:52:23 ok, agree 08:52:25 sdn = odl, onos 08:52:34 #info agreed 1 core(functest+odl), 1(feature tests), 1(vims), 1(vnfX),.. 08:52:52 #undo 08:52:52 Removing item from minutes: 08:52:54 agreed 08:52:58 #agreed 08:53:05 #info agreed 1 core(functest+sdn), 1(feature tests), 1(vims), 1(vnfX),.. 08:53:23 about the api 08:53:39 we need to do a small change on all CI pods 08:53:52 its easy, but someone has to do it 08:54:10 someone with the CI keys to all pods... 08:54:16 or each lab owner... 08:54:37 we need to put a requirement in pharos 08:54:53 can we we provide the script, let the lab owner do it for us? 08:54:56 it also increases a bit the complexity for the end users 08:55:02 yes 08:55:14 we can put the script into the code 08:55:14 but the way you described is not for all OS' 08:55:28 i have been thinking about the script 08:55:28 we need to investigate at least ubuntu/redhat 08:55:40 and centos? 08:55:41 and need sudo rights 08:55:47 yes 08:55:51 which we normally have 08:55:59 centos should be the same as redhat 08:56:05 I can work out the script for centos/ubuntu/redhat 08:56:33 #action HelenYao prepare script to update jumphost with the needed docker daemon flags 08:56:36 is there any other os that needs to be supported? 08:56:36 thanks 08:56:46 for now that should be fine 08:56:57 I can test it on LF labs 08:57:03 and some ericsson labs 08:57:13 ok, running out of time 08:57:21 #topic Internships 08:57:27 #info we performed a first interview and have another one this week. 08:57:32 jose_lausuch: good. I will contact u once it is ready 08:57:38 HelenYao: ok 08:57:42 3 possible candidates for intern projects in Functest. 08:57:50 It seems our topics are attractive :) 08:58:17 yes 08:58:31 #info Added a new internship projet to implement security groups https://wiki.opnfv.org/display/DEV/Intern-projects-page 08:58:32 and it seems that it is internship time in India :) 08:58:56 we have an interview this week as well 08:59:19 #topic AoB 08:59:20 all the candidates are in India? 08:59:30 HelenYao: for now yes \ 08:59:52 is there any plan for enforcing python style? 08:59:53 thats why its internship time there it seems 08:59:54 :) 09:00:04 other projects are leveraging flake8 09:00:06 I'd like to change the name of result_collection_api to testapi, is that ok? 09:00:07 enforcing python style? 09:00:16 since we always use testapi now 09:00:25 SerenaFeng: yes 09:00:28 SerenaFeng: no objections from my side 09:00:37 i ran flake8 against functest and all passed which shows we have good coding habit 09:00:45 yes 09:00:57 we have a gerrit gate in Functest for flake8 09:01:07 not in all opnfv repos 09:01:14 but we requested it 09:01:16 where is the gate? 09:01:27 triggered in Jenkins 09:01:34 i did a search in the functest code and did not see any flake8 check 09:01:35 for each commit 09:01:44 its a CI thing 09:01:51 common for all opnfv repos 09:02:03 see. i will check it out 09:02:43 ok 09:02:58