08:30:39 #startmeeting yardstick work meeting 08:30:39 Meeting started Mon Jun 19 08:30:39 2017 UTC. The chair is rbbratta. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:30:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:30:39 The meeting name has been set to 'yardstick_work_meeting' 08:30:55 #topic roll call 08:31:03 #info kubi 08:31:07 #info Ross 08:31:14 #info Abhijit 08:31:22 #info Jack 08:31:25 #info JingLu 08:31:29 #info Rex 08:31:34 #info Kanglin 08:32:16 #topic action items follows up 08:32:56 #info zhihui 08:33:25 #info Ace____ 08:33:27 rbbratta: how about your trip 08:33:38 trip was good 08:34:04 still getting back into sync 08:34:49 let's see, we talked to OpenRetriever team as summit, right? so we can close that action point 08:35:17 rbbratta: yes, agree 08:35:47 rbbratta: yes, I have talked with Ruijing. 08:35:59 #info: AP2: we talked to OR team at summit, have plan for Kubernetes support 08:36:34 JackChan: have we made a Jira task for Kuberenetes support? 08:37:06 rbbratta: Current no, I will create it soon. 08:37:49 Now I have installed k8s. I plan to write a test case this days as the first step. 08:37:58 Initially we planned to support pre-deploy k8s containers using pod.yaml, then add k8s context at some point. 08:38:43 rbbratta: agree. 08:39:29 #info Initial plan to support pre-deployed k8s containers using pod.yaml node context, then add k8s context 08:40:14 #info deepak 08:40:52 next AP was to plan a backlog scrub at summit, we didn't do that, we should scrub backlog and Danube 3.0 tasks\ 08:42:51 oh, yes, we can do that at US time slot meeting with gotomeeting 08:42:56 okay 08:43:45 #action backlog scrub at US time slot meeting 08:44:23 AP4 was to talk to David about MS4 requirements. 08:44:36 That can happen at the release meeting tomorrow 08:45:19 Do you guys go to the APAC release meeting? 08:45:27 I need to find the timeslot for that 08:46:21 APAC release is bi-weeks meeting 08:46:26 #info follow up on MS4 requirements at release meeting 08:46:50 kubi001: can you forward me the APAC release meeting invite? 08:46:59 rbbratta: sure 08:47:19 AP5 was SNAPS-OO Heat gerrit review, that has already been merged 08:47:59 #info SNAPS-OO Heat support review https://gerrit.opnfv.org/gerrit/35753 has been merged 08:48:18 anything else for action points? 08:48:39 rbbratta: Done for invitation 08:48:40 about SNAPS-OO i take the action to rewrite Ping to use SNAPs first. 08:49:15 Mingjiang: okay, please make Jira task for it 08:49:24 okay 08:49:42 next topic, summit 08:50:18 #topic OPNFV Summit 2017 Beijing 08:50:57 Everyone had a good time? It was good to meet you all. :) 08:51:16 nice meeting you all, too 08:51:33 #link https://wiki.opnfv.org/pages/viewpage.action?pageId=5734608 08:51:40 Thank you all for your hospitality 08:51:55 any slides or demo video could be uploaded here. 08:51:57 :) 08:52:43 Has the GUI demo video been uploaded? 08:52:48 #link https://www.youtube.com/watch?v=M3qbJDp6QBk 08:53:10 rbbratta: yes, I have just uploaded it. 08:53:27 #info everyone please watch Yardstick GUI Demo https://www.youtube.com/watch?v=M3qbJDp6QBk 08:54:20 where there any other Yardstick presentations? 08:54:32 JackChan: you can also add the link into yardstick wiki so everyone knows about it. 08:55:12 Mingjiang: yes, I will do it right now. 08:55:26 rbbratta: i've uploaded mine in the wiki. 08:55:44 i will upload mine soon 08:55:47 kubi001: did you have slide for your other talk? 08:56:10 rbbratta: yes, will upload soos, slide with trevor 08:56:11 Mingjiang: Done! 08:56:31 also the one with China Mobile 08:56:52 sure 08:57:57 #action everyone please add slides and videos to wiki 08:58:31 There was a presentation by Morgan about measuring power utilization using IPMI during testing 08:58:50 Energy Audit aaS with OPNFV 08:58:53 that's a interesting topic 08:59:18 They have a python library already written and used in functest 08:59:37 I need to find the slides, but there is a developer at Orange that worked on that. 09:00:13 We should add it as a feature request and scope it out. I will create Jira ticket 09:01:24 okay 09:01:28 #action Ross: find slides for Energy Audit aaS and create Jira story for it 09:02:14 There was also discussion in a another session about using linking the Pod Descriptor File to the test results, so people can track hardware 09:02:33 this is related to the current task for gathering hardware info 09:02:52 the hardware is already defined in some cases in the PDF 09:03:19 rbbratta: can you create a jira task for it or updated existed jira? 09:04:23 #action Ross: create Jira story for link PDF to test results for recording HW info 09:04:41 Which Pod Descriptor File? 09:04:44 rbbratta: do you mean the pharos userguide.pdf that contains the hardware info of pods 09:04:57 PDF -> POD Descriptor File 09:05:06 ok 09:05:09 The PDF from the dynamic CI business 09:05:12 got it 09:05:42 I think Uli suggested it 09:05:48 Alexandru Nemes proposed yardstick: Configure Yardstick flavor to give more RAM to ARM instances https://gerrit.opnfv.org/gerrit/36179 09:06:13 Where they any other ideas/tasks from the summit? 09:06:49 did we have more ideas from the SNAPS tutorial? 09:07:39 did we talk about ansible something? 09:07:49 it could help to clean the code. 09:09:48 Alexandru Nemes proposed yardstick: Configure Yardstick flavor to give more RAM to ARM instances https://gerrit.opnfv.org/gerrit/36179 09:10:08 I can't remember any additional ansible ideas, if we have any we can add to exists jira 09:10:17 any other comments on the summit? 09:10:32 any interesting sessions? 09:11:29 next topic Dovetail docker tag 09:11:58 Leo from Dovetail asked to add tag of cvp in yardstick docker image. 09:12:01 #topic Dovetail requires Yardstick docker tag 09:12:37 what is cvp tag supposed to represent? 09:12:42 which version? 09:13:40 they want to tag yardstick docker image so dovetail can use it to specify which version of yardstick is related to dovetail 09:13:56 they would also add tag on dovetail docker image 09:13:59 sure, but do they only want release versions? 09:14:17 I assume they want Danube 3.0, etc. 09:14:36 So the concern would be Dovetail using a non-git-tagged yardstick version 09:14:55 this also seems like a release meeting decision 09:14:58 not release versions, but a specific commit that dovetail have verified. 09:15:23 no need on git 09:15:34 no need to tag on git 09:15:35 I'm not unopposed, but I suspect we don't want to start using un-released versions, since that defeats the purpose of having releases 09:16:57 dovetail do not sync with opnfv release, i think that's why they need to tag it. 09:17:22 other projects and the public in general should only officially consume tagged released yardstick versions 09:18:18 because released versions are the only ones we support 09:18:38 is there an email thread or something on tech-discuss? 09:19:33 i don't think so, I can ask him to create a thread about it. 09:19:40 please do 09:20:03 sure 09:20:18 we are flexible, but we don't want to create bad process 09:21:08 when will we have Danube 3.0 ? 09:21:11 #action Rex: follow up on Dovetail request to create docker tag for Yardstick version to use with Dovetail 09:21:22 okay, next topic Danube 3.0 09:21:43 #topic Danube 3.0 09:22:13 so I tagged Danube 3.0 already before summit, because I didn't see the defer email 09:22:52 I think we resolved and moved all the Danube 3.0 issues 09:23:08 Are there critical issues that we need to revisit? 09:24:49 kanglin: what about ha test case 09:25:48 Mingjiang: Discussed with Fu Qiao, but she seems to be busy these days, the detail HA test case design will be discussed later. 09:26:27 there's a problem about ha test case to run on https SUT 09:27:11 currently the cli command ha test case use do not support insecure way when connect to https SUT 09:28:31 Got it, can you make an issue on jira? 09:29:09 Kanglin: I will 09:31:04 Mingjiang: OK, I'll deal with it. 09:32:11 okay, so if we have fix in time, we can cherry-pick to stable and re-tag Danube 3.0. 09:32:33 Kanglin: https://jira.opnfv.org/browse/YARDSTICK-683 09:32:58 #info looking at https://jira.opnfv.org/browse/YARDSTICK-683 for Danube 3.0 09:33:07 #link https://jira.opnfv.org/browse/YARDSTICK-683 09:33:47 can we close the other 3.0 issues https://jira.opnfv.org/browse/YARDSTICK-683 09:34:28 kubi001, JingLu: can we close the Danube 3.0 issues? 09:35:41 err, what is the correct Jira process, do we close or resolve? 09:37:32 both will be OK 09:37:44 okay, so Jira is good for 3.0 09:37:50 developer would use resolve 09:38:04 the creater of task and PTl would use close 09:38:05 any other items for 3.0? 09:39:32 #topic AoB 09:40:40 https://gerrit.opnfv.org/gerrit/#/c/30509/ is ready for merging, everyone please review 09:40:47 #link https://gerrit.opnfv.org/gerrit/#/c/30509/ 09:40:57 #info https://gerrit.opnfv.org/gerrit/#/c/30509/ is ready for merging, please review 09:41:29 will do 09:41:45 The other NSB releated patches from Deepak are squashed and review 09:41:53 reviewed 09:43:06 ok 09:43:13 we have a whole bunch of reviews in the queue 09:43:48 maybe we can discuss at the US time-slot meeting 09:44:07 okay, anything else? 09:45:00 not from me 09:45:54 okay, thanks everyone 09:45:59 #endmeeting