08:30:03 <anac1> #startmeeting Yardstick work meeting
08:30:03 <collabot> Meeting started Mon Jan 25 08:30:03 2016 UTC.  The chair is anac1. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:30:03 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:30:03 <collabot> The meeting name has been set to 'yardstick_work_meeting'
08:30:11 <anac1> #info Ana Cunha
08:32:34 <QiLiang> #info QiLiang
08:32:53 <anac1> #topic release-B scenarios
08:33:51 <anac1> #info continue troubleshooting ODL scenario
08:34:18 <anac1> have we tested the workaround ?
08:35:04 <jnon> The workaround is removing security groups from template
08:35:46 <anac1> jnon - thanks, have you tested in a OPNFV lab ?
08:35:51 <jnon> It works if default security group setting are open on all pods
08:36:03 <jnon> no only eri pod1
08:36:22 <anac1> and it work on eri pod1, or?
08:36:39 <jnon> yes
08:37:08 <jnon> wait sorry not eri pod1, it was a virtual node
08:37:48 <anac1> ok, maybe try on bm ?
08:38:28 <anac1> #info workaround for ODL scenario to be tested on bm
08:38:59 <anac1> what's the implication of the workaround ? do we know the security group settings for the various labs ?
08:39:25 <jnon> no
08:39:37 <anac1> ok, i'll discuss on the release meeting
08:40:01 <anac1> QiLiang: i saw onos scenario worked last friday
08:40:10 <QiLiang> yes
08:40:22 <anac1> good work !
08:40:29 <anac1> what was the problem ?
08:40:47 <QiLiang> onos team fix bug in onos
08:41:05 <anac1> ok, no bug on yardstick ?
08:41:16 <QiLiang> yes
08:41:32 <QiLiang> one thing related to yardstick is ping6
08:41:47 <QiLiang> onos don't support ipv6
08:42:08 <QiLiang> ipv6 currently only tested on nosdn senario
08:42:14 <anac1> so  the test case have to be removed if the scenario is onos, right?
08:43:16 <QiLiang> yes, or ping6 scenario check NFVI scenario
08:43:34 <anac1> ok, for the problem on odl, have you tested the workaround ?
08:43:54 <QiLiang> not yet
08:44:03 <anac1> ok
08:44:49 <anac1> #info yardstick onons scenario works
08:45:03 <anac1> #info code freeze not yet declared
08:45:28 <anac1> last friday, not all installers were ready, so we continue
08:45:59 <anac1> there will be a discussion tomorrow on TSC about the release date
08:46:44 <anac1> #topic vTC
08:47:39 <akis> #info Akis Kourtis
08:47:49 <anac1> #info vTC daily runs in Ericsson POD1
08:48:35 <anac1> akis: will you enable vtc data to the new server ?
08:49:08 <akis> Yes after we solved the influx firewall issues
08:49:23 <anac1> thanks !
08:49:23 <akis> We will move on to enable it
08:50:06 <anac1> thnaks, great!
08:50:12 <anac1> thanks*
08:50:57 <anac1> #info firewall issues related to influxdB have been solved, LF updated configuration
08:51:12 <anac1> looking forward to seing the graphs !
08:51:32 <anac1> #topic license info
08:52:36 <anac1> #info to solve the pcap files license issue, legal agreed on adding an .rst file to the folder with license header, list all pcap files
08:53:03 <anac1> #topic other
08:53:19 <QiLiang> i've test inluxdb connection
08:53:26 <anac1> does it work for you?
08:53:48 <QiLiang> so we need set user/password to access influxdb
08:54:50 <QiLiang> work for me with opnfv/0pnfv2015
08:55:11 <wuzhihui> I have a question:is it possible not to build yardstick image every time in Jenkins CI daily job, but to download the yardstick image from the public image repo?
08:55:58 <anac1> QiLiang: have you pushed data to influxdb ?
08:56:33 <anac1> wuzhihui: is this related to the failed run today in your lab?
08:56:54 <jnon> wuzhihui: i think it is possible to change that if we need
08:56:57 <wuzhihui> This can shorten the execution time. We can create another Jenkins job to test the scripts of building yardstick image individually.
08:57:27 <QiLiang> i've pushed data before new configration throught ssh tunnel
08:58:05 <wuzhihui> Ana:yes
08:58:06 <QiLiang> will try it again later use the global ip
08:58:45 <wuzhihui> I can not figure out why zte pod met this problem
08:59:06 <anac1> QiLiang: ok, thanks - let me know if you find problems with the global ip
08:59:32 <QiLiang> ok
09:00:57 <anac1> wuzhihui: what fule version you have installed ? the scenario says old l2
09:01:01 <anac1> fuel*
09:01:15 <wuzhihui> 6.1
09:01:56 <wuzhihui> Our pod is still on Arno version
09:02:17 <anac1> ok, thanks
09:02:37 <jnon> if we don't build the image during CI, where should we upload the image?
09:02:44 <anac1> when do you plan to upgrade ?
09:04:16 <anac1> wuzhihui: you run succesfully several days before, right?
09:04:29 <wuzhihui> after release B
09:04:34 <wuzhihui> YES
09:05:12 <wuzhihui> Serveral times
09:05:37 <wuzhihui> The ratio of success is not high
09:08:23 <anac1> jnon: we need to find out where to upload the image and what is the impact of having two different ways of handling yardstick image
09:09:03 <anac1> wuzhihui: please add this topic here: https://etherpad.opnfv.org/p/yardstick_release_b_troubleshooting
09:09:16 <jnon> yes and we need another jenkins job to build and upload the image
09:10:16 <anac1> #action wuzhihui to add the yardstick image question on release-b troubleshooting etherpad
09:10:23 <anac1> anything else?
09:10:36 <anac1> can i cancel the meeting today at UTC 15?
09:11:36 <anac1> #info meeting today at UTC 15 is cancelled
09:12:05 <anac1> wuzhihui: we continue with your question on the etherpad
09:12:13 <anac1> thanks all for today
09:12:17 <anac1> #endmeeting