17:00:48 #startmeeting tsc 17:00:48 Meeting started Thu Oct 20 17:00:48 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:48 The meeting name has been set to 'tsc' 17:00:51 #topic agenda bashing and roll call 17:00:58 #info abhijitkumbhare 17:00:58 #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-10-13-17.01.html last week's meeting minutes 17:00:58 #info Anil Vishnoi 17:00:59 #info Daniel Farrell 17:01:17 #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=51162#Agenda the agenda in it's usual place 17:01:20 #info colindixon 17:01:25 TSC members, please #info in 17:01:41 #info Stephen Kitt standing in for Alexis de Talhouƫt 17:01:48 #action colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way 17:01:50 #info Chris Price 17:01:55 #action colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs 17:02:00 #action dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion 17:02:33 #action phrobb to get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/ 17:02:37 * ChrisPriceAB wonders what "impolite" might look like :P 17:02:44 :) 17:03:11 #action phrobb to work on getting us bettter control of the events page to make his life less painful 17:03:19 #action phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better 17:04:55 #info gkaempfer 17:05:14 #action colindixon to add the agenda topic that networking-odl seems like it will be kicked out of ocata unless we improve our results on a scorecard 17:05:25 #info rovarga for jmedved 17:06:39 #info scorecard for networking-odl recently done by Newtron team: https://review.openstack.org/#/c/383910/6/specs/stadium/ocata/networking-odl.rst 17:07:00 #link https://review.openstack.org/#/c/383910/ the review for networking-odl in ocata 17:08:02 #Info isaku says he things the major issue is the peception is that we are closer to a vendor driver than a "stadium" driver 17:09:11 #info isaku says that the general feeling is that the opendaylight community is not cooperative with the neutron community, edwarnicke asks how and isaku answers basically in that we stay inside our own boundaries and don't participate more broadly 17:10:38 #action colindixon start a thread on networking ODL in ocata on the neutron-dev list: https://review.openstack.org/#/c/383910/6/specs/stadium/ocata/networking-odl.rst 17:11:41 #info ChrisPriceAB looked a how OpenDaylight and OPNFV will line up for the next release 17:12:18 #info it looks like OPNFV releases at the same time that we have code freeze, which will obviously have issues 17:14:43 #ino ChrisPriceAB asks the TSC if there are ideas about how to get the projects that cross OPNFV/ODL over to OPNFV in a way that works 17:14:47 #info ChrisPriceAB asks the TSC if there are ideas about how to get the projects that cross OPNFV/ODL over to OPNFV in a way that works 17:15:08 #unfo Ed hates branches!!! 17:16:42 * ChrisPriceAB can be safely actioned to take this to the list. 17:16:43 #action ChrisPriceAB to open a maling list thread on release@ and tsc@ to talk about how to help projects that cross ODL/OPNFV deliver on promises in both places at the same time 17:18:19 #info tykeal says that pre-boron branches were a bit of a pain, and nobody used it, which this would effectively be similar 17:19:37 #info dfarrell07 says that what OPNFV really needs is builds with semi-stable patches released regularly with known issues, making sure autorelease runs wihtout failures more regularly would be huge 17:20:03 * ChrisPriceAB hears the music ... +1 dfarrell07 & edwarnicke 17:20:06 #Info edwarnicke gives a pitch for dfarrell07's work on a continuous pipeline from OpenDaylight to OPNFV (and other downstreams) being expanded 17:21:02 #topic events 17:21:10 #link https://www.opendaylight.org/global-events 17:21:10 #info fd.io already has continuous pipelines to OpNFV, and edwarnicke is more than happy to share lessons learned ;) 17:21:55 #info openstack in barcelona next week, there is a ODL/OPNFV reception as part of that on Tuesday night, you should receive info soon if you haven't already 17:22:07 #info india forum coming up november 16th 17:22:16 #Info MEF coming up 16 on 11/7 17:22:22 #undo 17:22:22 Removing item from minutes: 17:22:27 #Info MEF 16 coming up on 11/7 17:22:30 #link https://www.surveymonkey.com/r/RZKD83B OPNFV / ODL reception link 17:22:40 #info OPNFV plugfest on 12/6-12/9 17:22:54 #topic boron 17:22:56 #chair phrobb anipbu 17:22:56 Current chairs: anipbu colindixon phrobb 17:23:08 #info Boron-SR1 is next week on October 27 with a cutoff this Sunday on 10/23 23:59 UTC. 17:23:12 #info The Boron Autorelease job is passing. 17:23:20 #link https://git.opendaylight.org/gerrit/#/q/status:open+branch:stable/boron <--- 33 patches pending for stable/boron 17:23:37 #link https://bugs.opendaylight.org/buglist.cgi?bug_severity=blocker&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=WAITING_FOR_REVIEW&f1=cf_target_milestone&f2=cf_target_milestone&j_top=OR&list_id=67733&o1=substring&o2=substring&query_format=advanced&resolution=---&v1=Boron&v2=--- <--- Two blocker bugs in openflowplugin 17:23:37 (6575, 6917) and l2switch (6956), for Boron. Kindly ask projects to please fix or retarget blocker bugs before the cutoff. 17:24:01 #link https://git.opendaylight.org/gerrit/#/dashboard/?title=Boron+Status&Yang+File+Changes+Since+Boron=branch:stable/boron+status:merged+file:%22%255E.%252Byang%22+after:2016-09-15 <--- 34 patches modifying yang files without API Freeze Waiver between Boron Release and Boron SR1 17:24:47 #topic beryllium 17:24:53 #info Beryllium SR4 Build 20161019 is ready to be presented to the TSC for approval. Blocking bugs have been resolved and test issues have been signed off as OKAY. 17:25:10 #link https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR4/Status <--- Status Page 17:25:17 #link https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1820514274 <--- All projects with test issues have signed off as OKAY to release 17:25:18 #link https://lists.opendaylight.org/pipermail/tsc/2016-October/006169.html thread from anipbu saying we're good to go 17:25:48 #starvote shall the TSC release Beryllium-SR4 based on the 20161019 build? -1,0,+1 17:25:52 #startvote shall the TSC release Beryllium-SR4 based on the 20161019 build? -1,0,+1 17:25:52 Begin voting on: shall the TSC release Beryllium-SR4 based on the 20161019 build? Valid vote options are -1, 0, +1. 17:25:52 Vote using '#vote OPTION'. Only your last vote counts. 17:25:54 #vote +1 17:25:55 #vote +1 17:25:55 #vote +1 17:25:56 #vote +1 17:25:56 #vote +1 17:25:56 #vote +1 17:25:59 #vote +1 17:25:59 #vote +1 17:26:04 starvote == make the vote shiny? 17:26:05 #vote +1 17:26:13 #endvote 17:26:13 Voted on "shall the TSC release Beryllium-SR4 based on the 20161019 build?" Results are 17:26:13 +1 (9): gkaempfer, rovarga, ChrisPriceAB, skitt, edwarnicke, dfarrell07, colindixon, abhijitkumbhare, vishnoianil 17:26:15 glimmering 17:26:26 #agreed Beryllium-SR4 based on build 20161019 is released! 17:26:31 w00t last Be 17:26:31 tykeal: it is vote by the stars :) 17:27:29 #info that is the last scheduled release of Beryllium, we will publish security updates until carbon is released 17:27:49 #info zxiiro says the release might happen later today rather than immediately after the TSC call as normal 17:27:58 #topic carbon 17:28:05 #link https://lists.opendaylight.org/pipermail/release/2016-October/008490.html <--- We had Carbon Autorelease Failures in infrautils but it was fixed in https://git.opendaylight.org/gerrit/#/c/47059/ 17:28:11 #link https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-carbon/34/ <--- Autorelease Build Failures in DLUX - DLUX Static Web. 17:28:45 #link https://git.opendaylight.org/gerrit/#/c/47001/ <--- SFC project changing module artifact versions in maven and remove incorrect parent versions with potential impact to cardinal, faas, groupbasedpolicy, netvirt, nic. 17:29:08 #link https://lists.opendaylight.org/pipermail/release/2016-October/008491.html <--- Carbon M1 Offset 0 Status is due on today 10/20 17:29:20 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan <--- Kindly request TSC to formally approve the Carbon Simultaneous Release 17:30:51 * ChrisPriceAB is an anarchist at heart... 17:31:00 * edwarnicke is with ChrisPriceAB 17:31:05 #startvote shall the TSC approve the Carbon Release Plan as it stands here: https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan ? -1,0,+1 17:31:05 Begin voting on: shall the TSC approve the Carbon Release Plan as it stands here: https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan ? Valid vote options are -1, 0, +1. 17:31:05 Vote using '#vote OPTION'. Only your last vote counts. 17:31:17 #vote +1 17:31:18 #vote +1 17:31:19 #vote +1 17:31:19 #vote +1 17:31:21 #vote +1 17:31:21 #vote +1 17:31:22 #vote +1 17:31:30 #vote +1 17:31:35 #endvote 17:31:35 Voted on "shall the TSC approve the Carbon Release Plan as it stands here: https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan ?" Results are 17:31:35 +1 (8): rovarga, skitt, ChrisPriceAB, dfarrell07, edwarnicke, colindixon, abhijitkumbhare, vishnoianil 17:31:48 #agreed the carbon release plan as it stands here is formally approved: https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan 17:32:00 that was easy ;) 17:32:18 #info colindixon strongly encourages relevant projects to work to include fast and/or phased elements into their per-project release plans where appropirate and staffable 17:33:13 #topic infra 17:33:37 #info rackspace did finish expanding our cloud for us (last week), we haven't expanded the quota on anything to use the new resources 17:33:45 #info tykeal is planning to build out odlforge there now 17:34:32 #info we may have to have some outages to roll out a kernel security update at some point 17:34:41 tykeal: if you want an example project to move into ODL Forge, Int/Pack volunteers the ansible-opendaylight and puppet-opendaylight repos 17:35:23 #info we will be updating main nexus and jenkins/gerrit sandbox this weekend (small outges) 17:35:42 #info there are some issues with jenkins/gerrit integration based on the gerrit ssh API changing 17:36:14 Counterexample: https://git.opendaylight.org/gerrit/47210 17:37:00 #info committers have the ability to remove jenkins as a reviewer to remove a -1 verify from it, then after that jenkins won't be able to post to gerrit in the new version (one unresolve edge case with no workaround) 17:37:23 vrpolak: I think that's because we haven't updated yet 17:38:23 #link https://git.opendaylight.org/gerrit/46975 Integration-distro-test trigger fix 17:38:38 #link https://git.opendaylight.org/gerrit/47139 distro-check patch for 60 minute timeout 17:39:18 #link https://git.opendaylight.org/gerrit/47151 renaming console log name in logs server 17:40:05 #info the last thing makes everything but the domain part the same for logs and jenkins servers 17:40:30 #topic Claudio Gasparini on BGPCEP 17:40:37 #uno 17:40:39 #Undo 17:40:39 Removing item from minutes: 17:40:43 #topic Claudio Gasparini as a committer on BGPCEP 17:40:47 #link https://lists.opendaylight.org/pipermail/tsc/2016-October/006150.html 17:40:58 #link https://lists.opendaylight.org/pipermail/bgpcep-dev/2016-October/000796.html 3 of 5 current committers +1 17:41:07 #link https://git.opendaylight.org/gerrit/#/q/owner:cgaspari%2540cisco.com+status:merged+project:bgpcep lots of patches 17:41:23 #startvote shall the TSC approve Claudio Gasparini as a committer on BGPCEP? -1,0,+1 17:41:23 Begin voting on: shall the TSC approve Claudio Gasparini as a committer on BGPCEP? Valid vote options are -1, 0, +1. 17:41:23 Vote using '#vote OPTION'. Only your last vote counts. 17:41:31 #vote +1 17:41:33 #vote +1 17:41:33 #vote +1 17:41:34 #vote +1 17:41:35 #vote +1 17:41:52 #vote +1 17:41:56 #vote +1 17:42:03 #vote +1 17:42:06 #vote +1 17:42:29 #endvote 17:42:29 Voted on "shall the TSC approve Claudio Gasparini as a committer on BGPCEP?" Results are 17:42:29 +1 (9): gkaempfer, rovarga, ChrisPriceAB, skitt, edwarnicke, dfarrell07, colindixon, abhijitkumbhare, vishnoianil 17:42:44 #agreed Claudio Gasparini is a committer on BGPCEP 17:42:47 #topic Jakub Morvay as a committer on NETCONF 17:42:48 #link https://lists.opendaylight.org/pipermail/tsc/2016-October/006165.html 17:42:49 #link https://lists.opendaylight.org/pipermail/netconf-dev/2016-October/000699.html 2 of 3 current committers +1 17:42:50 #link https://git.opendaylight.org/gerrit/#/q/owner:jmorvay%2540cisco.com+project:netconf lots of patches 17:42:51 #startvote shall the TSC approve #topic Jakub Morvay as a committer on NETCONF 17:42:51 Unable to parse vote topic and options. 17:43:02 #startvote shall the TSC approve #topic Jakub Morvay as a committer on NETCONF? -1,0,+1 17:43:02 Begin voting on: shall the TSC approve #topic Jakub Morvay as a committer on NETCONF? Valid vote options are -1, 0, +1. 17:43:02 Vote using '#vote OPTION'. Only your last vote counts. 17:43:15 #vote +1 17:43:17 #vote +1 17:43:18 #vote +1 17:43:18 #vote +1 17:43:19 #vote +1 17:43:19 #vote +1 17:43:20 #vote +1 17:43:20 #vote +1 17:43:25 #endvote 17:43:25 Voted on "shall the TSC approve #topic Jakub Morvay as a committer on NETCONF?" Results are 17:43:25 +1 (8): rovarga, ChrisPriceAB, skitt, dfarrell07, edwarnicke, colindixon, abhijitkumbhare, vishnoianil 17:43:43 #agreed Jakub Morvay is a committer on NETCONF 17:43:55 #topic ODL Parent Graduation Review 17:44:05 #link https://wiki.opendaylight.org/view/ODL_Root_Parent:Mature_Graduation_Proposal 17:44:14 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-October/000538.html requested on 10/6/2016 17:45:17 #info dfarrell07 thanks skitt for doing this so that odlparent can be mature and thus have stable features, so other projects can have stable features 17:45:24 #info skitt adds that's what prompted this 17:45:37 #info with colindixon's help 17:45:42 #startvote shall the TSC graduate odlparent to being a mature project? -1,0,+1 17:45:42 Begin voting on: shall the TSC graduate odlparent to being a mature project? Valid vote options are -1, 0, +1. 17:45:42 Vote using '#vote OPTION'. Only your last vote counts. 17:45:43 #vote +1 17:45:44 #vote +1 17:45:45 #vote +1 17:45:45 #vote +1 17:45:46 #vote +1 17:45:46 #vote +1 17:45:47 #vote +1 17:45:47 #vote +1 17:45:53 #endvote 17:45:53 Voted on "shall the TSC graduate odlparent to being a mature project?" Results are 17:45:53 +1 (8): dfarrell07, gkaempfer, rovarga, edwarnicke, ChrisPriceAB, colindixon, abhijitkumbhare, vishnoianil 17:46:05 #agreed odlparent is a mature project 17:46:12 #action skitt to update the wiki 17:46:28 congrats skitt and odlparent team! 17:46:29 #undo 17:46:29 Removing item from minutes: 17:46:32 thanks! 17:46:36 #action skitt to update the wiki with odlparent being mature 17:47:05 congrats skitt! 17:47:13 #topic TSC elections 17:47:28 congrats skitt 17:48:05 #info last week the TSC agreed to open the nominations, and about the dates, as well as when people need to have their things done to participate 17:48:39 #info phrobb didn't start the nomination process last week as was agreed 17:48:57 #info in essence, we have two choices, (a) assume that things are OK with a 1-week nomination period, or (b) push the elections out a week 17:50:19 #info rovarga notes that we have no self-nominations, which points to maybe people haven't been paying attention, colindixon notes that things tend to happen at the end, so that wouldn't have pointed 17:51:02 is it clear that the people who are eligible know they are eligible to run? 17:51:06 #startvote shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same? 1,1 17:51:06 Begin voting on: shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same? Valid vote options are 1, 1. 17:51:06 Vote using '#vote OPTION'. Only your last vote counts. 17:51:14 #endvote 17:51:14 Voted on "shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same?" Results are 17:51:18 #startvote shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same? 1,2 17:51:18 Begin voting on: shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same? Valid vote options are 1, 2. 17:51:18 Vote using '#vote OPTION'. Only your last vote counts. 17:51:29 #vote 2 17:51:30 #vote 2 17:51:33 #vote 2 17:51:36 #vote 2 17:51:48 #vote 2 17:51:49 push them out 17:51:52 #vote 2 17:51:58 #vote 2 17:51:59 #vote 2 17:52:10 #endvote 17:52:10 Voted on "shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same?" Results are 17:52:10 2 (8): rovarga, ChrisPriceAB, skitt, edwarnicke, dfarrell07, colindixon, abhijitkumbhare, vishnoianil 17:52:23 every vote glimmers like a little star? 17:52:31 * ChrisPriceAB wonders what happens if a vote is wasted... 17:52:33 #agreed we will move the dates for the TSC election out a week to accomodate the fact that the call for self-nomination didn't go out last week 17:52:46 colin gets irate? 17:53:44 did any one hear me, just 5 minutes back ? just wondering if my audio is not working :) 17:54:04 #action phrobb will send mail to all people who are eligible to run that they are eligible as well as asking for self-nomination 17:54:36 #undo 17:54:36 Removing item from minutes: 17:55:18 #action phrobb will send mail to all people who are eligible to run that they are eligible as well as asking for self-nomination, dfarrell07 adds that we should use this opportunity to encourage people to get the categorizatoin right, clean up committer lists and hold PTL elections if need be (either new ones or first ones in the case of 6-8 projects) 17:55:35 #Info dfarrell07 says that they way that works is that projects without PTLs wouldn't get votes 17:56:56 #Info abhijitkumbhare asks if we should have a google sheet to track PTLs, categorization, (and maybe committers) to make gathering information easier 17:57:03 #link https://wiki.opendaylight.org/view/Project_list#Project_Types Wiki with projects sorted by types into RGs 17:58:12 #action colindixon to change the project facts template to include a type field and then auto-populate lists based on that information 17:59:00 #info phrobb says that his plan was to let self-nominees declare their group when they fill this out here: https://wiki.opendaylight.org/view/TSC:2016_Election (which does part of the categorization) 17:59:26 #info in the next two weeks, we get all of the projects put in a the right types to make voters (not nominees correct) 17:59:48 #inf the intented project type was reported in M0 status, we got responses from a lot, but not all projects for that 17:59:51 #info the intented project type was reported in M0 status, we got responses from a lot, but not all projects for that 18:00:22 #action anipbu to verify the project types match the M0 reports: https://wiki.opendaylight.org/view/Project_list#Project_Types 18:00:37 #topic cookies 18:00:46 #endvote 18:00:52 #endmeeting