14:00:54 <timirnich> #startmeeting weekly TSC call
14:00:54 <collabot`> Meeting started Tue Jan 30 14:00:54 2018 UTC.  The chair is timirnich. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:54 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:54 <collabot`> The meeting name has been set to 'weekly_tsc_call'
14:01:13 <timirnich> #chair rpaik
14:01:13 <collabot`> Current chairs: rpaik timirnich
14:01:18 <timirnich> #topic roll call
14:01:22 <ttallgren> #info Tapio Tallgren
14:01:24 <fuqiao> #info fuqiao
14:01:25 <timirnich> #info Tim Irnich
14:01:25 <bh526r> #info Bin Hu
14:01:27 <fdegir> #info Fatih Degirmenci
14:01:27 <rossella_s> #info Rossella Sblendido
14:01:35 <mtahhan> #info Maryam Tahhan
14:01:40 <XavierCosta> #info Xavier Costa
14:01:41 <bjskerry> #info Brian Skerry
14:01:42 <kubi003> #info Kubi
14:01:48 <rpaik> we have a quorum
14:01:57 <frankbrockners> #info Frank Brockners
14:02:10 <trevor_intel> #info Trevor Cooper
14:02:13 <dneary__> #info dneary
14:02:16 <jose_lausuch> #info Jose Lausuch
14:02:17 <rpaik> #topic approval of previous minutes
14:02:33 <rpaik> #info no comments on minutes thus approved
14:02:36 <timirnich> #topic agenda bashing
14:03:06 <rpaik> #link https://wiki.opnfv.org/display/meetings/TSC#TSC-January30,2018 today's agenda
14:03:45 <rpaik> #info no other topics suggested
14:04:59 <rpaik> #topic TSC member backfill
14:06:16 <rpaik> #info mtahhan will be able to propose an alternate that TSC members can vote on
14:07:05 <rpaik> #info discussion on the alternate to serve the remainder of the term (until ~September'18)
14:07:37 <bryan_att> #info Bryan Sullivan
14:07:38 <rpaik> #agree that the TSC will vote on an alternate TSC member suggested by mtahhan
14:08:00 <rpaik> #topic OPNFV Verified Program launch update
14:09:01 <rpaik> #info Chris Donley noted that LFN approved the OPNFV C&C committee to continue operating
14:09:47 <rpaik> #info the plan is to launch OVP next week and beta participants are re-submitting their results
14:10:34 <rpaik> #info bdwick confirms that 4 be re-submissions have come in as of yesterday and will be reviewed by C&C members
14:11:24 <rpaik> #info launch is February 6th as there was a desire to space out from LFN launch last week.
14:12:14 <rpaik> #info press release draft will be circulated amongst C&C plus marketing committee members for review
14:12:34 <rpaik> #info there will also be a blog post penned by Chris Donley
14:17:09 <rpaik> #info Chris Donley notes that community is in early stages of discussion regarding the "second release" for OVP
14:18:28 <rpaik> #topic release update
14:19:30 <rpaik> #info dmcbride notes that MS3.2 (pass health check for sdn-based scenario) is this week and installer teams are on track for the milestone
14:19:57 <rpaik> #info MS5 (scenario integration) is March 2nd
14:20:36 <dmcbride> #link https://wiki.opnfv.org/display/SWREL/Fraser
14:21:37 <rpaik> #topic LF IT/infra update
14:22:43 <rpaik> #info bramwelt notes that Jenkins server testing will continue this week
14:23:03 <Julien-zte> #info Julien
14:23:26 <rpaik> #info there was also issue with mailing list queues yesterday and this has been fixed
14:23:31 <aricg> #info https://gerrit.opnfv.org/gerrit/#/c/50381/
14:24:52 <rpaik> #info aricg notes that the goal is to easily identify PTLs from INFO files and will be discussed on Thursday's Technical Discussion call for feedback
14:26:23 <rpaik> #info this is so that only PTLs will be able to update information on the TestAPI
14:27:15 <rpaik> #topic Apex installer update
14:29:24 <rpaik> #info dneary notes that Apex team would like towards XCI-like model (pointing to the tip of trunk) and had discussions with a number of PTLs plus dmcbride
14:30:39 <rpaik> #info dmcbride notes that we're in the middle of the Fraser release cycle and concerned about impact on the release
14:32:24 <rpaik> #info for example Apex and test projects may need to redo Milestones 3/4 plus there maybe impact on MS5
14:37:44 <rpaik> #info mtahhan asks if the transition can wait until Fraser stable is cut (if there's a big risk in moving from Pike to Queen)
14:39:56 <bryan_att> #info can someone explain how a change in OOO impacts Barometer?
14:46:37 <trozet> #info Apex has the ability to deploy different versions of openstack and opendaylight.  Versions can be supplied in the deploy settings file, and artifacts will be downloaded at deploy time from upstream.  Also, upstream openstack gerrit patches can be provided which will be automatically pulled in and applied during deployment
14:46:47 <rpaik> thanks trozet
14:46:51 <trozet> np
14:48:02 <mtahhan> bryan_att, Tim explained - it won't because of backward compatibility... the ask would be that the projects make their changes/additions upstream in the relevant repositories and that would then get consumed by Apex...
14:49:02 <trozet> thanks mtahhan.  And I can help form/review the upstream patches to OOO
14:51:34 <bryan_att> #info I understand the momentum across projects shifts over time, but this puts additional requirements on feature projects to work in the multiple upstream communities. I would rather recommend that projects work to dis-aggregate themselves from upstream installer projects as dependencies. That is a more sustainable approach.
14:56:07 <rpaik> #info fdegir asks if there's a need to vote on a version of OpenStack (or other components) in an OPNFV release
14:57:51 <trozet> #info one non-obvious way we have version info for ODL is in the deploy settings file, which are set per release
14:58:44 <fdegir> this requires longer discussion but in my opinion, it is more important to achieve full traceability and reproducibility instead of releasing something which we don't even know what went into it
14:59:48 <fdegir> it is fine to decide on minimum versions of the components but using later version should be fine as long as the composed platform passes the criteria is set by OPNFV and projects can list what went into the scenarios they develop
15:01:11 <rpaik> #info suggestion to the Apex team to come back to the TSC to report on impact to existing projects with a new approach
15:01:29 <dmcbride> dropping off to start the release call
15:01:39 <dmcbride> please join the release call following this meeting
15:01:55 <rpaik> #info there will be also a separate/broader discussion on OPNFV releases going forward
15:02:21 <fdegir> as In mentioned, we will give xci update this Thursday and will talk about the possibility of having something released as  "experimental"
15:02:59 <timirnich> #endmeeting