08:31:27 <rbbratta> #startmeeting yardstick work meeting 08:31:27 <collabot> Meeting started Mon Jul 31 08:31:27 2017 UTC. The chair is rbbratta. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:31:27 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 08:31:27 <collabot> The meeting name has been set to 'yardstick_work_meeting' 08:31:38 <rbbratta> #topic roll call 08:31:42 <rbbratta> #info Ross 08:31:45 <zhihui_wu> #zhihui_wu 08:31:54 <zhihui_wu> #info zhihui_wu 08:32:15 <JingLu> #info Jing_Lu 08:32:19 <kubi003> #info Kubi 08:32:22 <JackChan> #info Jack 08:32:26 <Kanglin> #info Kanglin 08:32:57 <rbbratta> #topic action item follow up 08:33:09 <deepaks> #info deepak 08:33:22 <rbbratta> #action rbbratta figure out how to tag Jira tasks for testcases 08:33:31 <rbbratta> still haven't look at Jira 08:33:49 <Mingjiang> #info Rex 08:34:26 <rbbratta> #info AP2 rbbratta create scale-up/scale-out testcase template for bottlenecks team 08:34:43 <rbbratta> #info scale-up/scale-out drafts submitted to bottlenecks 08:34:54 <kubi003> cool 08:34:58 <rbbratta> #action rbbratta create plan for more CI testing for Euphrates 08:35:45 <rbbratta> #topic Euphrates MS5 feature freeze 08:35:58 <abhijitsinha> #info Abhijit 08:36:01 <rbbratta> how are we with feature freeze? 08:36:30 <rbbratta> I am noticing some unittest failures 08:37:54 <JackChan> rbbratta: but for some reason, it is passed. Don't know why. 08:37:59 <rbbratta> There is a bug in somewhere in the Jenkins cover.sh script that is causing false positives when coverage fails 08:38:48 <rbbratta> when testr cover fails, it reports 'No data to report.' which is passed to awk and awk print 'to' instead of the number of lines missing 08:39:01 <JingLu> sometimes rebase can avoid this bug 08:39:19 <rbbratta> so we need to fix cover.sh, but also need to figure out why testr coverage is failing 08:39:24 <JackChan> JingLu: yes, recheck also work. 08:39:32 <rbbratta> I notice another error related to 'ping' module in migrate.py 08:39:43 <rbbratta> #link https://build.opnfv.org/ci/job/yardstick-verify-master/3303/console 08:39:57 <JackChan> rbbratta: yes, ping package is only for Python2 08:39:58 <rbbratta> File "/home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master/yardstick/benchmark/scenarios/lib/migrate.py", line 19, in <module> 08:39:58 <rbbratta> import ping 08:39:58 <rbbratta> ImportError: No module named 'ping' 08:40:46 <JackChan> rbbratta: I plan to find a package to replace it. 08:41:25 <rbbratta> but this raises another issue. we cannot use the 'ping' module, it is GPLv2 and we cannot link to it 08:41:37 <rbbratta> JackChan: okay 08:42:06 <JackChan> rbbratta: ok, got it. 08:42:12 <rbbratta> remember, we can only link to LGPL librares, not GPL 08:42:54 <JackChan> ok, I will find a package to replace it. 08:43:18 <rbbratta> #action JackChan replace ping 0.2 library due to GPL license issue 08:43:35 <rbbratta> for the NSB features, I need to fix unittests and add coverage. 08:45:05 <rbbratta> I would like to propose extending MS5 one week, to 2017-08-04 08:45:40 <Mingjiang> agree 08:45:43 <JackChan> agree 08:45:48 <JingLu> Agree. 08:46:25 <rbbratta> more specifically we would file an milestone exception request and submit to TSC. 08:47:06 <kubi003> It makes sense. I noticed that we still have several patch which are need to be merged in the gerrit. 08:47:28 <rbbratta> yes, we need more time for review as well 08:47:41 <rbbratta> and to fix cover.sh 08:47:56 <kubi003> TSC will review the request at this week TSC meeting. 08:48:10 <kubi003> so we need to fill it soon 08:48:28 <rbbratta> #agree submit MS5 exception request to postpone MS5 to 2017-08-04 08:48:43 <rbbratta> I will file it after this meeting 08:48:52 <kubi003> thanks 08:49:08 <rbbratta> #action rbbratta file MS5 exception request to postpone MS5 to 2017-08-04 08:50:09 <JingLu> rbbratta the patch "leave port_security_enabled undefined by default" has introduced a bug in our CI 08:50:52 <JingLu> I have created a JIRA ticket: YARDSTICK-765 08:51:07 <Mingjiang> JingLu: what problem would it lead to? 08:51:13 <rbbratta> JingLu: :( okay I'll look at it 08:51:41 <rbbratta> did it fix the Joid issue? Do the installers have different settings for port_security? 08:51:54 <JingLu> In compass and apex(virtual) deployment, if the "port_security_enabled" is undefined, VMs are not pingable. 08:52:45 <rbbratta> did we always define port_security_enabled? 08:53:03 <JingLu> I am not sure. it seems as long as port_security_enabled is defined (true or false), the vms are pingable 08:53:05 <rbbratta> I guess we want to default to the installer default 08:54:24 <rbbratta> I guess this is scenario issue, scenario should require port security so we can disable it? 08:55:28 <rbbratta> okay, we will debug. 08:55:45 <rbbratta> any other critical bugs? 08:56:22 <JingLu> No. Just this one as it will effect all testcases. 08:56:36 <rbbratta> I haven't emailed David McBride about the /etc/yardstick.conf issue. I will try to do that tomorrow. 08:56:58 <JackChan> rbbratta: ok, thanks 08:57:16 <rbbratta> #topic AoB 08:57:57 <rbbratta> #info https://jira.opnfv.org/browse/YARDSTICK-765 critical blocking issue with port_security_enabled 08:58:30 <kubi003> well, for /etc/yardstick.conf issue, I guess we neen't to retag the repo and docker image 08:58:48 <kubi003> neen't -> needn't 09:00:06 <kubi003> I assume that use will install the influxDB if he really want to use yardstick as a testing tool 09:00:17 <kubi003> use -> user 09:00:29 <kubi003> use -> user-> users 09:01:01 <rbbratta> I was going to ask David about adding a documentation fix 09:01:21 <Mingjiang> if the workaroud works well then it would be fine 09:01:48 <JackChan> kubi003: yes, that's true. He/She should use influxdb&&grafana to analysis 09:02:00 <kubi003> https://docs.opnfv.org/en/stable-danube/ 09:02:35 <rbbratta> #info https://jira.opnfv.org/browse/YARDSTICK-730 we assume user will install influxdb before doing any real testing 09:02:50 <Mingjiang> rbbratta: it make sense to fix the documentation if necessary 09:03:50 <rbbratta> okay, I will ask David about documentation update 09:04:25 <rbbratta> any other issues? 09:04:42 <kubi003> https://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/04-installation.html#install-yardstick-using-docker-recommended 09:05:11 <kubi003> I noticed that user guide asked user to do "docker pull opnfv/yardstick:stable" 09:05:54 <kubi003> so two thing we can do 09:06:01 <JackChan> yes, can we fix this bug in stable? 09:06:40 <kubi003> 1. update documentation for danube.3.1 for workaroud 09:06:41 <JackChan> To reduce the influence. 09:07:29 <kubi003> 2. we can fix this bug at stable if it is possible 09:08:27 <JackChan> kubi003: I think it is a good solution if we can fix this bug in stable. 09:09:15 <kubi003> but I'm not sure if it is possible to upload patch into stable branch at now 09:10:17 <rbbratta> we can ask David, I suspect a documentation fix is easier 09:11:37 <kubi003> yes, both are ok with me. 09:12:27 <rbbratta> okay, anything else? 09:12:33 <Kanglin> Last wednesday I attended HA meeting and discussed about HA test cases, they agreed three HA test cases I proposed, I'll commit them before MS6 09:12:45 <rbbratta> Kanglin: okay 09:12:56 <rbbratta> yes, MS6 is next up, 2017-08-11 09:12:56 <kubi003> I saw the email, that 's a good job 09:13:18 <Mingjiang> Kanglin: that's great! 09:14:03 <kubi003> a academic slide for HA testing :) 09:16:04 <rbbratta> okay, good job Kanglin 09:16:04 <Kanglin_> sorry my browser crashed just now, is there any information I missed? 09:16:48 <kubi003> https://thepasteb.in/p/r0hwJKQVjqGuK 09:17:08 <kubi003> Kanglin: all the info you missed 09:17:21 <Kanglin_> my hornor : ) 09:17:25 <Kanglin_> kubi003: thanks 09:18:12 <rbbratta> okay, I think we are done for today 09:18:24 <kubi003> yes 09:18:32 <rbbratta> #endmeeting