17:00:13 <colindixon> #startmeeting tsc
17:00:13 <odl_meetbot> Meeting started Thu Jun  8 17:00:13 2017 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:00:13 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:13 <odl_meetbot> The meeting name has been set to 'tsc'
17:00:19 <colindixon> #topic roll call and agenda bashing
17:00:26 <colindixon> TSC members, please #info in
17:00:28 <colindixon> #info CaseyODL
17:00:30 <colindixon> #undo
17:00:30 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1cd6190>
17:00:32 <colindixon> #Info colindixon
17:00:37 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=57406#Agenda
17:00:49 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2017/tsc/opendaylight-meeting-tsc.2017-05-26-03.30.html las week's meeting minutes
17:01:31 <colindixon> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan#Schedule carbon SRs are updated based on votes of release dates
17:01:43 <rovarga> #info rovarga
17:01:44 <colindixon> #action phrobb to bring the need for a security manager to the board
17:01:48 <anipbu> #info anipbu
17:01:50 <colindixon> #action phrobb to bring the TSC replacement language to the board
17:02:04 <colindixon> #action colindixon to look to see if any current security response team members would like to voluntarily step down for any reason
17:02:19 <colindixon> #action colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
17:02:24 <colindixon> #action phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better at tutorials
17:02:29 <hideyuki> #info Hideyuki
17:02:38 <lori> #info lori
17:02:50 <abhijitkumbhare> #info abhijitkumbhare
17:03:10 <colindixon> #link https://git.opendaylight.org/gerrit/#/c/58124/ this is the beginnings of how to make it easy for projects to release without participating in a simultaneous release
17:03:22 <zxiiro> #info Thanh
17:03:31 <shague> #info shague
17:03:46 <colindixon> #action colindixon to cerate a bug (or sometign) to track off-cycle release tools and docs
17:04:37 <vishnoianil> #info Anil Vishnoi
17:05:00 <colindixon> #info colindixon did notifiy people about Beryllium-SR5 not happening and discussing the CVEs both in docs and to security-announce
17:09:27 <colindixon> #info dfarrell07 wants to talk about IPR with incoming code
17:09:37 <colindixon> #topic TSC mailing list votes and discussions
17:09:51 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007379.html We will move the APAC-time TSC call to Wed night/Thu morning
17:10:23 <colindixon> #action colindixon to make sure TSC meeting invites are right
17:11:05 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007375.html Carbon-SR1 will release on 7/6/2017
17:11:31 <CaseyODL> Sorry I'm not present. I'm about to get on a plane to SFO so I can go back to Beijing
17:11:37 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007418.html Nitrogen release plan is approved
17:11:49 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007416.html We will kick all projects out of Nitrogen to start
17:12:22 <colindixon> #topic events
17:12:29 <colindixon> #link https://www.opendaylight.org/global-events
17:12:35 <colindixon> #link https://wiki.opendaylight.org/view/Events:Main
17:13:11 <colindixon> #info everyone is in China for ONAP this week, OPNFV summit next week, and then LinuxCon Asia the week after
17:13:28 <colindixon> #info dfarrell07 has talks on ODL at the OPNFV summit
17:13:50 <colindixon> #info we had the DDF last week
17:16:27 <colindixon> #action colindixon to send out mail about how to plan DDFs forward
17:16:33 <colindixon> #undo
17:16:33 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x1de4750>
17:16:49 <colindixon> #action colindixon to send out mail about how to plan DDFs forward, some ideas are: regional topic-specific DDFs, colocating with other projects to do mega-DDFs
17:17:46 <colindixon> #info vishnoianil asks if we know why people aren't going, a lot of people have event fatigue
17:18:57 <colindixon> #topic boron
17:19:14 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#Schedule   <--- The last regularly scheduled Boron-SR4 is next Thursday with a cutoff on Sunday 6/15/2017 at 23:59 UTC.
17:19:20 <anipbu> #link https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/   <--- Boron Autorelease builds are healthy.
17:19:34 <anipbu> #link https://jenkins.opendaylight.org/releng/view/CLM/   <--- CLM failures are similar to that of Boron-SR3.  Although each violation were not individually signed off, the analysis indicates similar violations as in previous releases.
17:19:35 <vishnoianil> i think 2 day event is not the only reason for people not joining
17:19:54 <anipbu> #link https://bugs.opendaylight.org/show_bug.cgi?id=8623   <--- We will be using this bug to track General Boron-SR4 Security Concerns.
17:20:04 <colindixon> vishnoianil: I agree
17:20:07 <vishnoianil> i think we have 100 people who actively work on ODL all the times
17:20:33 <colindixon> #topic carbon
17:20:36 <anipbu> #link https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_9XugJp-6Qbbw20Omk/edit#gid=1746681968    <--- We are waiting on 3 projects to revise and merge their Carbon Release Notes: packetable.  We are missing release notes from 2 projects: next, dlux.
17:20:52 <vishnoianil> so some people might not really feel a need for join ddf as well (that's something we should explore why)
17:21:12 <vishnoianil> probably as a community we are executing pretty well through virtual channels :)
17:21:34 <vishnoianil> so i personally would suggest to have survey from linux foundation about the reasons
17:21:38 <vishnoianil> and then think of solutions
17:23:23 <colindixon> #info per the above, vishnoianil says he thinks it's likely not that it's a 2-day event and event fatigue alone
17:23:40 <jamoluhrsen> vishnoianil, +1 on the survey idea
17:24:21 <colindixon> #info zxiiro will branch carbon docs to fix a user issue
17:24:45 <colindixon> #topic release manager
17:25:05 <colindixon> #Info katie has stepped down as release manager
17:26:59 <colindixon> #info colindixon would like to see us create a TSC-appointed position called "release manager" and then call for nominees
17:27:23 <colindixon> #info rovarga asks what the job description is, anipbu says it's really two goals to track the release and facilitate projects coming together
17:27:46 <colindixon> #action anipbu and colindixon to write up a short blurb about what a release manager actually does
17:28:35 <colindixon> #info abhijitkumbhare asks if it's a still a volunteer position, colindixon says yes
17:28:43 <colindixon> #info colindixon notes that after this we would need to call for nominees
17:29:59 <colindixon> #info anipbu and others thank katie for her work
17:30:20 <abhijitkumbhare> +1 to katie for her work
17:31:19 <colindixon> #topic nitrogen
17:31:34 <colindixon> #undo
17:31:34 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x1e26450>
17:31:41 <colindixon> #Info anipbu offerst to help train anyone who wants to do it
17:31:44 <colindixon> #topic nitrogen
17:32:08 <vishnoianil> how we solve the problem of "no volunteer" ? :)
17:32:30 <abhijitkumbhare> yes - that was my thought vishnoianil :)
17:32:47 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2017-June/011123.html   <--- Nitrogen M0 Offset 0 Status Due.  Kindly request projects to declare their intent to participate in the Nitrogen Simultaneous Release.
17:32:57 <anipbu> #link https://wiki.opendaylight.org/view/Project_Proposals:Main#New_Pending_Creation_Review   <--- Projects have until the next three weeks (Offset 0: 6/14; Offset 1: 6/21, Offset 2: 6/28) to submit their project proposals and still participate in Nitrogen.
17:33:00 <colindixon> vishnoianil, abhijitkumbhare: I ws hoping that we'd see some people step forward, but we'll see what happens
17:33:10 <anipbu> anipbu recommends that new projects submit their proposal but should delay participation until Oxygen.
17:33:29 <anipbu> #link https://bugs.opendaylight.org/show_bug.cgi?id=8580   <--- In Nitrogen, we will manually release odlparent artifacts.  We will update releng/builder job, staging repository in nexus.  This will affect the version bumping scripts.  In future, projects can depend on range of odlparent versions.
17:34:02 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release/Nitrogen/Karaf#Status   <--- Nitrogen Karaf 4 Status
17:34:11 <vishnoianil> colindixon, TSC chair and Release engineer positions are bit tricky for getting volunteers :-)
17:34:26 <anipbu> #link https://docs.google.com/spreadsheets/d/1MYyGLFWN2RzUkJl8XMzXQ-3zWuOrUCQpIS6ORbmf4_U/edit#gid=1274532933   <--- Nitrogen Karaf 4 Tracking Spreadsheet
17:34:44 <anipbu> #info TWS Session on Monday 6/12/2017 to discuss Nitrogen Karaf 4 Project Action Items
17:34:52 <anipbu> #info Plan of Action: (1) Remove int/dist from autorelease (done) (2) Remove all non-offset0 from autorelease and int/dist - Bug 8625 (3) Fix Karat 4 Dependency Resolution - Bug 8622 (4) Add int/dist back into autorelease - Bug 8626 (5) Individually add projects back into autorelease and int/dist as they stabilize their build.
17:35:00 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007427.html anipbu and others recommend that new projects submit their proposal but should delay participation until Oxygen
17:35:56 <anipbu> #link https://bugs.opendaylight.org/show_bug.cgi?id=8628    <---Removed Infrautils until it solves the dependency on nitrogen odlparent OR until nitrogen odlparent releases
17:36:10 <anipbu> #link https://bugs.opendaylight.org/show_bug.cgi?id=8627   <--- Change the way we install features for CSIT. We are not going to use featuresBoot any longer and install from the karaf shell instead.
17:36:36 <anipbu> #link https://bugs.opendaylight.org/show_bug.cgi?id=8622   <--- Karaf 4 Dependency Resolution.  Four possible ways forward: (1) use the karaf 3 resolver in karaf 4 (2) fix all bundles/features to be reloadable (3) use dependency=true, which won't reload them (4) figure out if we can effectively enable --no-auto-refresh
17:37:08 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2017-June/011173.html    <--- Progress on old feature resolver in Karaf 4
17:37:17 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/58478/   <--- Sets up all karaf4-parent descendants to build distributions with
17:37:17 <anipbu> the old (Karaf 3) feature resolver by default
17:37:35 <anipbu> In Nitrogen, will we plan to support only Karaf 4 (drop Karaf 3) meaning we only build?  Do we to figure out how to keep doing a karaf 3 distribution for nitrogen so projects can keep running CSIT?
17:38:41 <colindixon> #info zxiiro  is workign on a per-project release job that can release outside of autorelease and is nearly done
17:40:09 <colindixon> #Info vrpolak asks if he should make a stable distribution or not, colindixon says that we can ignore it for now
17:42:36 <dfarrell07> I think if shague is okay with not having Karaf 3, that's a good data point
17:43:04 <colindixon> #info jamoluhrsen asks if we should have a Karaf 3 distribtion in nitrogen or not to allow for more testing
17:43:31 <shague> dfarrell07: yes, karaf 3 depracated is not a problem - as long as karaf 4 is working
17:43:41 <colindixon> #info colindixon and rovarga take the position that we shouldn't, if you want to test things, you can do the developement on top of carbon if you want to test things easier
17:44:00 <dfarrell07> shague: yeah, the implication is that netvirt will not be able to test with it while karaf 4 is stabilizing
17:44:06 <colindixon> #info enabling people who are working on new features before trying to get their features to come up in Karaf 4 seems bad
17:45:45 <colindixon> #info vishnoianil asks how confident are we that we'll get to karaf 4 in nitrogen
17:45:58 <colindixon> #Info vishnoianil alsk asks if we have a backup plan if we can't moce to karaf 4
17:46:27 <shague> agreed with anil... for some reason I can't get off mute, but that is key - if we are doing karaf 4, we need to work quickly and get to a stable state
17:47:05 <colindixon> #Info colindixon says no, because if we can't migrate to karaf 4 in 2 months with it as our primary/only focus, then we need need to radically re-evaluate how the project works
17:47:22 <jamoluhrsen> i want it to be clear that it's basically seen that we should waste no cycles on karaf3 for nitro. that's what I'm hearing
17:47:42 <colindixon> jamoluhrsen: that's my take
17:48:41 <anipbu> +1 to ed
17:49:14 <colindixon> #startvote shall we say that we will focus solely on Karaf 4 in nitrogen and not spend any cycles on karaf 3? -1,0,+1
17:49:14 <odl_meetbot> Begin voting on: shall we say that we will focus solely on Karaf 4 in nitrogen and not spend any cycles on karaf 3? Valid vote options are -1, 0, +1.
17:49:14 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:49:16 <colindixon> #vote +1
17:49:30 <jamoluhrsen> #vote +1
17:49:31 <rovarga> #vote +1
17:49:35 <anipbu> #vote +1
17:49:36 <vishnoianil> #vote +1
17:49:36 <edwarnicke> #vote +1
17:49:41 <zxiiro> #vote +1
17:49:41 <abhijitkumbhare> #vote 1
17:49:41 <odl_meetbot> abhijitkumbhare: 1 is not a valid option. Valid options are -1, 0, +1.
17:49:42 <hideyuki> #vote +1
17:49:48 <shague> #vote -1
17:49:48 <abhijitkumbhare> #vote +1
17:49:50 <lori> #vote +1
17:50:02 <colindixon> #endvote
17:50:02 <odl_meetbot> Voted on "shall we say that we will focus solely on Karaf 4 in nitrogen and not spend any cycles on karaf 3?" Results are
17:50:02 <odl_meetbot> +1 (10): rovarga, zxiiro, edwarnicke, hideyuki, colindixon, lori, jamoluhrsen, anipbu, vishnoianil, abhijitkumbhare
17:50:02 <odl_meetbot> -1 (1): shague
17:50:07 <shague> I can't unmute for some reason
17:50:16 <colindixon> shague: :-(
17:50:39 <shague> only concern is that we actually get karaf 4 done
17:50:48 <colindixon> shague: can you elaborate on your -1 and let us know what we can do to help
17:51:08 <colindixon> #info shague is just concerned that we will be able to get Karaf 4 to work
17:51:12 <shague> we did have some features we wanted in, so that would push us to carbon whcih we don't like
17:52:56 <colindixon> #info colindixon notes that (to his knowledge) pretty much all projects should be able to start buildign and testing their local karaf 4 distribution to get it working
17:53:06 <colindixon> #info so everyone should be able to be doing something toward getting us onto karaf 4
17:53:22 <colindixon> #topic system integration and test
17:53:38 <colindixon> #info nothing major, Boron CSIT is still running daily, it will be weekly after SR4
17:53:48 <colindixon> #topic infastructure
17:54:19 <colindixon> #info we have had long queues (currently 142 down from 216 this morning east coast)
17:55:31 <colindixon> #info colindixon asks if we can purge jobs that don't do anything, nobody looks at, etc.
17:56:28 <colindixon> #info colindixon notes that verifies and merges are still going through, and it's been a bit slow, but not bad
17:57:12 <colindixon> #topic pulling in commits from github to int/pack
17:57:39 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007435.html
17:58:29 <colindixon> #Info dfarrell07 asks if he can pull that in
17:59:08 <colindixon> #info colindixon and edwarnicke say that for all the commits from dfarrell07 this shoudl be fine, if there are commits from others, we need to make sure they agree to the OpenDaylight DCO
17:59:55 <colindixon> #info edwarnicke notes that you really want the logging the approval from other authors as the commit history in the repo
18:01:44 <colindixon> #topic cookies
18:01:54 <colindixon> #endmeeting