17:00:31 <colindixon> #startmeeting tsc
17:00:31 <odl_meetbot> Meeting started Thu Aug  4 17:00:31 2016 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:00:31 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:31 <odl_meetbot> The meeting name has been set to 'tsc'
17:00:32 <colindixon> #topic agenda bashing and roll call
17:00:34 <colindixon> #chair phrobb
17:00:34 <odl_meetbot> Current chairs: colindixon phrobb
17:00:35 <colindixon> TSC members please #info in
17:00:38 <gkaempfer> #info gkaempfer
17:00:40 <colindixon> #info colindixon
17:00:50 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-07-28-17.00.html last week's meeting minutes part 1
17:00:59 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-07-28-17.40.html last week's meeting minutes part 2
17:01:13 <adetalhouet> #info adetalhouet
17:01:26 <colindixon> #action anipbu to track the removal of ancient dependencies and readout next time how far we get
17:01:35 <abhijitkumbhare> #info abhijitkumbhare
17:01:38 <colindixon> #action colindixon to get CaseyODL to replay about nofollow on the TSC list so we get an actual ruling
17:01:49 <colindixon> #action anipu to follow up with relevant projects about distribution size: https://lists.opendaylight.org/pipermail/release/2016-July/007250.html
17:02:10 <colindixon> #action colindixon to try to drive some/all of the ongoing TSC discussions to completion
17:02:23 <dfarrell07> #info Daniel Farrell
17:02:48 <vishnoianil> #info Anil Vishnoi
17:03:02 <ChrisPriceAB> #info Chris Price
17:03:17 <colindixon> #action edwarnicke to send out his analysis ouf how to remove nodejs servers from people pulling in dlux to see if that helps
17:03:23 <mohnish__> #info Mohnish Anumala
17:04:15 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-August/005725.html features that are currently labeled as experimental, comment there if you disagree or things have changed
17:04:25 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron/Carbon?
17:04:32 <colindixon> #action phrobb to work on having a policy for how attendance to design forums works going forward with community involvement
17:04:37 <colindixon> #action colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time
17:05:02 <colindixon> #action phrobb to add linuxcon europe to the events list
17:05:13 <colindixon> #action colindixon to add TSC elections to the agenda for next week
17:05:35 <colindixon> #acion colindixon to work with anipbu on making when you need to be in distriubtion even clearer in the Carbon release plan, maybe even at M5
17:06:13 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=48214#Agenda the agenda in it's usual place
17:06:15 * ChrisPriceAB wants to run for TSC election and incubate the software defined wall project
17:06:51 <abhijitkumbhare> is that the Trump wall ChrisPriceAB ? :)
17:07:05 <abhijitkumbhare> Or the Pink Floyd Wall :)
17:07:06 <colindixon> #info edwarnicke says that he's been trying to help get projects into the distribution, it's been bumpy for a variety of reasons,b ut making progress
17:07:14 <ChrisPriceAB> I don't have the hair for that one...  (nor can I get audio working...)
17:07:27 <rovarga> #info rovarga for jmedved
17:07:28 * ChrisPriceAB fumbles further with the cables and keyboard
17:07:46 <colindixon> #topic TSC mail list discussions and votes
17:08:13 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-July/005695.html vote to set tentaive dates for a tradition carbon release plan passed
17:08:44 <colindixon> #info next step it hammer out what we need to get done and plan it for this release so that we can credibly take a stab at fast and/or phased if we want to for Nitrogen
17:10:06 <colindixon> #action colindixon to start an e-mail thread trying to start a fast and/or phased experience during Carbon (pull in skitt, rovarga, and edwarnicke)
17:10:17 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-July/005539.html  escalation process we have in OpenDaylight
17:10:31 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005377.html  Additional questions in the Project Proposal Template
17:10:35 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005407.html  Asking the Board to Remove the Singularity Principle
17:10:45 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-July/005594.html  Categorizing projects, both on the wiki and for new projects to browse
17:11:10 <edwarnicke> #info edwarnicke
17:11:26 <colindixon> #topic event
17:11:32 <colindixon> #link https://www.opendaylight.org/global-events
17:11:35 <colindixon> phrobb:
17:12:03 <tykeal> stop! backup up this packet ;)
17:12:39 <colindixon> #info openstack sillicon valley and openstack east coming up wtih OpenDaylight involvement
17:12:47 <colindixon> #info opendalyight summit is coming up at the end of september
17:13:13 <colindixon> #info linuxcon Europe has a talk on ODL performance (from dfarrell07)
17:13:53 <colindixon> #info CFP for the OpenDaylight forum in India, CFP closes next week
17:14:20 <colindixon> phrobb: are you going to do the boron update
17:14:41 <jamoluhrsen> colindixon, think you are breaking up
17:14:42 <colindixon> it would be great if you could do it
17:14:46 <colindixon> I'm apparently undeground
17:15:53 <colindixon> #topic boron
17:16:05 <colindixon> #info There are plans to change the yang model leaf name of  tcp_flag in OpenFlowPlugin. Fix patches are pushed to all the impacted project: netvirt, genius, sfc, nic, vtn, didm
17:16:23 <colindixon> #link https://wiki.opendaylight.org/view/Simultaneous_Release/Boron/Waiver/API/Records#OpenFlow_plugin_Tcp_Flags_API_Change_Waiver   <--- Link to API Change
17:16:42 <colindixon> #info Kindly remind projects to submit API Change Waiver if submitting any changes to the API such as yang files after M4
17:16:51 <colindixon> #link https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/203/   <--- Successful build of Boron Autorelease.
17:16:56 <colindixon> #info Kindly remind project not to introduce further breakages into autorelease.
17:17:17 <colindixon> #link https://lists.opendaylight.org/pipermail/release/2016-August/007550.html   <--- Boron M5 Offset 2 Status is due Today (8/4)
17:17:31 <colindixon> #info that also means we'll be doing branch cutting today
17:20:40 <colindixon> #info dfarrell07 and zxiiro say that there have been some conversations about delaying the release and/or M5 if we're having issues
17:21:08 <colindixon> #info jamoluhrsen says that if we weren't able to fix the distribution size limit, we might have to delay the final release, but seemingly not M5
17:22:05 <colindixon> #info LuisGomez says we need to fix the distribution size issue in 1-2 days or we really will need to consider letting the release slip
17:22:05 <colindixon> lost cell again
17:22:41 <abhijitkumbhare> +1 rovarga - on having too big download
17:22:55 <jamoluhrsen> +1 rovarga - on having too big download
17:24:02 <colindixon> #info colindixon asks if there's a  reason we couldn't temporarily increase the nexus size limit to avoid slipping Boron while we fix it?
17:24:02 <colindixon> phrobb: or somebody else if you could scribe for a bit, that would help
17:24:02 <colindixon> not sure when I get out of this tunnel
17:24:12 <jamoluhrsen> #link https://bugs.opendaylight.org/show_bug.cgi?id=6341 <--- blocker bug for distro size
17:24:42 <vishnoianil> dfarrell07, is saying that distribution size is increased probable because of running odl offline
17:24:44 <phrobb> #info, discussion ensues on the sanity of the huge distro.
17:25:01 <colindixon> to be clear, I'm not saying we shoudln't fix it, but that if we're losing test coverage and jeapordizing the release by not temporarliy removing the file limit, that seems like a bad idea
17:25:05 <vishnoianil> that actually bring in lot of jars/packages in the distribution
17:25:12 <colindixon> e.g., (i) fix texts, (ii) in parallel fix size
17:25:41 <jamoluhrsen> colindixon: and (ii) has a release blocker bug, so we can go this route
17:26:46 <jamoluhrsen> 100G  :)
17:27:03 <vrpolak> At least one distribution Bug is already open: https://bugs.opendaylight.org/show_bug.cgi?id=6341
17:27:18 <phrobb> #info the plan proposed is for Andy to increase the size allowed in Nexus so that other progress can be made.  At the same time a blocking bug will be posted on the distro size and a condition of bug fix is to revert the max size limit to 500MB
17:27:26 <colindixon> #action tykeal to increase the file limit from 512MB to 600MB to get us pas tthis hump
17:27:45 <jamoluhrsen> I will
17:27:49 <rovarga> this is MiB, right?
17:28:10 <phrobb> #info Andy to increase the size by 100MB to 600MB while this issue persists and the blocking bug is open
17:28:36 <colindixon> #action jamoluhrsen should add to the bug that we need to have the nexus file size limit set to 512 MB again
17:29:53 <rovarga> #info quote: [8/4/16 16:13:51] <shague> zxiiro: any idea if we are going to relax the m5 deadline today? infra has been painful during this crucial time
17:30:41 <colindixon> #info colindixon says that projects should please raise their issues on the release and/or tsc list so we can figure out how to deal with it up-to and/or including a delay
17:31:42 <jamoluhrsen> vtn is probably affected the same as netvirt, but they can speak to that.
17:32:43 <colindixon> #info colindixon says that if it's one project and a leaf project (which I think netvirt is) that this shoudl be handled for the one project instead of delaying the entire release over it
17:32:50 <colindixon> #info jamoluhrsen says VTN likely has simlar issues
17:33:06 <colindixon> #info colindixon says, obviously we'll dealy the release if we have to at the end if we'll have regressions
17:33:33 <colindixon> #info that being said (and edwarnicke and dfarrell07 agree) that we should wait until we get to the point we feel we have to dealy the final relese
17:34:14 <colindixon> #info obviously, if the approach seems fatally flawed, please speak up, the TSC exists to help projects get stuff done
17:34:26 <colindixon> #topic stable/beryllum
17:34:57 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-August/005710.html Beryllium-SR3 release status: Ready to go
17:35:38 <colindixon> #startvote shall the TSC approve the Beryllium-SR release as linked to in the above mail? -1,0,+1
17:35:38 <odl_meetbot> Begin voting on: shall the TSC approve the Beryllium-SR release as linked to in the above mail? Valid vote options are -1, 0, +1.
17:35:38 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:35:40 <colindixon> #vote +1
17:35:49 <abhijitkumbhare> #vote +1
17:35:51 <dfarrell07> #vote +1
17:35:56 <ChrisPriceAB> #vote +1
17:36:10 <colindixon> gkaempfer, edwarnicke
17:36:22 <colindixon> vishnoianil:
17:36:25 <adetalhouet> #vote +1
17:36:31 <colindixon> mohnish__:
17:36:42 <mohnish__> #vote +1
17:36:50 <rovarga> #vote +1
17:36:50 <vishnoianil> #vote +1
17:36:55 <edwarnicke> #vote +1
17:37:03 <gkaempfer> #vote +1
17:37:04 <colindixon> #endvote
17:37:04 <odl_meetbot> Voted on "shall the TSC approve the Beryllium-SR release as linked to in the above mail?" Results are
17:37:04 <odl_meetbot> +1 (10): mohnish__, gkaempfer, rovarga, adetalhouet, ChrisPriceAB, dfarrell07, edwarnicke, colindixon, abhijitkumbhare, vishnoianil
17:37:21 <colindixon> #agree by consenus, the TSC approves the Beryllium-SR3 release
17:39:03 <colindixon> #topic singlularity discussions
17:39:38 <colindixon> #info this was a topic at the board 2 meetings ago, and a small group of people was going to try to explain the intent of those principles and it would maybe help the discussion
17:40:08 <colindixon> #info phrobb says he expects that to come back at the beginning of september
17:40:30 <colindixon> #topic TSC elections
17:40:41 <colindixon> #info there was TWS on Monday on the TSC elections and our progress
17:40:56 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-08-01-17.00.html meeting minutes
17:41:19 <colindixon> #link https://wiki.opendaylight.org/view/Tech_Work_Stream:Main there's a WebEx recording that should be posted here
17:42:17 <colindixon> #info the results of the meeting were that we needed to do 3 things: (1) pick represented groups, (2) pick election cadence, (3) make sure we work out corner cases of using the tools we have
17:43:24 <colindixon> #action colindixon and edwarnicke to try to work through the corner cases and process of the TSC elections
17:43:31 <phrobb> #linkhttps://meetings.webex.com/collabs/url/R2WM4rG0u4td9xj_n_xbKIKyWrZp7hZvOlvPnsnQYhG00000 <-- Link to Webex Recording of the TWS meeting on the Elections Process
17:44:01 <colindixon> #action dfarrell07 to upate the wiki about what happens when a person is a PTL for more than one project in the same represented group
17:44:08 <colindixon> #link https://meetings.webex.com/collabs/url/R2WM4rG0u4td9xj_n_xbKIKyWrZp7hZvOlvPnsnQYhG00000 <-- Link to Webex Recording of the TWS meeting on the Elections Process
17:44:32 <colindixon> #info the other corner case is how to do weighted elections after the fact, e.g., scaled-popularity
17:44:40 <colindixon> dfarrell07: can you #info the point about the RGs?
17:44:52 <colindixon> #link https://wiki.opendaylight.org/view/TSC:Election_Proposal the wiki page on this
17:45:39 <colindixon> #link https://wiki.opendaylight.org/view/TSC:Election_Proposal#All_Types.2C_Mature_Lifecycle_States in particular dfarrell07 says this one seems to have had the most support so far
17:46:05 <colindixon> #action dfarrell07 to try to get us to the point that we coudl vote on (1) and (2) above
17:46:39 <colindixon> #topic cookies
17:46:45 <colindixon> #endmeeting