07:32:36 #startmeeting qtip 07:32:36 Meeting started Mon May 8 07:32:36 2017 UTC. The chair is yujunz. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:32:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:32:36 The meeting name has been set to 'qtip' 07:32:42 #info zhihui 07:32:54 #topic roll call 07:32:58 #info Yujun Zhang 07:33:02 #info Taseer 07:33:04 #info zhihui 07:33:34 #info SerenaFeng 07:33:46 #link https://etherpad.opnfv.org/p/qtip-meetings-2017-05-08 07:33:54 #topic weekly updates 07:34:00 I'll go first 07:34:49 I was busy with openstack/vitrage last week, still not done yet... Will start working on doctor performance profiler after that 07:35:06 There is a joint presentation with doctor project in the summit 07:35:11 That's it 07:35:29 I am working on integrating the ansible-runner with CLI. 07:36:20 Now we should be able to run `qtip workspace create` anywhere to create a new workspace 07:36:40 Not limited to qtip/tests/integration 07:36:54 that's great 07:37:31 Anyone else will update? 07:37:58 Qtip report is finished but not merged yet 07:38:25 no update about QTIP from my side. 07:38:37 Next topic will be yours zhihui 07:38:47 #topic OPNFV plugfest retrospective 07:38:55 This week, I will verify QTIP workflow in container. 07:39:48 We did QTIP interoperation tests in plugfest. 07:39:53 OK, to give some explanation on background, we met some issues with ssh-proxy on plugfest 07:40:16 I also get ssh issues on my pod. 07:40:34 What exactly? Taseer 07:40:52 I always get ssh connection closed by remote host while executing run.yml 07:41:16 Try to ssh -F ./ssh.cfg node-name -vvv to debug 07:41:23 Ok 07:41:31 Back to plugfest 07:41:33 #link https://etherpad.opnfv.org/p/qtip-plugfest 07:41:39 You may go on zhihui 07:41:47 We covered 4 installers and 5 hardware resources. 07:42:07 That was great! 07:42:28 We all know how many installers have be released in OPNFV? That is 4! 07:43:14 so we collected many different test results and we can analysis them and maybe can find some conclusion. 07:43:34 #info We covered 4 installers and 5 hardware resources. 07:43:44 zhihui you can use #info 07:44:00 ok, thanks SerenaFeng 07:44:02 to indicate it is important not trivial conversation 07:45:28 Anything else? 07:45:35 #info based on these test results, we will do some data analysis. 07:45:57 OK 07:46:16 #info need to solve the issues that we met in plugfest. 07:47:05 #link: https://etherpad.opnfv.org/p/qtip-plugfest 07:47:28 All issues are listed on etherpad. 07:47:59 # info QTIP gave a presentation in plugfest. 07:48:42 #link https://drive.google.com/drive/u/0/folders/0B541CgjKBG6lT2M0RnNrTEZkYm8 07:48:56 #info slides and recorded video here in https://drive.google.com/drive/u/0/folders/0B541CgjKBG6lT2M0RnNrTEZkYm8 07:49:48 people are interested on the compute QPI baseline. 07:50:50 I explained that the baseline is not a serious one. a good baseline need to be accepted by users and community. 07:51:41 To find a good baseline is important to QTIP. 07:52:27 #info need verify workflow in QTIP container 07:53:44 The user ask whether QTIP support docker. They would like to run QTIP on their own labs by using docker. 07:55:00 I agree, as more services are added to qtip, docker is becoming more important. It is also a lightweight validation environment for qtip installation 07:55:50 Recently, i will verify QTIP workflow in container. If it is ok, i would like to send an email to inform them and tell them how to use QTIP container. 07:56:22 Please update the user doc and send them link instead 07:56:32 by the way, i run QTIP test on my own laptop in plugfest. 07:56:44 yujunz: ok 07:57:00 That's all, from my side. 07:57:05 Thanks 07:57:43 SerenaFeng: do you have something to share with us? maybe i miss something. 07:58:45 If nothing else, we shall move on to Beijing summit plan 07:58:53 #topic OPNFV summit plan 07:58:59 #link https://etherpad.opnfv.org/p/qtip-opnfv-summit-beijing 07:59:16 #info some companies were willing to leverage qtip to their other pods 07:59:35 Good to know, SerenaFeng 07:59:54 #info and they say it is a good demo, thanks to zhihui 07:59:58 It was really a success to not only tested the inter-operation but also promoted QTIP in the community 08:00:07 yes 08:00:28 OK, let's talk about next big event, OPNFV summit 08:00:34 #info they also think the role of QTIP benchmark-as-a-service is a good idea 08:00:38 okey 08:00:57 For now, I have just one session confirmed for OPNFV Summit, the one with doctor project 08:01:02 About performance profiler 08:01:32 In which we shall show how to use QTIP library or agent in feature project for performance profiling 08:01:56 I haven't got any news on the sessions of design summit yet 08:02:03 #link https://etherpad.opnfv.org/p/qtip-opnfv-summit-beijing 08:02:27 The updated plan is on the **top** part of this page 08:02:53 We shall recorded some video for QTIP demo to play repeated in market place 08:03:54 Let me explain a bit on web interface PoC on behalf of Akhil 08:04:32 We reviewed some potential solutions and will propose to use ansible-semaphore to build web interface of qtip 08:05:13 We may demonstrate it in next project meeting 08:06:31 I listed some topics in design sessions no matter which sessions are pick by the conference 08:06:50 I think there will be room allocated for each project for team discussion 08:07:07 good luck for our topics. :) 08:07:26 How is going with your VISA, Taseer? 08:08:40 No progress. Hotel reservation and return neccessary along with Visa Application. 08:09:06 Return ticket I mean. Can only proceed when I get from Linux Foundation. 08:10:20 I see. Thanks for update 08:10:28 #topic E release plan 08:10:34 #link https://etherpad.opnfv.org/p/qtip-euphrates 08:11:09 I have submit the plan to release manager 08:11:23 And highlighted the high priority tasks 08:13:59 #topic AoB 08:14:43 BTW, we will not use JIRA as heavily as we did in D release 08:15:04 We shall focus more on weekly update from team, it seems more efficient... 08:15:50 That's all from me 08:16:03 Is it good to not use JIRA. 08:17:14 We still use it 08:17:26 maybe we can discuss it offline. 08:17:34 Just not follow sprints so strictly as we did in last release 08:17:46 Bug reporting still goes to JIRA 08:18:08 If you want to plan a new feature in JIRA, feel free to use it 08:19:38 ok 08:20:52 Thanks all. That's it for today 08:20:54 #endmeeting