07:31:33 #startmeeting qtip 07:31:33 Meeting started Mon Mar 27 07:31:33 2017 UTC. The chair is yujunz. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:31:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:31:33 The meeting name has been set to 'qtip' 07:31:35 #undo 07:32:12 #link https://etherpad.opnfv.org/p/qtip-meetings-2017-03-27 07:32:38 #topic Action followup 07:32:56 #info AP1 SerenaFeng to help investigate the logging issue JIRA: QTIP-230 07:33:33 It seems an issue with socket creation in container, not resolved yet, but not a blocking issue 07:33:48 #info AP2 all review https://gerrit.opnfv.org/gerrit/#/c/30971/ and finish document for Danube 07:33:53 In good progress to me 07:34:04 #info AP Taseer to publish QTIP document to opnfv site 07:34:18 I think akhilbatra took the task in the end, did you? 07:34:21 I will take care of that 07:34:24 yes 07:35:09 It seems QTIP is published to the site correctly, right? 07:35:46 Only Danube release note issue, for which serena submitted the patch today 07:36:07 I saw also http://docs.opnfv.org/en/latest/submodules/qtip/docs/testing/developer/devguide/index.html 07:36:28 #link http://docs.opnfv.org/en/latest/submodules/qtip/docs/testing/user/userguide/index.html 07:36:43 #link http://docs.opnfv.org/en/latest/submodules/qtip/docs/testing/user/userguide/index.html 07:36:47 #undo 07:36:47 Removing item from minutes: 07:36:55 http://docs.opnfv.org/en/latest/submodules/qtip/docs/testing/user/configguide/index.html 07:37:30 Yeah but now publishing is automated. Just the right files need to be at right place 07:38:18 It seems stable-danube is empty. 07:38:21 #link http://docs.opnfv.org/en/stable-danube/testing/testing-dev.html 07:38:32 Might need many cherry-pick to sync the content 07:38:53 yes 07:39:35 OK, thanks for taking care of it and please help to track the changes in opnfvdocs 07:40:05 #info AP yujunz send Beijing Summit CFP draft for review 07:40:15 We will cover it in next topic 07:40:26 #topic CFP OPNFV Summit Beijing 07:40:50 The deadline has been extended to April 10th since everyone is busy with releasing recently 07:41:04 #link https://goo.gl/rEtl13 07:41:33 I have submit one of them. The rest are under review 07:42:48 Oops, it seems I skipped the weekly update topic. Let's do it first 07:42:52 #topic weekly update 07:43:10 I was busy creating document for Danube release 07:43:33 Zhihui and Julien resolved the socket connection issue in Docker 07:43:52 And now we don't have any blocking issue for release now except for stability of fuel deployment 07:44:02 That's it 07:44:10 Who's next? 07:44:21 I have the documentation completed 07:45:11 I have the documentation and unit tests in place now. 07:45:34 Great 07:45:56 Need to add qpi configuration in docker. 07:45:56 yujunz I will discuss it with you after meeting 07:46:10 OK akhilbatra 07:46:11 sorry *api 07:46:44 #topic Danube 1.0 release 07:46:51 Let's go to etherpad and update 07:46:57 #link https://etherpad.opnfv.org/p/qtip-danube 07:51:46 Taseer, do you consider runner with CLI is done? 07:52:02 I saw it still in progress in https://etherpad.opnfv.org/p/qtip-danube 07:52:32 And CLI documentation, any additional work planned for Danube 1.0? 07:53:21 I think it mostly covers all that has been done up to date 07:53:41 OK, I think we can consider it done 07:53:54 And amend if you find anything missing before the release 07:53:59 Sure 07:54:21 #info Danube 1.0 release is likely to be delayed. TSC will vote for it on 28th March 07:54:42 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-March/015680.html 07:56:19 QTIP is ready for release, so we can start planning for E release now 07:56:34 We don't plan to add more features in Danube 2.0 and 3.0. 07:56:38 Only bug fixes 07:57:02 #topic E release planning 07:57:09 #link https://etherpad.opnfv.org/p/qtip-euphrates 07:57:33 I added some topics, please feel free to propose your ideas 07:57:40 Not limited to the intern project, akhilbatra Taseer 07:59:52 I saw an issue in JIRA regarding WSGI support. 07:59:52 That is for? 08:00:01 Yes 08:00:19 py35 and wsgi are two community goal in OpenStack Pike PTG 08:00:29 So I think it worth following 08:01:53 ok 08:02:26 akhilbatra maybe you can have a look at ara for job monitoring? http://ara.readthedocs.io/en/latest/index.html 08:03:03 It seems a good way expose the progress of async jobs in api 08:03:22 Reading it 08:04:37 The E release plan will be open for several weeks. 08:04:57 I will align it with OPNFV milestones, not checked yet 08:05:35 We may have more details to discuss in next meeting, when every member is present 08:06:09 #topic active sprint followup 08:06:11 #link https://jira.opnfv.org/secure/RapidBoard.jspa?projectKey=QTIP&rapidView=135 08:06:26 Please update task status 08:08:24 #topic CI status 08:08:32 #link https://build.opnfv.org/ci/view/qtip/ 08:08:59 Fuel seems recovered. Hooray 08:09:33 #link https://wiki.opnfv.org/display/qtip/CI 08:09:59 Currently the qtip validation CI jobs depends on fuel deployment on zte-pod1 and zte-pod3 08:10:30 There are three scenarios validated for Danube everyday and two for master 08:11:16 #topic AoB 08:11:21 Any other topics? 08:11:47 How do we define the baseline for benchmarking ? 08:12:15 We need something qualified as a baseline 08:12:30 Stable, repeatable 08:12:45 For example, dpi gives pps and bps, are these not performance measurement rather then benchmark ? 08:12:46 Easy to get 08:13:02 These are measurement 08:13:13 We need the measurement on a reference pod as baseline 08:13:38 Ok 08:14:53 Zhihui has asked about selective running Taseer 08:15:16 Is it possible to provide an argument in CLI to select metrics in a plan to run instead of all? 08:15:50 No. Currently a single metric 08:16:06 single metric is fine 08:16:20 She says currently cli always run the whole plan 08:16:24 All metrics 08:16:39 qtip metric run -p 08:16:49 This would run a single metric 08:17:34 This is independent from the runner/runner.py, is it? 08:17:38 Yes 08:17:59 OK, I'll forward this message to her 08:18:03 Ok 08:18:11 That's all from me 08:18:23 Are we upto a separate qtip-readthedocs documentaion? 08:18:49 It is nice to have, but not an urgent request 08:19:11 I think QTIP code is quite independent from OPNFV 08:19:15 Can it be static for danube-relase? 08:19:16 not updating after every cherry pick. 08:19:51 I think we need to publish it automatically 08:20:02 I will update the final documentation at the day or two before the release. So the latest documentation is published seeparately 08:20:05 We can start with a manual push at the beginning 08:20:15 ok 08:21:14 We can update a static first. if the release schedule is too close to do automatically. 08:21:25 Later we will automate it? 08:22:38 That is not a mandatory part of OPNFV release 08:22:49 For OPNFV release, docs.opnfv.org is enough 08:23:45 I am just consider that we can make a better reachout for QTIP project 08:23:48 I confirmed. readthedocs will take care of the changes in repo. We are good to go :) 08:25:57 If nothing else, I shall close the meeting now 08:26:13 thats all from my side 08:26:13 We may discuss about qtip-api in docker in Google hanout 08:26:18 akhilbatra 08:26:24 ok 08:26:27 #endmeeting