17:00:13 <colindixon> #startmeeting tsc
17:00:13 <odl_meetbot> Meeting started Thu Jul 14 17:00:13 2016 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:18 <colindixon> #topic agenda bashing and roll call
17:00:21 <colindixon> #chair phrobb anipbu
17:00:21 <odl_meetbot> Current chairs: anipbu colindixon phrobb
17:00:29 <colindixon> TSC members please #info in
17:00:32 <colindixon> #info colindixon
17:00:33 <gkaempfer> #info gkaempfer
17:00:58 <rovarga> #info rovarga for jmedved
17:00:59 <Chrisy> #info Chris Luke
17:01:00 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47673 agenda
17:01:07 <abhijitkumbhare> #info abhijitkumbhare
17:01:13 <mohnish__> #info mohnish anumala
17:01:15 <colindixon> #info Chrisy  is here for edwarnicke
17:01:56 <vishnoianil> #info Anil Vishnoi
17:01:58 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-07-07-17.00.html last week's meeting minutes
17:02:38 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47673#Committer_promotion_process_for_contributors is no longer a draft per last week's meeting minutes
17:02:39 <jamoluhrsen> #info Jamo Luhrsen  (for Daniel Farrell)
17:03:13 <colindixon> #action vishnoianil, phrobb and abhijitkumbhare to schedule a meeting to discussion the project categorization, so that it can be helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope.
17:03:22 <colindixon> #action phrobb to work on having a policy for how attendance to design forums works going forward with community involvement
17:04:01 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-July/005593.html we have a revision to the ODL summit registration where you can attend the DDF without having to have a gerrit patch
17:04:12 <colindixon> https://lists.opendaylight.org/pipermail/tsc/attachments/20160714/658d5edf/attachment-0001.png
17:04:43 <colindixon> #action phrobb to create a wiki page with topics for the September DDF
17:04:54 <colindixon> #action skitt or colindixon to work on removing the ancient org.eclipse dependencies in controller (and elsewhere?)
17:05:01 <colindixon> #action phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election (TWS?)
17:05:29 <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:49 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
17:06:48 <colindixon> #info abhijitkumbhare wants to talk about openflowplugin staffing
17:07:17 <colindixon> #topic tsc mailing list discussion and votes
17:07:33 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47673#Agenda find them here
17:08:54 <colindixon> #info vishnoianil asks people to please chime in on those topics
17:08:58 <colindixon> #topic events
17:09:04 <colindixon> #link https://www.opendaylight.org/global-events
17:09:18 <colindixon> #info linuxcon japan is now in Tokyo
17:09:58 <colindixon> #info we are (for the first time) doing stuff around openstack days (both east on 8/23 and silicon valley 8/9)
17:10:15 <jamoluhrsen> phrobb: did tutorial schedule for ODL Summit get ironed out yet?
17:10:20 <colindixon> #info CFP for OpenStack  closed yesterday
17:10:51 <colindixon> #info CFP will be coming for OpenDayilght Forum India
17:10:54 <jamoluhrsen> thanks phrobb
17:11:02 <colindixon> #topic boron
17:11:39 <anipbu> #info The IETF Types Migration Effort has completed successfully with 35 patches merged, 1 patch pending (atrium), and two projects with pending issues (groupbasedpolicy and topoprocessing).
17:11:42 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-July/007280.html   <--- Email summarizing upgrade activity
17:11:48 <anipbu> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=778533050   <--- Tracking patch status
17:12:09 <anipbu> #info Discussion and concerns related to distribution size, with feedback needed from snmp4sdn, lispflowmapping, nemp, alto, capwap, usc, groupbasedpolicy, sfc, tsdr
17:12:19 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-July/007248.html   <--- Email thread for distribution size
17:12:38 <anipbu> #info Need feedback from projects regarding their documentation for Boron release: aaa, bgpcep, didm, faas, genius, natapp, nemo, neutron, next, nic, ovsdb, persistence, sdninterfaceapp, snbi, snmp4sdn, topoprocessing, usecplugin
17:12:45 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-July/007282.html   <--- Email thread for documentation patches
17:13:35 <anipbu> #info Reminder to Offset 0 projects that code freeze was two weeks ago and we are missing M5 Status from three projects: controller, infrautils, netconf
17:14:26 <abhijitkumbhare> https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-July/005492.html
17:15:07 <colindixon> #link https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-July/005492.html "Jozef Bacigal and Andrej Leitner will cease their work on OpenFlow project at the end of July 2016"
17:15:20 <colindixon> #info abhijitkumbhare mentions this as a risk—even for Boron
17:15:57 <colindixon> #info LuisGomez points out that these are the people who brought the new plugin in this release and know it best
17:16:15 <colindixon> #action colindixon to reach out to them about whether we could at least keep them through the Boron release
17:17:36 <colindixon> #info the July 21st meeting of OFP will be a bug scrub, so please come if you want to contribute or pick up bugs
17:19:10 <colindixon> #topic stable/beryllium
17:19:22 <anipbu> #info Autorelease Build is successful.  Reminder for projects that the cutoff is in one week and half on July 24 with a release on July 28.
17:19:38 <colindixon> #info cutoff is in 1.5 weeks for SR3
17:19:51 <colindixon> #topic system integration and test
17:20:18 <colindixon> #info all of the boron system test has been moot starting the last week b/c of distribution size, pay attention as we get it going again now
17:20:29 <colindixon> #action colindixon to follow up on distribution size issues
17:21:34 <colindixon> #info rovarga says unless they start pulling in more artifacts or more stuff, it should be fine for Boron (in that it stays under the 512 MB limit), but that's maybe still bad only because of size
17:22:03 <colindixon> #topic infrastructure
17:22:54 <colindixon> #Info there was an issue this morning where Jenkins was in shutdown mode (for reasons tykeal and zxiiro don't understand), when they fixed it, it cause a Jenkins reboot
17:23:17 <colindixon> #info they're investigating ways to move away from "matrix" jobs, which seem to be some source of problems
17:24:12 <colindixon> #info we've fixed our JJB so that we can more easily have per-project (and per-job) VM sizing, which should help some of the problems we saw in the migration to private cloud
17:25:02 <colindixon> #info as part of moving away from "matrix" jobs, we'll also be moving away from the maven job type in Jenkins (this will help because it hasn't been updated in >2 years, but will remove the blue bubble per "artifact" in maven jobs)
17:25:44 <colindixon> #info this will also speed things up by not archiving artifacts even if we tell them not to and avoiding storying md5sums of all artifacts (called fingerprints), which slows down the boot of Jenkins
17:26:24 <colindixon> #info Jenkins with no fingerprints takes about 2 minutes, took 10 minutes today, took 40 minutes before we migrated to the private cloud
17:26:42 <colindixon> #info zxiiro hopes that doing this will speed up builds and effectively giving us more resources
17:27:17 <colindixon> #info tykeal says, from his view, we're holding the line in the private cloud, but we are aware that we are somewhat more constrained than before
17:27:26 <zxiiro> #action zxiiro to create a thread outlining the planned JJB changes in infra
17:27:53 <colindixon> #info tykeal is hoping (with help from rackspace) to have a way for CSIT jobs to run in the public cloud, but he can't promise
17:29:02 <colindixon> #info tykeal says the current theory with Nexus issues is that it's the latency to Oregon from Rackspace, they're creating a replica of the authentication  in Rackspace to fix it, if not...
17:31:01 <colindixon> #info vishnoianil notes that we're expecting a lot more load as we move toward RCs, tykeal notes that's a bunch of the reason to look at the public cloud
17:32:24 <colindixon> #action vishnoianil and anipbu to work out if and how we can poll projects about how they're doing on their timelines and how that might impact the boron release and infrastructure issues
17:33:05 <colindixon> #topic committer promotions
17:33:23 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-July/005592.html Thanh Ha on Documentation
17:33:41 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/project:docs+owner:%22Thanh+Ha+%253Cthanh.ha%2540linuxfoundation.org%253E%22+status:merged+branch:master lots of merged commits
17:34:05 <colindixon> #info two +1s and no -1s in 8 days
17:34:43 <colindixon> #link http://docs.opendaylight.org/en/latest/ he's been instrumental in getting this up and working
17:34:52 <rovarga> #vote +1
17:34:52 <colindixon> #startvote shall the TSC approve Thanh Ha as a committer on docs? -1,0,+1
17:34:52 <odl_meetbot> Begin voting on: shall the TSC approve Thanh Ha as a committer on docs? Valid vote options are -1, 0, +1.
17:34:52 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:34:55 <rovarga> #vote +1
17:34:55 <abhijitkumbhare> #vote +1
17:34:56 <vishnoianil> #vote +1
17:34:57 <rovarga> :-)
17:34:58 <gkaempfer> #vote +1
17:35:00 <jamoluhrsen> #vote +1
17:35:01 <colindixon> #vote +1
17:35:02 <Chrisy> #vote +1
17:35:03 <mohnish__> #vote +1
17:35:04 <jamoluhrsen> no brainer :)
17:35:10 <Chrisy> totally no brainer
17:35:13 <colindixon> #endvote
17:35:13 <odl_meetbot> Voted on "shall the TSC approve Thanh Ha as a committer on docs?" Results are
17:35:13 <odl_meetbot> +1 (8): mohnish__, gkaempfer, Chrisy, jamoluhrsen, rovarga, colindixon, vishnoianil, abhijitkumbhare
17:35:27 <colindixon> #agree Thanh is a committer on docs
17:35:27 <vishnoianil> Congrates Thanh :)
17:35:31 <jamoluhrsen> congrats zxiiro
17:35:40 <abhijitkumbhare> yes - no brainer - that’s why  rovarga jumped the gun early :)
17:35:50 <abhijitkumbhare> Congrats zxiiro
17:36:03 <anipbu> Congrats zxiiro
17:36:30 <colindixon> #topic fast and/or phased release schedule in carbon
17:36:39 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005428.html discussion
17:37:33 <colindixon> #info colindixon asks if we need to draw a line in the sand to incorporate fast and/or phased into Carbon?
17:37:59 <colindixon> #info jamoluhrsen says it feels almost too late now, there's not enough discussion to safely put it in a plan
17:38:33 <colindixon> #Info vishnoianil points out that we need to run the pilot first and we likely can't reasonably do that before Carbon
17:39:21 <colindixon> #info mohnish__ agrees with vishnoianil, but asks if we know how much development time we have if we go with "fast" and have only 2 months
17:39:54 <colindixon> #info rovarga says that one thing that might help is if  you had experimental features, which need not be tracked as part of a given release as they're worked on across release
17:39:56 <colindixon> #undo
17:39:56 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x223dfd0>
17:39:58 <colindixon> #info rovarga says that one thing that might help is if  you had experimental features, which need not be tracked as part of a given release as they're worked on across releases
17:40:45 <colindixon> #info rovarga also notes that if people take 2-3 weeks off (which they do) during a 2-month release with only 6 weeks of coding, that can trash a release
17:41:29 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-July/005588.html this is the "pilot" vishnoianil referenced
17:42:06 <colindixon> #info the idea would be to do it sometime on the side during Carbon
17:44:22 <colindixon> #Info colindixon suggests maybe we should wait until edwarnicke comes back, but Chrisy notes he's out for 3 weeks
17:45:04 <colindixon> #info rovarga agrees that we don't really have any of the scripts and tooling around, and that we can't have any real hope of getting to it in Carbon
17:45:13 <colindixon> #info rovarga suggests having a hackfest during Carbon working on this
17:48:32 <colindixon> #startvote shall the TSC put together a 6-month release (like Boron) that will start shortly after Boron? -1,0,+1
17:48:32 <odl_meetbot> Begin voting on: shall the TSC put together a 6-month release (like Boron) that will start shortly after Boron? Valid vote options are -1, 0, +1.
17:48:32 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:49:29 <colindixon> #endvote
17:49:29 <odl_meetbot> Voted on "shall the TSC put together a 6-month release (like Boron) that will start shortly after Boron?" Results are
17:50:44 <colindixon> #info the consensus on the call (without edwarnicke) is that we really don't enough runway to make an drastic changes to the Carbon release, e.g., fast and/or phased
17:51:38 <colindixon> #info vishnoianil asks if we should have a parallel pilot with a few projects on a topic branch during carbon, colindixon thinks that's right
17:52:10 <colindixon> #info vishnoianil points out (and colindixon and phrobb agrees vehemently) that would give projects clarity that we will have a normal, 6-month release in Carbon, at the same time as giving us experience
17:53:43 <colindixon> #info phrobb suggests that as part of the Carbon release plan which projects would be part of the pilot and how they'd do it, e.g., topic branches
17:55:21 <colindixon> #action phrobb to put out a sample Carbon release plan based on Boron, which we could then iterate on
17:56:35 <colindixon> #action Chrisy to reach to to edwarnicke about fast and/phased carbon
17:57:52 <anipbu> would it be helpful to set a deadline when we want to make such a decision (not about the merits of either, but just to set a deadline)?
17:58:09 <colindixon> #action colindixon will try to get us to some clarity by next week's TSC call, not to rush things, but to make sure that we give projects clarity, especially new ones
17:59:04 <mohnish__> makes sense to me
18:02:12 <colindixon> shall the TSC commit to having the basic outline of the main Carbon release, e.g., approx length and milestones w/approx dates, by 7/28?
18:03:03 <colindixon> #startvote shall the TSC commit to having the basic outline of the main Carbon release, e.g., approx length and milestones w/approx dates, by 7/28? -1,0,+1
18:03:03 <odl_meetbot> Begin voting on: shall the TSC commit to having the basic outline of the main Carbon release, e.g., approx length and milestones w/approx dates, by 7/28? Valid vote options are -1, 0, +1.
18:03:03 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:03:13 <vishnoianil> #vote +1
18:03:14 <rovarga> #vote +1
18:03:14 <colindixon> #vote +1
18:03:15 <mohnish__> #vote +1
18:03:16 <jamoluhrsen> #vote +1
18:03:20 <Chrisy> #vote +1
18:03:20 <abhijitkumbhare> #vote +1
18:03:21 <gkaempfer> #vote +1
18:03:26 <colindixon> #endvote
18:03:26 <odl_meetbot> Voted on "shall the TSC commit to having the basic outline of the main Carbon release, e.g., approx length and milestones w/approx dates, by 7/28?" Results are
18:03:26 <odl_meetbot> +1 (8): mohnish__, gkaempfer, rovarga, Chrisy, colindixon, jamoluhrsen, vishnoianil, abhijitkumbhare
18:03:50 <colindixon> #agree the TSC commits to having the basic outline of the main Carbon release, e.g., approx length and milestones w/approx dates, by 7/28
18:04:16 <colindixon> #action colindixon to bring the commitment to a outline of a Carbon release plan up on the TSC mailing list
18:04:22 <colindixon> #topic cookies
18:04:31 <colindixon> #endmeeting