07:32:21 #startmeeting qtip 07:32:21 Meeting started Mon Mar 6 07:32:21 2017 UTC. The chair is yujunz. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:32:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:32:21 The meeting name has been set to 'qtip' 07:32:29 #topic roll call 07:32:33 #info Yujun Zhang 07:32:39 #info akhilbatra 07:33:06 #info Taseer 07:33:46 Agenda for today 07:33:47 #link https://etherpad.opnfv.org/p/qtip-meetings-2017-03-06 07:35:09 #topic Action followup 07:35:19 #info AP1 all review api requirement and comment https://goo.gl/UrFzlR 07:35:28 Have you done it, SerenaFeng? 07:35:35 nope 07:35:51 OK, when do you plan to do it? 07:36:31 I planed this morning, but occupied by a job interview 07:36:37 I will do it after the meeting 07:37:09 Good, thanks. 07:37:13 #info AP2 all make proposals for OPNFV Summit Beijing before Mar 27th https://etherpad.opnfv.org/p/qtip-opnfv-summit-beijing 07:37:47 There is some rumor that Linux Foundation may invite interns to the summit 07:37:59 Or one can directly review this patch https://gerrit.opnfv.org/gerrit/#/c/29815/4 07:37:59 It is adhering the requirements 07:38:11 So you two can make proposal of some talks also, akhilbatra Taseer 07:38:24 Yes, but I don't whether all the interns will be invited 07:38:34 We can? :) 07:38:43 It is not confirmed 07:38:46 But possible 07:38:47 ok 07:38:57 I don't know, it depends on LF 07:39:36 I think if your proposal is accepted. The chance of getting invited will increase significantly 07:40:42 #topic Status update from the team 07:40:43 But we can attend, even if we don't give talks ? 07:40:46 talk proposal should be on the work we are doing or something else 07:40:49 ? 07:41:09 The work you are doing 07:41:13 Or the work you are going to do 07:41:31 Or something that would be interested by the community 07:41:38 ok thanks 07:42:06 The non-speaker need to pay the ticket 07:42:17 The speakers are sponsored by LF 07:42:26 For interns, I'm not sure 07:42:30 Okay 07:42:34 It is the first time I get this rumor 07:42:35 the rule are for us 07:43:08 for the intern, if he/she is invited the OPNFV will pay his/her accomodation/transport and tickets 07:43:18 Thanks for the information 07:44:15 Who go first on status update? 07:44:16 OPNFV plan to do but not decide yet 07:45:39 On my part, I was cleaning up the code for Danube release 07:46:14 And for the missing runner module, I have planned to execute collector and reporter directly in ansible playbook 07:46:40 Hard code them for this release 07:46:56 zhihui_ Taseer could you work together to make it work? 07:47:09 ok. 07:47:12 I implement ansible_driver and rework env.py. Please feel free to review my patches. 07:47:17 Thank you. 07:47:21 Who's next? 07:48:03 no work from my side :) :( 07:48:09 I have implemented basic prototype of api. 07:48:09 request and response parameters have to be worked on now 07:48:23 Great 07:48:39 Have you prepare also the document and test, akhilbatra 07:48:52 On my local env, I can tirgger ansible driver to execute dhrystone test. 07:50:22 Great. The key mission is to make the framework "complete". We can expand to more api and test in next release 07:50:26 I plan to refactor the rest of compute test case. Then we can let qtip daily ci job to run these test. 07:50:32 document I will do. 07:50:32 I dont intend to make whole test coverage right now. 07:50:32 because right now all responses are `Not implemented` right now. 07:50:32 one test will suffice to see if api is running. 07:51:09 OK, when I say test, I mean give some sample on how api will be tested 07:51:16 The coverage is less important in Danube release 07:51:33 ok will do that :) 07:51:35 About unit test, can we finish it after the code freeze. 07:51:58 OK, thanks 07:52:08 #topic Danube release status update https://etherpad.opnfv.org/p/qtip-danube 07:52:50 All, please update status on the page now and back to IRC when you have done 07:57:33 OK, let's continue 07:57:59 I cancelled the tasks about async jobs and native runners 07:58:14 We are thinking about implement qtip as ansible module. 07:58:42 Because Ansible has everything we need as a runner, and we don't want to re-invent wheels 07:59:44 qtip-cli will be kept as the user interface in console. It's like qtip runs ansible, ansible uses qtip modules 07:59:56 We'll see how to do it in release E 08:00:39 #topic active sprint followup https://jira.opnfv.org/secure/RapidBoard.jspa?projectKey=QTIP&rapidView=135 08:01:28 You may update the JIRA tickets now and come back to the IRC meeting after 5 minutes 08:01:58 It seems we haven't got used to update them in daily work yet. Let's do it on meeting instead :-) 08:04:22 It also seems I didn't create jira ticket for my works. 08:05:27 OK, let's continue 08:05:42 #topic CI status https://build.opnfv.org/ci/view/qtip/ 08:06:00 pod3 is down, zhihui_? 08:06:19 Zte pods met problems when running "docker pull" 08:06:46 Is anybody handling this issue now? 08:06:51 me 08:07:09 Thanks, we shall revisit next week 08:07:24 Julien build the local docker cache 08:07:29 #topic new tasks in JIRA https://jira.opnfv.org/issues/?filter=11198 08:07:38 build -> built 08:07:49 OK, I saw the ticket about it now 08:08:03 #link https://jira.opnfv.org/browse/QTIP-219 08:08:26 #topic AoB 08:08:31 After updating docker, this is solved now. 08:08:50 So pod3 is recovered? 08:09:04 yes 08:09:26 Great. When will be next execution 08:09:51 tomorrow morning. 08:09:58 I see 08:10:08 #info MS7 stable branch on Mar 10th https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-March/015342.html 08:10:29 I think we shall branch until the deadline 08:10:51 It will be created by gerrit admin 08:11:14 Before that, I may block new features which are not in our danube plan. 08:11:27 So don't be surprised if you get -2 on some submit :-) 08:11:46 haha~ 08:11:49 I prefer to use -1 08:12:01 Openstack uses -2 for blocking 08:12:06 -2 is too harsh 08:12:09 I will comment so it won't be so rude 08:12:09 so famous -1 will become to famous -2? 08:13:22 #link https://review.openstack.org/#/c/423084/ 08:13:25 In my current patch I have included basic mapping and response details for async jobs which are now part of E release. 08:13:25 Shall I keep serving them as Non implemented or It qualifies for -2 now? 08:13:26 See example here 08:13:42 "Proceedural -2 for freeze. If you wish to request an exemption please submit an email to openstack-dev with the starting subject line of '[FFE][requirements]' with the reasoning behind your request." 08:14:22 I'll check the patch later. 08:14:30 I should we do with cli and api 08:14:32 ok thanks 08:14:41 I don't think they can catch up before that 08:14:45 It is just procedural -2. Don't get discouraged on it. Nothing serious 08:15:42 #info license tool in qtip/third-party/License 08:15:55 All code and configuration file need license header 08:16:20 You may use a third party tool to check it before you submit a patch to gerrit for review 08:16:32 There is README in it. It should be easy to use 08:16:50 #info intern project review: qtip-cli 2nd period next week 08:17:09 Taseer will send invitation for 2nd period review of qtip-cli next week 08:17:30 #action Taseer to send invitation of qtip-cli 2nd review next week 08:17:41 Alright, anything else? 08:18:19 Nope? 08:18:32 nope from me 08:18:55 Thank you all, bye 08:18:57 #endmeeting