14:31:01 #startmeeting Brahmaputra Daily Standup 14:31:01 Meeting started Thu Jan 7 14:31:01 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:31:01 The meeting name has been set to 'brahmaputra_daily_standup' 14:31:13 #topic rollcall 14:31:35 #info Debra 14:31:36 #info Ana Cunha 14:32:39 topic is roll call 14:33:04 sorry I'm late...didn't see the irc in the pile of links. 14:33:18 #info Tim Rozet 14:33:25 #info Fatih Degirmenci 14:33:40 joekidder: no problem, a number of people are still active on the weekly tech call 14:33:43 #info Trevor Cooepr 14:33:45 #info Joe Kidder 14:34:12 #info Morgan Richomme 14:34:51 #undo 14:34:59 #topic Milestone E status 14:35:04 #info Trevor Cooper 14:35:35 #info Projects reporting: 29 14:36:02 #info: Projects who have not yet reported: 9 14:36:03 DPACC 14:36:05 Moon 14:36:07 Movie 14:36:08 NFV for KVM 14:36:09 Policy Test 14:36:11 Resource Scheduler 14:36:12 SDNVPN 14:36:13 Service Function Chaining 14:36:14 #info Bin Hu 14:36:14 VNFFG 14:36:25 <[1]JonasB> #info Jonas Bjurel 14:36:36 #info Not reported projects: DPACC, Moon, Movie, NFV for KVM, Policy Test, Resource Scheduler, SDNVPN, SFC 14:36:49 #info Key Issues: 14:36:50 1. Lab infrastructure not fully up: 14:36:52 Moon has never been Release B candidate... 14:37:00 thanks fdegir 14:37:04 debrascott: you typed in 8 projects 14:37:06 1 missing 14:37:38 fdegir: VNFFG 14:37:49 #info And VNFFG not reported 14:37:55 sorry 14:37:57 missed it 14:38:24 #info Key Issues: 14:38:40 #info 1. Lab infrastructure not fully up: 14:38:59 #info As of now, we have 4 fully operational PODs 14:39:02 #info 2. None of the 4 installers has fully completed integration checks with all components. In some cases this is due to troubleshooting issues, in others it is due to component availability (OpenContrail & ONOS) with the right lab infrastructure 14:39:13 #info 2 under verification 14:39:25 #info 1 network troubleshooting 14:39:27 #info 3. Minimal Scenario definitions are pending which impacts CI & some test projects. 14:39:45 #link https://wiki.opnfv.org/brahmaputra_testing_page 14:39:49 #info 1 pending VPN access 14:39:52 #info 4. A number of projects have not yet prioritized their open issues and so are not able to determine which issues to defer. 14:39:58 #info page updated to track the scenario 14:40:04 #link https://wiki.opnfv.org/pharos_rls_b_labs#status_of_production_ci_resources_for_release_b 14:40:13 can we report each item one by one 14:40:18 #info 6. A couple feature projects do not have working deployment yet and may be at risk of missing this release 14:40:23 oops missed #5 14:40:39 #info 5. Nearly all projects are still working on documentation 14:41:13 #info 7. A number of feature projects have not yet had opportunity to test in a Pharos lab, creating risk for test projects 14:42:43 that’s it 14:43:43 one question I have is what is the drop dead date for fixing ANY bugs in order to reach Feb 2? 14:45:26 ie: when is last build with time for minor regression testing? 14:46:01 #topic Hot issues 14:46:10 any additional issues to above? 14:46:35 5 is not really an issue... 14:47:13 morgan_orange: agree low priority since we have plan in place to accomodate for this release 14:47:57 for info 2, we mention onos and opencontrail, but soo far we do not have also arno scenario available as well 14:48:06 i.e.odl 14:48:39 #info issue #2 also do not have Arno (ODL) available 14:49:29 for the test scenarios, I updated the page https://wiki.opnfv.org/brahmaputra_testing_page 14:49:42 A table for the available scenario (the one for which we have a jenkins job in CI) 14:49:57 A table for the candidate scenario (people are identify to lead the scenario) 14:50:01 ODL availability is lab availability issue isn’t it? not troubleshooting issues? 14:50:11 I also updated the page project to try to put the projects into a scenario 14:50:26 but it has to be checked by the project 14:50:54 for odl: labs are available... 14:51:11 joid has an integration, apex also but in virtual mode (lab issue) 14:51:41 compass has also a virtual mode but has a bm deployment without odl 14:52:05 so difficult to say, except apex that had lab issue, for the other, as far as I understand it is not a problem of lab 14:53:11 it is more a question for the installer project ... 14:53:37 yes was just looking if we have representation- they were all invited 14:54:14 I don’t see Artur on or Narinder 14:54:56 also don’t see Weidong— will ping them 14:56:19 trozet: is this correct that Apex issue for completing integration validation of all components is a lab issue only? 14:56:42 debrascott: Not really 14:57:03 debrascott: we havent integrated contrail yet 14:57:16 debrascott: ODL is done 14:57:27 what is the holdup on integrating contrail? 14:57:29 debrascott: onos is pending CI 14:58:25 trozet: by CI you mean development of Jenkins job? 14:58:44 debrascott: the folks that are integrating it upstream for us are not responsive, and the status is unknown, and we havent had the time to try to integrate it ourselves yet 14:59:10 debrascott: well CI was broken until it got fixed last night, then broke again last night due to upstream problems, which im trying to put an end to this morning 14:59:26 debrascott: so the ONOS patch is sitting there waiting to be verified in CI when CI is back up 15:00:03 i have to leave, have another meeting now 15:00:22 trozet who are you reaching out to for contrail? 15:00:28 same for me 15:00:34 I have to leave 15:00:38 debrascott: since im already giving status, the LF POD1 baremetal pod looks to be functioning again, so im working on baremetal deployment in LF lab today 15:00:55 debrascott: stuart mackie and some other folks inside of red hat who were supposed to be doing the integration 15:01:00 trozet: thanks 15:01:34 trozet: anything we can to to escalate? 15:02:11 debrascott: at this point we need to get CI stable again and stop this madness of upstream breaking us, then get ONOS and baremetal through 15:02:34 debrascott: then we will look at opencontrail, but maybe stuart could apply more pressure on his end to get things going 15:03:22 trozet: yes I understand heads down for now but need to continue in parallel so opencontrail is ready when you are. Will contact Stuart for you. 15:04:02 I think we need to make this meeting longer as we dont get through agenda. Maybe just temporarily until we get through the knotholes 15:04:08 <[1]JonasB> Contrail is an issue for Fuel as well, the contrail team doesnt have people to help out 15:04:56 Ok do we need to drop Contrail support for this release? What impact would that have overall? 15:05:39 <[1]JonasB> debrascott: That is being voted on in Genesis 15:06:07 JonasB: ok- let me know outcome. When is the vote? 15:07:51 #info we are past the meeting time & key people are dropping off. Will work offline to make progress on these stated issues. For tomorrow will lengthen this meeting to 1 hour. 15:08:11 debrascott: I think maybe you should join our weekly genesis meetings, we could probably use your input, and might give you better visibility 15:08:19 frankbrockners: ^ 15:09:06 trozet: I’ve tried but must have wrong meeting info. 15:09:24 will contact frank 15:09:27 debrascott: ok lets see if frankbrockners can add you 15:10:00 debrascott: i think maybe it would also be useful to have a release ops meeting like you did for the first 30 min, overall project status, then maybe another 30 min for installers only 15:10:20 thanks all for joining. We’ll chat again tomorrow 15:10:32 #endmeeting