00:31:20 <rbbratta> #startmeeting yardstick work meeting 00:31:20 <collabot> Meeting started Tue Aug 15 00:31:20 2017 UTC. The chair is rbbratta. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:31:20 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 00:31:20 <collabot> The meeting name has been set to 'yardstick_work_meeting' 00:31:30 <rbbratta> #topic roll call 00:31:33 <rbbratta> #info Ross 00:33:11 <rbbratta> goto meeting problems 00:33:51 <rbbratta> namely I can't connect to gotomeeting 00:35:00 <rbbratta> can anyone connect to the gotomeeting? 00:35:08 <JackChan> no 00:35:11 <kubi001> #info kubi 00:35:15 <rbbratta> yep, looks busted 00:35:29 <JackChan> #info Jack 00:35:55 <rbbratta> okay let's continue IRC only 00:36:00 <kubi001> ok 00:36:03 <rbbratta> #info gotomeeting not working, IRC-only meeting 00:36:05 <JackChan> Ok 00:36:37 <JingLu> #info JingLu 00:36:38 <rbbratta> #topic action item follow up 00:37:12 <rbbratta> #info https://jira.opnfv.org/browse/COMPASS-559 jira for provider networks for compass 00:37:37 <rbbratta> #info https://wiki.opnfv.org/display/yardstick/Scale-out+testing scale-out testing diagram 00:38:30 <rbbratta> #info created yardstick_testcase Jira label for testcases. We should tag all our testcases with yardstick_testcase so we filter Jira by feature or testcase 00:39:30 <rbbratta> okay, actions items completed. any questions about Jira yardstick_testcase label proposal. 00:39:50 <kubi001> yes, when will be the deadline for label 00:41:10 <rbbratta> supposed to be MS6 for test cases completed 00:42:09 <rbbratta> although I think we don't count YAML for that. So that would be new Scenario subclasses only 00:42:33 <rbbratta> we should plan to have all testcases completed by MS6. 00:43:45 <rbbratta> so we would expect to see all Jira issues for 5.0.0 labeled yardstick_testcase implemented by MS6. 00:44:10 <kubi001> sounds good 00:44:45 <kubi001> I forget the new time for MS6, two weeks delay than previous planning? 00:45:16 <rbbratta> 2017-08-25 + 1 week grace period 00:45:28 <rbbratta> soon 00:45:51 <kubi001> Ok, got it 00:46:07 <JackChan> So we have only two weeks. 00:46:36 <kubi001> so it seems that we need to review the process for label at next meeting. 00:46:41 <JackChan> Do we have the test case plan before MS6? 00:46:47 <rbbratta> for new tests, new Scenario subclasses 00:47:37 <rbbratta> we should be labeling testcases in Jira so we can review them 00:47:38 <kubi001> rbbratta: you said the MS6 will not include yaml freezen, yes? 00:48:18 <rbbratta> MS6 should not include YAML freeze. 00:48:46 <kubi001> ok, good 00:49:31 <rbbratta> as far as I'm concerned YAML can be merged anytime, it should be near-zero risk 00:50:17 <rbbratta> we are mostly concerned about Python code and regression 00:50:59 <rbbratta> okay, so we can start to review testcase and next meeting 00:51:20 <rbbratta> #info review new testcases next yardstick meeting 00:51:22 <JackChan> OK 00:51:34 <kubi001> +1 00:51:46 <rbbratta> next topic 00:51:54 <rbbratta> #topic Danube 3.2 00:52:10 <rbbratta> JingLu was going to update the release notes for Danube 3.2 00:52:22 <rbbratta> then we can merge release notes, git tag and create new docker 00:52:40 <rbbratta> JackChan: you tested the stable/danube fix? 00:52:50 <JingLu> yes will upload patch after meeting 00:52:59 <rbbratta> okay 00:53:09 <JackChan> yes 00:53:31 <rbbratta> anything else for Danube 3.2? 00:53:58 <rbbratta> #topic Euphrates MS5 feature freeze 00:54:12 <rbbratta> #info PROX patch was merged, all NSB features merged 00:55:05 <rbbratta> #link https://gerrit.opnfv.org/gerrit/#/c/39217/ 00:55:09 <rbbratta> ready to merge? 00:55:26 <JackChan> yes 00:55:50 <rbbratta> #link https://gerrit.opnfv.org/gerrit/#/c/35379/ 00:55:53 <rbbratta> ready to merge? 00:55:54 <JackChan> I think it is ready to be merged. 00:56:29 <rbbratta> which one? 00:56:35 <rbbratta> 35379? 00:56:46 <JackChan> 39217 00:56:55 <OPNFV-Gerrit-Bot> Merged yardstick: Add yardstick report for each task https://gerrit.opnfv.org/gerrit/39217 00:57:14 <JackChan> It seems 35379 merge conflict. 00:57:14 <rbbratta> what about 35379? Ace had comment 00:57:20 <rbbratta> oh, crap 00:57:53 <Ace__> This patch is merge conflict. 00:58:32 <rbbratta> in .gitignore 00:58:50 <Ace__> ZhangJ has told me maybe it's my environment error, I will try to test it again after config openstack environment. 00:58:55 <OPNFV-Gerrit-Bot> Ross Brattain proposed yardstick: Integrate vsperf in Tgen mode https://gerrit.opnfv.org/gerrit/35379 00:59:22 <OPNFV-Gerrit-Bot> Ross Brattain proposed yardstick: Integrate vsperf in Tgen mode https://gerrit.opnfv.org/gerrit/35379 00:59:44 <rbbratta> okay I remove .gitignore conflict, it rebased. once it passes Jenkins we can merge 01:00:03 <Ace__> Yes. 01:00:06 <rbbratta> then fix .ignore in new patch 01:00:39 <rbbratta> anything else for MS5? 01:01:48 <OPNFV-Gerrit-Bot> Jing Lu proposed yardstick: Update release note for Danube.3.2 https://gerrit.opnfv.org/gerrit/39293 01:02:29 <OPNFV-Gerrit-Bot> Jing Lu proposed yardstick: Update release note for Danube.3.2 https://gerrit.opnfv.org/gerrit/39295 01:03:47 <rbbratta> #topic AoB 01:04:32 <rbbratta> will probably talk about scale-out testing in next bottlenecks meeting. 01:05:02 <rbbratta> specifically the diagram https://wiki.opnfv.org/display/yardstick/Scale-out+testing 01:05:20 <rbbratta> okay, looks like we are done. 01:06:59 <OPNFV-Gerrit-Bot> Merged yardstick: Integrate vsperf in Tgen mode https://gerrit.opnfv.org/gerrit/35379 01:07:09 <rbbratta> okay merged. MS5 complete! 01:07:19 <rbbratta> #info MS5 complete 01:07:24 <rbbratta> thanks everyone 01:07:29 <rbbratta> #endmeeting