13:30:01 #startmeeting Brahmaputra release meeting 13:30:01 Meeting started Tue Apr 12 13:30:01 2016 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:30:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:30:01 The meeting name has been set to 'brahmaputra_release_meeting' 13:30:18 #topic roll call 13:30:24 #info Chris Price 13:31:04 #info Uli Kleber 13:31:07 #info Joe Kidder 13:31:33 hey folks 13:32:28 limited people online, maybe timirnich trozet anac1 and others will show up shortly 13:32:41 im here 13:32:57 im here 13:33:41 hi guys. want to run through quickly and capture state. (I'm in a meeting as I type so am a little unstructured) 13:33:51 meeting == 2 days of fun 13:34:19 #topic Brahmaputra.3.0 troubleshooting status 13:34:36 #info 3.0 Scenario troubleshooting freeze, deadline: April 20, 2016 13:35:13 trozet do you have a status update for ocl? (or is it only narindergupta who is working on that?) 13:35:28 scenario update from apex? 13:35:47 ChrisPriceAB: for OC it will be targeted for colorado, we added the bgpvpn scenario 13:35:51 for B3.0 13:36:02 ChrisPriceAB: we should have had our first functest run on it last night, need to check the results 13:36:17 cool 13:36:39 #info apex scenario update on bgpvpn scenario, deployment troubleshooting ongoing 13:36:45 trozet: can you point me to the daily job with that and running functest? 13:37:39 jose_lausuch: yeah just a sec 13:37:55 ok 13:37:57 ty 13:38:03 jose_lausuch: https://build.opnfv.org/ci/job/apex-daily-brahmaputra/89/console 13:38:26 thanks guys. 13:38:34 thanks trozet 13:38:48 #info Tim Irnich (SDN VPN) 13:38:50 np 13:38:53 trozet: do you have bgpvpn scenario active already? 13:38:53 Hi folks sorry for being late 13:39:08 I had an action from last week to hunt down scenario owners but have not had time to manage it. 13:39:32 hi timirnich, any update on bgovpn scenario's. trozet has alsready reported on apex 13:39:57 First successful deploy including all ODL patches finished few minutes ago 13:39:57 jose_lausuch: what do you mean? active in jenkins? 13:40:09 Niko is running tests now 13:40:15 looks good overall 13:40:19 trozet: yes 13:40:27 timirnich: I mean on apex, with trozet's integration :) 13:40:40 jose_lausuch: https://build.opnfv.org/ci/job/apex-deploy-baremetal-os-odl_l2-bgpvpn-ha-brahmaputra/ 13:40:54 daily should execute it next I think 13:40:58 #info sdnvpn completed deployment with all patches complete and undergoing troubleshooting. 13:41:00 ya, is that to be part of b3? 13:41:04 yeah 13:41:07 ok 13:41:14 timirnich, do we have a solution for the patching of ODL for the deployment? 13:41:23 it will be intesresting to see if nikolas fixes worked also for apex :) 13:41:37 timirnich, ChrisPriceAB: which patches are needed for sdnvpn with ODL? 13:41:54 ChrisPriceAB: yes we have some midstream patches as a workaround until ODL Be SR2 - agreed with Fuel 13:42:13 I'm using a build for SFC that im going to patch into stable/b which is an early SR2 build that contains an SFC fix, it probably has the SDNVPN fixes as well if they were pushed at least 2 days ago 13:42:28 seems like trozet and timirnich have a short discussion reauired. :D 13:43:10 trozet: we did not want to make an OPNFV release consuming a gery build from ODL, that is why we went for the midstream patching approach 13:43:16 *grey 13:43:16 #action timirnich and trozet to discuss bgpvpn ODL patching in Apex 13:43:45 any updates from the testing projects? 13:44:18 well, basically the same 13:44:32 bgpvpn tests are being fixed and tested currently 13:44:36 on fuel (for now) 13:44:47 did you patch the sequential fix in stable? was it labelled 2.0? 13:44:49 soon on apex as well 13:44:58 #info yardstick measurements for sfc scenario, need to check if all test cases are included 13:44:58 well, the fix came yesterday 13:45:04 I should label it now as 2.0 right? 13:45:06 :) ok for 3.0 then 13:45:15 sorry, 3.0 13:45:24 opps.. we dont have 2.0 label... 13:45:25 no we passed that, just follow 3.0 process https://wiki.opnfv.org/display/SWREL/3.0.release.plan 13:45:54 it's OK we did not label repo's in 2.0 that did not deliver into the release. 13:46:03 ok 13:46:18 I'll label with 3.0 as soon as we have the proof it works :) 13:46:23 ok, guys I have to run. Too many things on today. 13:46:32 jose_lausuch -> https://wiki.opnfv.org/display/SWREL/3.0.release.plan 13:46:42 says 3.0 release is April 28 13:46:50 #topic hot items for 3.0 13:46:51 so we dont need to tag until the 27th deadline 13:46:53 ok sorry 13:46:57 sure 13:47:02 any items we should focus on? 13:47:14 before next meeting? 13:47:30 Aside from stability of scenario's as we freeze mid next week for 3.0. 13:48:06 not from me 13:48:30 Ok, again sorry for being overbooked and underprepared. Life catches up with us all. 13:48:43 we shall call this an I will run off to prepare for the TSC 13:48:50 #endmeeting