12:58:42 <uli-k> #startmeeting TSC weekly call
12:58:42 <collabot`> Meeting started Tue Jul 11 12:58:42 2017 UTC.  The chair is uli-k. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:58:42 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
12:58:42 <collabot`> The meeting name has been set to 'tsc_weekly_call'
12:58:52 <uli-k> #topic roll call
12:59:00 <hongbo852147> #info  hongbo
12:59:10 <uli-k> #chair rpaik
12:59:10 <collabot`> Current chairs: rpaik uli-k
12:59:29 <cgoncalves> #info Carlos Goncalves (proxy for Xavier Costa)
12:59:39 <viktor_t> #info Viktor Tikkanen (substitute for Tapio Tallgren)
12:59:58 <naga_lenovo> #info naga chumbalkar
13:00:16 <lhinds> #info lhinds Luke Hinds
13:00:20 <morgan_orange> #info Morgan Richomme
13:00:33 <timirnich> #info Tim Irnich
13:00:59 <fdegir> #info Fatih Degirmenci
13:01:15 <bryan_att> #info Bryan Sullivan
13:01:20 <rbbratta> #info Ross Brattain (proxy for Jack Morgan)
13:01:46 <rpaik> #topic agenda bashing
13:02:39 <rpaik> #topic approval of previous meeting minutes
13:02:51 <rpaik> #info no comments on previous minutes thus approved
13:03:06 <rpaik> we now have a quorum
13:03:15 <rossella_s> #info Rossella Sblendido
13:03:22 <rpaik> #topic agenda bashing
13:03:59 <rpaik> #link https://wiki.opnfv.org/display/meetings/TSC#TSC-July11,2017 today's agenda
13:04:29 <rpaik> #info no other topics sugggested
13:04:44 <rpaik> #topic Danube/Euphrates update
13:05:52 <uli-k> #link https://wiki.opnfv.org/download/attachments/2925933/D3%20status%2020170711.pptx?version=1&modificationDate=1499744370029&api=v2
13:05:54 <rpaik> #info dmcbride discusses scenario status for Danube 3.0 scheduled for July 14th
13:06:18 <rpaik> #link https://wiki.opnfv.org/download/attachments/2925933/D3%20status%2020170711.pptx?version=1&modificationDate=1499744370029&api=v2 David's presentation on Danube 3.0
13:06:43 <fuqiao> #info fuqiao
13:07:34 <rpaik> #info dmcbride notes that compass builds seem to have issues on Ericsson HW resources
13:09:19 <rpaik> #info dmcbride notes that lot of scenarios are still having issues for Danube 3.0
13:09:47 <uli-k> #info dmcbride notes that Apex scenarios have lower success rate than other installers
13:10:13 <uli-k> #info a possible reason is the high number of scenarios that have to share the same resources
13:11:49 <Julien-zte> #info Julien
13:18:12 <rpaik> #info hongbo notes that the compass team expects to resolve the deploy issues in the next few days  when facility issues are reolved
13:18:22 <dneary> #info dneary (on call since top of the hour)
13:19:14 <rpaik> #info dmcbride notes that there are two new scenarios planned for Danube 3.0 (involving Barometer and ONOS-SFC)
13:19:45 <uli-k> #info the question is what to do about a big number of scenarios that were released in 1.0 or 2.0 and are failing now
13:21:12 <rpaik> #info options are (1) release as is (2) move the release date again (3) drop Danube 3.0
13:21:42 <uli-k> #info we have 3 choices: 1. release now with bad quality, 2. shift the release date again, 3. drop Danube 3.0 completely
13:24:15 <rpaik> #info timirnich and dneary notes their preference for option #1 to get Danube 3.0 behind them
13:27:40 <trozet> #info for apex, onos, ovn-ha, sfc scenarios can be removed
13:31:21 <trozet> os-odl_l3-fdio-ha deployed recently: https://build.opnfv.org/ci/job/apex-deploy-baremetal-danube/519/
13:31:25 <trozet> jlinkes:^
13:31:47 <jlinkes> trozet: yea I did see that
13:33:25 <rpaik> #action dmcbride to follow-up with scenarios owners on the health of their scenarios for Danube 3.0
13:35:17 <rpaik> #topic LF IT/infra update
13:36:30 <morgan_orange> #info test DB testresults.opnfv.org no more answering
13:36:48 <morgan_orange> #info ticket open 42911
13:36:57 <rpaik> #topic test wg update
13:38:38 <rpaik> #info morgan_orange notes that there's been a lack of stress testing that has been requested by EUAG
13:40:11 <rpaik> #info there's a need to do stress testing on a "stable" solution
13:40:48 <rpaik> #info this requires two chains of testing for the upcoming release and the previous release (for stress testing)
13:49:17 <rpaik> #info morgan_orange notes that we already have 2 CI resources for master for stable today
13:51:14 <Julien-zte> rpaik I think we share the same resources for master and stable not independent
13:55:07 <rpaik> #action morgan_orange to continue discussion with the Infra WG and come back to the TSC with a proposal
14:00:09 <morgan_orange> #info need for stress AND resiliency testing
14:00:43 <Julien-zte> #info I also agree to reserve some resources for the test group after the stable release.  We use opnfv release in our env and we find it sometimes down after 3-7 days deployed. theses issues maybe not happen only in one day.
14:02:06 <rpaik> #endmeeting