14:30:30 <debrascott> #startmeeting Brahmaputra Daily Standup
14:30:30 <collabot> Meeting started Fri Feb 19 14:30:30 2016 UTC.  The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:30:30 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:30:30 <collabot> The meeting name has been set to 'brahmaputra_daily_standup'
14:30:54 <radez> #info Dan Radez
14:31:00 <anac1> #info Ana Cunha
14:31:02 <jose_lausuch> #info Jose Lausuch
14:31:10 <debrascott> #link agenda https://wiki.opnfv.org/releases/brahmaputra/minutes
14:31:27 <debrascott> #topic roll call
14:32:53 <debrascott> #topic
14:32:56 <ashyoung_> #info Ashlee Young
14:33:02 <debrascott> #topic test status
14:33:04 <ashyoung_> I have a help request
14:33:24 <debrascott> Hi ashyoung: what do you need?
14:33:27 <ashyoung_> If you can factor in a little time
14:33:50 <ashyoung_> We have a patch for the vPing ONOS scenario
14:33:59 <debrascott> ashyoung: please go ahead now
14:34:02 <ashyoung_> I think we were 50/50 on passes
14:34:49 <ashyoung_> And we can retest on virtual PODs, but have been told it won't count against the 4 passes unless we can schedule on official PODs
14:34:53 <jose_lausuch> ashyoung_ I was about to document in functest that vPing cannot work in onos because we are trying to access the instance from the same floating ip subnet
14:35:10 <ashyoung_> Fatih doesn't want to commit the patch w/o a go ahead from todays meeting
14:35:16 <ashyoung_> This is for Fuel/ONOS
14:35:30 <jose_lausuch> ok
14:35:39 <ashyoung_> jose_lausuch: yeah, we have a fix for that
14:35:53 <jose_lausuch> which vPing do you mean? the one using floating IPs or the one using nova metadata service?
14:36:08 <ashyoung_> I believe it's floating IPs
14:36:17 <jose_lausuch> ok
14:36:24 <jose_lausuch> so, the issue we also have seen in apex and joid
14:36:38 <jose_lausuch> the limitation of "pinging to the same public subnet"
14:36:40 <ashyoung_> right
14:36:41 <jose_lausuch> radez: right?
14:36:44 <Guest48551_> I will reenable onos on bm (jonas)
14:37:04 <ashyoung_> k
14:37:04 <radez> sry... let me read back
14:37:10 <jose_lausuch> it would be nice to have that workaround in place
14:37:12 <radez> oh yes
14:37:25 <jose_lausuch> because otherwise we have to skip our 2 vping test cases for onos scenarios, and its not fair
14:37:40 <ashyoung_> I appreciate that
14:37:49 <ashyoung_> It's rather late in the cycle
14:37:57 <jose_lausuch> and skiping things because they dont work on a certain installer is not fair for the other installers
14:38:08 <jose_lausuch> s/installer/sdncontroller
14:38:57 <ashyoung_> I don't think this changes Sunday. It's a resource scheduling thing
14:39:10 <ashyoung_> And whether Fatih can push the patch in so we can run the tests
14:39:27 <ashyoung_> We've tested on unofficial resources
14:39:32 <jose_lausuch> ok
14:39:46 <jose_lausuch> can you post the patch here?
14:40:27 <ashyoung_> I need to get it. I can post it to email once I get it
14:40:38 <ashyoung_> Sorry. This was going on at 3am my time
14:40:57 <debrascott> alright can someone pound in a 1-line summary for the minutes record?
14:42:49 <debrascott> jose_lausuch: how is functest today?
14:42:54 <ashyoung_> I will
14:43:11 <jose_lausuch> #info updated https://wiki.opnfv.org/functextnexttaks
14:43:14 <jose_lausuch> but in short:
14:44:02 <jose_lausuch> #info if we manage to get rid of those tempest errors on fuel due to insufficient ips : https://gerrit.opnfv.org/gerrit/#/c/10159/ we will be green for fuel
14:44:02 <ashyoung_> #info Wuwenbin has a patch to resolve Fuel/onos vPing test scenario and will post the patch for re-test on approved PODs. Jose Lausuch is awaiting the patch.
14:44:32 <jose_lausuch> #info decided to consider orange-pod2 for the release to get the results from
14:44:44 <jose_lausuch> #info got more results on that pod and it looks good
14:44:54 <jose_lausuch> #info for compass no changes, everything looks fine
14:45:44 <jose_lausuch> #info apex, we found some causes for some tempest tests, but still a bit under 90%, same issues with vPing with ONOS... maybe we dont consider that test case for the green light? if that's fair...
14:46:08 <radez> jose_lausuch: YS will not pas due to the same issue btw on ONOS
14:46:20 <jose_lausuch> ya
14:46:21 <jose_lausuch> right
14:46:31 <jose_lausuch> then? we dont deliver that scenario next week?
14:46:55 <ChrisPriceAB> Is it a limitation or a big?
14:47:08 <ChrisPriceAB> Big...  (Can be big)
14:47:21 <ChrisPriceAB> Bug is better
14:47:32 <jose_lausuch> what do you mean
14:47:52 <ashyoung_> lol
14:48:08 <ChrisPriceAB> Is it a function ONOS intended to deliver or is it something they will do in the future?
14:48:26 <jose_lausuch> well, ashyoung_ just said they have a workaround for fuel..
14:48:29 <ashyoung_> intened
14:48:45 <ashyoung_> I can't type either
14:48:50 <ashyoung_> intended*
14:49:24 <radez> ashyoung_: is that something you have to deliver as a workaround or is it something we setup environmentally?
14:49:29 <ashyoung_> ChrisPriceAB: It was "deemed" good enough and we wanted to re-test with the fix
14:49:59 <ashyoung_> radez: I am not positive, but it might be environment
14:50:13 <ashyoung_> It's almost 11pm for the developer
14:50:27 <ChrisPriceAB> Ok.  Needs a deeper discussion.
14:50:32 <ashyoung_> And they typically lose access to their gear once they leave the office
14:50:44 <ashyoung_> ChrisPriceAB: When
14:50:55 <ashyoung_> It's Friday and we freeze Sunday
14:51:06 <ashyoung_> We are asking for a re-test
14:51:30 <ChrisPriceAB> Early Monday (for you ash) would be the first and best time I guess.
14:51:34 <radez> so does that mean we probably won't get the work around this weekend?
14:51:41 <ChrisPriceAB> Yes, we retest.  We freeze state on Sunday.
14:51:48 <ashyoung_> Ok
14:51:55 <ashyoung_> Understood
14:52:05 <ChrisPriceAB> If we need to make judgement calls we do that once we have a set state.
14:52:07 <ashyoung_> Thanks!
14:52:13 <Guest48551_> Ash is the fix in is it only for me to reenable onos(jonas)
14:52:15 <ashyoung_> Agreed
14:52:19 <ChrisPriceAB> :)
14:52:33 <ashyoung_> Guest48551_: Awesome!!!
14:52:43 <ashyoung_> Guest48551_: You look different
14:52:47 <ashyoung_> ;)
14:53:03 * ChrisPriceAB thinks he might have been useful, but is not sure yet...
14:53:06 <Guest48551_> Mobile;-)
14:53:25 <ChrisPriceAB> It's a good look!  ;)
14:53:35 <ChrisPriceAB> Very mysterious
14:53:40 <ashyoung_> #info fuel/onos vping patch is in and only waiting on Jonas to re-enable the onos scenario
14:53:53 <debrascott> OK we missed ys update yesterday. Let’s get to anac1
14:53:57 <anac1> #info looks like yardstick apex odl l2 scenario has 3 successful runs, waiting for next run
14:53:57 <ashyoung_> Sounds like we're good for that re-enable Jonas
14:54:21 <Guest48551_> Cool
14:54:27 <anac1> we noticed data coming in the dashboard: http://130.211.154.108/grafana/dashboard/db/yardstick-main
14:55:11 <anac1> notice dashboard is not ready, work in progress (use opnfv/opnfv if you want to see the data)
14:55:23 <debrascott> anac1: what is grafana? we have to sign up to see
14:55:38 <anac1> sign up or use opnfv/opnfv
14:55:57 <debrascott> anac1: thans for uname/pw
14:57:21 <debrascott> anac1: nice
14:57:25 <anac1> that's all from e
14:57:27 <anac1> me
14:58:27 <debrascott> jose_lausuch and anac1 can you summarize scenarios that pass 4x in both ft and ys?
14:58:55 <anac1> compass (nosdn, onos, odl l2), fuel (nosdn, onons, odl l2)
14:59:11 <anac1> hopefully more on the weekend
14:59:14 <jose_lausuch> compass (nosdn, onos, odl l2)
14:59:38 <debrascott> OK good want to make sure I had it right
15:00:17 <debrascott> jose_lausuch: kvm was near working the other day, what is status there?
15:00:57 <jose_lausuch> I need to check ...
15:01:05 <jose_lausuch> which installer do you mean?
15:01:16 <anac1> debrascott: not ready
15:01:21 <jose_lausuch> fuel?
15:01:23 <debrascott> looking back in notes…
15:01:40 <jose_lausuch> I dont see any functest run with that scenario on fuel https://build.opnfv.org/ci/view/functest/job/functest-fuel-ericsson-pod2-daily-brahmaputra/
15:02:07 <debrascott> jose_lausuch: yes it was fuel
15:02:42 <jose_lausuch> need to douclbe check...
15:02:43 <debrascott> Guest48551: update was from you
15:02:49 <debrascott> Fuel (Jonas Bjurel) Tickets and backlog jira dashboard .Since yesterday we have 2 consecutive good runs with NFVOVS .We have 4 successful deployments with KVM4NFV but tests are failing. .KVM4NFV have been informed, don't know if they are working on it? .BGPVPN scenario will start in a couple of hours. .We might have a solution for the ODL-L3 scenario, testing it, will give results tomorrow.
15:03:28 <jose_lausuch> 4 successful deployments doesnt mean 4 successful functest's+yardstick's :)
15:03:53 <debrascott> jose_lausuch: yeah, see that now
15:04:15 <jose_lausuch> but we do have runs for OVS scenario, I need to update the table
15:04:21 <jose_lausuch> just realized
15:04:46 <debrascott> jose_lausuch: good!
15:04:48 <jose_lausuch> ah well, its updated sorry
15:04:55 <jose_lausuch> we are good, we dont have runs with kvm
15:05:09 <debrascott> ok top of the hour
15:05:12 <debrascott> thanks for joining
15:05:22 <ashyoung_> Thanks everyone!!!
15:05:33 <debrascott> if we didn’t get you your project please send an update to me via email or irc
15:05:41 <debrascott> #endmeeting