16:02:53 <dmcbride> #startmeeting OPNFV Release
16:02:53 <collabot> Meeting started Tue Jan 17 16:02:53 2017 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:53 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:02:53 <collabot> The meeting name has been set to 'opnfv_release'
16:03:08 <dmcbride> #topic roll call
16:03:12 <dmcbride> #info David McBride
16:03:18 <jose_lausuch> #info Jose Lausuch
16:03:25 <sofiawallin> #info Sofia Wallin
16:03:51 <jmorgan1> #info Jack Morgan
16:04:19 <trevor_intel> #info Trevor Cooper
16:04:25 <uli-k> #info Uli
16:04:38 <tallgren> #info Tapio Tallgren
16:08:28 <bryan_att> #info Bryan Sullivan
16:08:49 <dmcbride> #topic Daisy integration with functest
16:09:08 <dmcbride> #info jose_lausuch continues to provide information to the Daisy team
16:09:15 <dmcbride> #info progress is unclear
16:09:45 <bryan_att> can anyone provide me the best link to a description of the OPNFV infrastructure program for CI/CD ? I need to pass this on internally. The Releng wiki page doesn't have much info.
16:09:51 <dmcbride> #topic Danube schedule
16:11:49 <fdegir> bryan_att: what are you asking exactly?
16:11:59 <fdegir> bryan_att: I mean "OPNFV Infrastructure Program"
16:12:01 <dmcbride> #topic Movie status
16:12:11 <bryan_att> CI/CD, the toolchain etc
16:12:37 <bryan_att> I'm not finding a lot of detail on the wiki
16:12:54 <fdegir> bryan_att: we moved all that info to infra space
16:13:04 <fdegir> bryan_att: releng only contains the project info
16:13:19 <fdegir> bryan_att: https://wiki.opnfv.org/display/INF/Continuous+Integration
16:13:28 <fdegir> above page is still WIP as mentioned on the page
16:13:31 <bryan_att> thanks
16:13:39 <fdegir> bryan_att: tools: https://wiki.opnfv.org/display/INF/Software+Infrastructure
16:13:49 <fdegir> bryan_att: hw: https://wiki.opnfv.org/display/INF/Hardware+Infrastructure
16:14:20 <fdegir> child pages also contain specifics of some of the stuff
16:14:53 <fdegir> but some pages are in need of updates, or empty as you or your colleagues will notice
16:15:11 <fdegir> if you pass me the info about a certain thing, I'll do my best to update the page
16:15:17 <dmcbride> #info Prakash reports that Movie team is making progress in adding test cases to the TC database
16:15:36 <dmcbride> #info Prakash says that there are no longer any access issues
16:16:03 <dmcbride> #topic Danube schedule
16:17:59 <jmorgan1> #info Intel labs still needing to be brought online are kvm4nfv, ovsnfv, vsperf, Barometer
16:18:28 <jmorgan1> #info Intel lab will be back online by Wednesday this week
16:20:11 <trozet> apex works with nosdn and odl_l3
16:20:13 <dmcbride> #info bryan_att reports that the Barometer project has been delayed due to resource unavailability
16:20:14 <trozet> on Danube
16:21:30 <dmcbride> #info bryan_att also notes that the unavailability of scenarios for Danube has also been a problem
16:25:44 <jose_lausuch> I'm concerned about Joid https://build.opnfv.org/ci/view/joid/job/joid-deploy-baremetal-daily-master/
16:25:52 <jose_lausuch> no deployments since 28 december
16:26:02 <bryan_att> #info - to clarify there are several underlying delay issues beyond the lab infra issues we experienced this time. I don't want to conflate these, but they are: (1) the timeline in which current upstream code is integrated in installers; (2) the complexity and resource requirements of OPNFV deploys
16:26:36 <dmcbride> #info trevor_intel also reports being delayed due to resource migration
16:28:38 <bryan_att> #info as a result this year I am shifting toward more independence from OPNFV scenarios as a basis for test/dev, with functest integration at the right time (when installers are ready) and using OPNFV CI/CD infra for all that testing, rather than my dev lab resources
16:28:44 <dmcbride> #info trevor_intel asks about documentation requirements
16:29:40 <dmcbride> #info sofiawallin reports that documentation setup will be similar to prior releases, even though we are switching to read-the-docs
16:29:55 <dmcbride> #info doc WG continues to define requirements
16:31:07 <bryan_att> #info this approach should enable more early/continual progress on current upstream release support and features - in essence this is like OPNFV on Devstack, and no/few tests will be OPNFV-specific (all will run on upstream dev environments alone)
16:32:50 <dmcbride> #info sofiawallin reports that the doc WG is having an additional meeting on Weds (tomorrow)
16:33:03 <dmcbride> #topic AoB
16:33:27 <dmcbride> #info jose_lausuch expresses concern about status of Joid
16:33:53 <dmcbride> #info narinder reports that Joid has been impacted by the Intel lab migration
16:34:50 <jmorgan1> #info Intel POD5 Node5 needs to be reset due to IMPI being stuck
16:37:34 <dmcbride> #action narinder to update team on status of Joid at the next release meeting (Jan 24)
16:37:45 <dmcbride> #endmeeting