08:31:21 #startmeeting yardstick work meeting 08:31:21 Meeting started Mon Sep 25 08:31:21 2017 UTC. The chair is rbbratta. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:31:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:31:21 The meeting name has been set to 'yardstick_work_meeting' 08:31:29 #topic roll call 08:31:44 #info JingLu 08:31:49 #info Ross 08:32:01 #info Jack 08:32:03 #info Kubi 08:32:40 #topic Euphrates CI 08:33:05 #info Kanglin 08:33:16 #info Rex 08:33:20 JingLu: we need to update Jenkins dashboard for Euphrates 08:33:23 The CI yardstick page has been updated 08:33:35 # link https://build.opnfv.org/ci/view/yardstick/ 08:34:35 I don't see Project Jobs - Branch: stable/euphrates 08:34:52 also I think we need to add docker build jobs for euphrates 08:35:41 rbbratta ok I will update the Project Jobs section as well 08:35:44 rbbratta: do we need add it manually? in releng? 08:36:42 JingLu: I think so, Mark was saying something about it at last release meeting. I'll have to check the meeting minutes 08:36:57 JingLu: I don't think releng will add the jobs for us. 08:37:27 although something must be working because the Euphrates CI jobs are running? 08:37:32 One minute. II will try to add it now. 08:38:56 looks like CI is pulling opnfv/yardstick:stable 08:40:09 also I don't see results for yardstick-compass-baremetal-daily-euphrates 08:41:16 apex euphrates seem to be hitting the influxdb parse error: unable to parse invalid field format 08:41:27 did we have a fix for the influxdb parse issue? 08:41:48 Just added merge and verify jobs for euphrates. I didn't find docker build job for E. Only a job for D. 08:41:56 rbbratta: no, We don not come to a conclusion about it 08:42:57 was there a Jira for it? I thought we had a patch. 08:43:21 rbbratta: we have this error due to sometimes we can't ping the target. 08:43:31 not wure 08:43:32 sure 08:44:04 https://jira.opnfv.org/browse/YARDSTICK-809 08:44:22 I have created this jira, but not fixed. 08:44:40 but the real issue is the ping fails? 08:44:47 rbbratta: yes 08:45:25 for example, maybe we ping 100 times, but 10 failed. So we will get 10 times this error. 08:45:40 so we can communicate to Apex team that ping is failing intermittently. 08:46:07 but we also need to figure out null value, or -1 or something for ping result 08:46:59 or if the ping data is null, we do not upload the data. 08:47:18 we need to come to a conclusion about that. 08:47:21 Is there anything we need to do to get the testresults page for Euphrates working? 08:47:47 Maybe, I will check it later. 08:48:15 JackChan: if ping fails I think we do need to record that it failed 08:48:39 OK, so we set it -1 by default? 08:49:32 -1 seems to make senses 08:51:11 or if it is a float then positive infinity might also work 08:51:53 or the timeout is better? 08:52:37 if you want this result to present in grafana, i think i can be set to huge enough 08:52:42 Set to a larger time seems better 08:52:50 since -1 in grafana maybe a little strange. 08:53:48 I agree it should be large 08:54:22 maybe max_rtt? 08:55:25 sla value? 08:56:20 sla max_rtt or larger 08:56:26 agree 08:57:28 but max_rtt is small, so we may choose a much larger one 08:57:59 okay, we have a few minutes left. We still have a lot of Jira issues in open state 08:58:29 please move features that you aren't going to do to 6.0.0 and mark resolved issues resolved, so we have a clear picture 08:59:09 we have a about a week left to finish things up. 08:59:29 I did another sync from master to stable/euphrates for all the NSB fixes. 09:00:24 we have one Critical bug https://jira.opnfv.org/browse/YARDSTICK-786 09:00:30 #link https://jira.opnfv.org/browse/YARDSTICK-786 09:00:41 but it has no details 09:01:56 #topic AoB 09:02:24 Notice:All Chinese contributors will be in vacation for National Day from Oct. 1st to Oct.8th 09:04:35 kubi001: I suspect the release might be delayed for that reason then. 09:05:32 rbbratta: yes, one week later would be better 09:06:43 kubi001: okay David asked for feedback, I will send email. 09:07:05 ok 09:08:44 okay, I think that's it for today. 09:09:34 #endmeeting