08:00:32 #startmeeting qtip 08:00:32 Meeting started Wed Sep 28 08:00:32 2016 UTC. The chair is yujunz. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:00:32 The meeting name has been set to 'qtip' 08:00:53 #chair zhihui_wu 08:00:53 Current chairs: yujunz zhihui_wu 08:01:03 #info zhihui 08:01:20 Let's wait a few minutes 08:01:54 agenda https://etherpad.opnfv.org/p/qtip-meetings-2016-09-28 08:02:00 #link https://etherpad.opnfv.org/p/qtip-meetings-2016-09-28 08:02:09 #topic rollcall 08:02:29 #info Yujun Zhang 08:04:42 #topic Project vision 08:04:53 #link https://etherpad.opnfv.org/p/qtip-vision 08:05:08 This is the **long term** vision for qtip project 08:05:23 It may take several release to complete. 08:06:12 QTIP shall focus on performance benchmarking and aim to boost the platform benchmark to extreme 08:06:27 The whole chain would be Benchmark->Report->Analysis->Predict->Improve 08:06:53 We shall start with benchmark and reporting 08:07:32 The rest steps are planned for future but need to be taken into consideration during development 08:07:46 Any questions? 08:08:13 No 08:08:16 Good 08:08:50 I think we can create jira ticket about what we plan to do. 08:08:53 OK, let's move on to next topic 08:09:12 Yes, we have created many jira tickets 08:09:18 Ok 08:09:40 I'll try to categorize them. 08:09:45 I suggest EPIC 08:09:53 But first we need to define the target 08:09:56 each EPIC includes some tasks 08:09:59 Then we know the priority 08:10:41 #topic Release D planning 08:11:06 I have sent intention to participate release D 08:11:13 #link http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-September/012840.html 08:11:39 Here is the etherpad for brainstorming 08:11:41 #link https://etherpad.opnfv.org/p/qtip-release-d 08:12:53 Currently we are a small group. So I put friendlyness as one of the target 08:13:24 Friendly means both on api and documents 08:13:28 I agree with you 08:14:09 And we want to create a typical benchmark suite for dedicated purpose 08:14:29 For example, to evaluate a Pharos lab, providing a qtip score 08:15:43 To achieve this, we need to run different perf tools to collect data and *invent* a formula to calculate the score and 08:16:18 #info Julien 08:18:03 Any questions? 08:18:35 OK, let's move on to next topic 08:18:55 #topic CI job status 08:19:01 zhihui_wu could you update? 08:19:37 From ci log, qtip job is stable 08:19:48 how many test cases are included? 08:20:42 For now, qtip has three test suites- compute, network and storage. 08:21:03 both bm and vm? 08:21:42 yes, there are 15 test cases 08:22:05 OK 08:22:24 #topic RESTful API progress 08:22:53 It seems Zhifeng is not online 08:23:30 #topic Select test suite to run instead of al 08:23:36 ^ all 08:23:52 #link https://gerrit.opnfv.org/gerrit/#/c/22407/ 08:24:00 This is a request from mailing list 08:24:13 Taseer is working on it 08:24:29 the patch is already abandoned 08:25:07 Yes, too many errors. He says he will check it locally first. 08:25:19 I have send a license of PyCharm to him 08:25:24 I invite him to attend irc meeting. 08:25:54 Could you send a mail to follow up the progress? 08:25:56 zhihui_wu 08:26:05 tell him if he needs help, feel free to contact us 08:26:08 yujunz, ok 08:26:34 #action zhihui_wu contact Taseer to follow up on selecting test suites 08:26:38 where is the agenda list 08:26:53 #link https://etherpad.opnfv.org/p/qtip-meetings-2016-09-28 08:27:12 Select test case 08:27:42 OK, next 08:27:56 #topic CLI progress 08:28:02 SerenaFeng could you update? 08:28:16 not start yet 08:28:27 Do you need any help? 08:28:32 Or info 08:28:36 we agree to start it after the Restful api is ready 08:28:56 So, I am waiting for the Restful apis 08:29:00 I think Zhifeng said it is almost ready. 08:29:04 I'll confirm with her 08:29:15 #action yujunz to confirm RESTful api progress 08:29:18 yes, and the wiki documentt 08:29:31 Link? 08:29:42 Have you created it? 08:29:47 SerenaFeng, just like testapi? 08:29:55 No, it will be created by zhifeng 08:30:18 Guest47887 yes 08:30:34 a swagger link a documents written by hands 08:30:39 OK, I'll forward this request to her also 08:30:49 a swagger link or a document written by hands 08:30:56 She knew it 08:31:02 I'm not sure 08:31:09 we talked it in a morning meeting 08:31:12 OK 08:31:27 Next 08:31:37 #topic gerrit reviews 08:31:42 base on the restful document I will create a CLI proposal page 08:31:51 #link https://gerrit.opnfv.org/gerrit/#/c/20661/ 08:32:04 zhihui_wu are you going to break it into small ones? 08:32:33 yes, 20661 is a huge patchset, not easy to do a codereview 08:32:53 And many conflicts 08:33:13 I will abandond 20661 08:33:17 I see 08:33:17 is it used to implement one function or multiple function? 08:34:04 multiple 08:34:28 then break it 08:34:28 It effect baremetal and virtual test env 08:34:30 Maybe you can consider one patchset for each bullet in current commit message 08:34:57 There are six bullets, so six patchsets? 08:35:16 Yes, I agree 08:35:32 six patchsets 08:35:47 OK, next 08:35:51 #topic AOB 08:36:04 Anything else to talk? 08:36:25 I think we should take some time talk about the working mechanism 08:36:37 what is working mechanism 08:36:57 for example, like function do with epic, and sprint 08:37:24 OK, get it. 08:37:34 Any good practise from functest? 08:38:05 tasks are catalogued to epics 08:38:19 almose each task is linked to one epic 08:38:37 one task one patch 08:39:10 3 weeks per sprint 08:39:26 try to finish one task within one sprint 08:39:47 OK, we can try. 08:40:06 and we need to collect all the urgent work we are doing now 08:40:18 And prioritize them in JIRA? 08:40:43 yes 08:40:59 estimate the time comsuming, set a deadline 08:41:37 Will there be too much overhead doing all this? 08:42:50 I think only the infrastructure work need to be speeded up 08:43:30 Infra for qtip? 08:43:34 yes 08:43:39 You mean the RESTful api and cli and etc? 08:43:47 yes 08:44:10 Yes, that's one of the basic target for this release. To make it complete and easy to run 08:45:01 ok 08:45:28 Thanks 08:45:38 Next week will be holiday in China 08:46:14 So the meeting will be canceled. Next one will be 12 Oct 08:46:25 Thank you everyone. 08:46:41 #endmeeting