17:00:26 <colindixon> #startmeeting tsc
17:00:26 <odl_meetbot> Meeting started Thu Aug 11 17:00:26 2016 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:00:26 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:26 <odl_meetbot> The meeting name has been set to 'tsc'
17:00:30 <colindixon> #topic agenda bashing and roll call
17:00:32 <colindixon> #info colindixon
17:00:43 <gkaempfer> #info gkaempfer
17:00:58 <adetalhouet> #info adetalhouet
17:01:00 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=48328#Agenda the agenda in it's usual place
17:01:11 <ChrisPriceAB> #info Chris Price
17:01:13 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-08-04-17.00.html last week's meeting minutes
17:01:14 <vishnoianil> #info Anil Vishnoi
17:01:27 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-August/005810.html thread trying to start a fast and/or phased experience during Carbon (pull in skitt, rovarga, and edwarnicke)
17:01:38 <colindixon> #link https://lists.opendaylight.org/mailman/listinfo/tsc phrobb working on having a policy for how attendance to design forums works going forward with community involvement
17:01:51 <dfarrell07> #info Daniel Farrell
17:02:45 <colindixon> #info edwarnicke sent out his analysis out how to remove nodejs servers from people pulling in dlux to see if that helps
17:02:58 <colindixon> #link https://lists.opendaylight.org/pipermail/documentation/2016-August/000875.html the current process for updating what is searchable on the ODL wiki
17:03:04 <colindixon> #undo
17:03:04 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2246850>
17:03:05 <adetalhouet> oh about nodeJs is really about two project, SFC and GBP
17:03:20 <colindixon> #link https://lists.opendaylight.org/pipermail/documentation/2016-August/000875.html the current process for updating what is googleable (search engine indexed) on the ODL wiki
17:03:57 <colindixon> #action colindixon to document the wiki follow/nofollow somewhere https://lists.opendaylight.org/pipermail/documentation/2016-August/000875.html
17:04:07 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron/Carbon?
17:04:37 <colindixon> #action colindixon to try to drive some/all of the ongoing TSC discussions to completion
17:04:57 <abhijitkumbhare> #info abhijitkumbhare
17:05:24 <colindixon> #info colindixon sent out a poll to all committers, ptls, primary contacts in boron, and TSC members to vote on whether we should have an APAC-friendly TSC meeting occasionally
17:05:56 <colindixon> #action colindixon to e-mail out results of the APAC-time-zone poll
17:06:06 <colindixon> #action phrobb to add LinuxCon Europe to the events list
17:06:20 <vishnoianil> i don't see any mail yet about the vote
17:07:01 <colindixon> #action jamoluhrsen should add to the bug that we need to have the nexus file size limit set to 512 MB again
17:07:09 <anipbu> https://bugs.opendaylight.org/show_bug.cgi?id=6341
17:08:04 <mohnish__> #info Mohnish Anumala
17:08:12 <colindixon> #action colindixon and edwarnicke to try to work through the corner cases and process of the TSC elections
17:11:07 <colindixon> #topic TSC votes
17:11:11 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-August/005790.html GBP comitters
17:11:20 <colindixon> #topic events
17:11:27 <colindixon> #link https://www.opendaylight.org/global-events
17:11:32 <colindixon> #Info openstack SV just ended
17:11:54 <abhijitkumbhare> edwarnicke: u might want to +1 for both the committers in your email
17:12:12 <colindixon> #info comments from people on the ground were good and that lots of people and interest going by the booth, and in talks
17:12:48 <colindixon> #info there's a similar event OpenStack east, and OpenStack North america coming up
17:13:04 <colindixon> #info CFP for OpenDayligth forum india is closing, we have 30 submissions, that will be good
17:14:52 <colindixon> #topic boron
17:15:21 <anipbu> #info The Boron Autorelease job is failing due to issues in building ipv6service-impl.  Kindly request NETVIRT team to fix the issues
17:15:28 <anipbu> #link https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/211/org.opendaylight.netvirt$ipv6service-impl/   <--- Boron Autorelease failure in Netvirt
17:15:42 <anipbu> #info All projects in Boron have been added to the Boron Autorelease and Boron Distribution Feature Index.  Many thanks to releng, integration, project PTL for addressing the issues before RC0.
17:15:46 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-August/007843.html   <--- No projects missing from Autorelease or Distribution
17:15:51 <anipbu> #info We have resolved the ancient dependencies and third party with missing sources and the weather item will be closed.
17:15:55 <anipbu> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=2041395610   <--- Ancient dependencies and third party with missing sources
17:16:37 <anipbu> #info We are down to 418MiB with 1379 bundles for the Carbon distribution.  Many thanks to Stephen, Robert, Ed, and countless other folks who chipped in for this important effort.
17:16:41 <anipbu> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=1408329875   <--- Distribution size tracking
17:17:51 <adetalhouet> https://git.opendaylight.org/gerrit/#/c/43260/
17:18:15 <adetalhouet> cherry-pick: https://git.opendaylight.org/gerrit/#/c/43593/
17:19:47 <colindixon> #info colindixon notes that we're still 50% bigger than we were in Beryllium-SR3 (285 MB vs. ~418 MB)
17:21:01 <colindixon> #info edwarnicke notes that the way the UI elements were being handled changed a lot from Be to B, and we're working on it
17:21:21 <colindixon> #Info rovarga has identified about 50 MB of duplicate versions, we might be able to hunt it down
17:22:25 <colindixon> #info colindixon says thanks so much for all the hard work to get this to the point where our tests are working again
17:22:41 <colindixon> #info colindixon says he doesn't think further reduction (even though it would be really good) should be considered a blocker for Boron
17:22:56 <anipbu> #info We have completed the upgrade from Karaf 3.0.6 to Karaf 3.0.7 and the patch has been merged in odlparent and the weather item will be closed.
17:22:56 <colindixon> #info nobody seems to object to that
17:23:02 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/40818/   <--- Patch for Karaf 3.0.7 Upgrade
17:23:22 <anipbu> #info We will be automatically migrating project documentation from AsciiDoc to reStructuredText in Boron for the User Guide and Developer Guide.  Request folks to review the plan of action and provide feedback such as opting out, etc.
17:23:27 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-August/007832.html   <--- Boron reStructuredText Migration Plan of Action
17:24:03 <anipbu> #info There are plan to merge changes to the OpenFlowPlugin NSH API to Support new matches and actions in ovs nsh patch with impact to openflowplugin, sfc, netvirt, gbp
17:24:07 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/37937/   <--- Patch for Openflow plugin NSH API changes
17:24:11 <anipbu> #link https://lists.opendaylight.org/pipermail/groupbasedpolicy-dev/2016-July/003481.html   <--- API Waiver Request for Openflow plugin NSH API changes
17:24:31 <anipbu> #info There are plans merge changes to the OpenFlowPlugin for Adding learn action with impact to netvirt, genius
17:24:34 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/42702/   <--- Patch for OpenFlowPlugin Add Learn Action
17:24:38 <anipbu> #link https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-August/005714.html   <--- API Waiver Request for OpenFlowPlugin Add Learn Action
17:25:12 <anipbu> #info There are planned changes in the yangtools api related to BitsTypeDefinition, EnumTypeDefinition, DataNodeContainer, yang-model-api with impact to controller, mdsal and netconf
17:25:17 <anipbu> #link https://wiki.opendaylight.org/view/Weather#Minor_change_of_BitsTypeDefinition_and_EnumTypeDefinition_API_in_Yangtools   <--- Weather Item for Yangtools changes
17:25:21 <anipbu> #link https://wiki.opendaylight.org/view/Weather#Change_of_yang-model-api_in_yangtools   <--- Weather item for yang-model-api changes
17:25:25 <anipbu> #link https://git.opendaylight.org/gerrit/#/q/topic:getDataChildByName   <--- Patches for impacted projects
17:26:07 <anipbu> #info We have modified the Restconf Response.  Before, when creating new resource with PUT method, status code 200 OK is returned.  After, if the PUT method creates a new resource, a "201 Created" Status-Line is returned.
17:26:32 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/40235/   <--- Patch for Restconf Response Changes
17:26:34 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-August/007799.html   <--- Email Thread discussing Restconf Response Changes
17:26:39 <anipbu> #link https://wiki.opendaylight.org/view/Weather#Added_return_code_201_for_PUT_method_in_RESTconf   <--- Weather Item tracking Restconf Response Changes
17:33:43 <colindixon> #info adetalhouet points out that this is basically a bug fix, fixing it internally should be manageable, the real issues is for external apps, but this will only change in a major release, where we can release note it
17:34:16 <colindixon> #action anipbu to make sure we release note the change in HTTP RESTCONF REPONSE codes
17:36:02 <colindixon> #action tcere to send a mail about what changed with HTTP response codes, so we can communicate it well
17:36:38 <colindixon> #Info the agreement seems to be that the change is valid and since it's happening in a major release, we should probably stick with it unless it's going to cause massive amounts of new testing effort in fixing our tests
17:37:11 <colindixon> #action colindixon to talk to LuisGomez and jamo to make sure we know what we're getting into
17:37:45 <colindixon> #info vrpolak points out that we're now accepting 2xx for the tests, which means we can revert without causing issues if need be
17:38:13 <anipbu> #info The build for RC0 will start at 23:59:59 UTC on 8/11/2016
17:38:22 <anipbu> #info We conducted an informal poll of project readiness and health check for Boron.
17:38:27 <anipbu> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=199721620   <--- Informal Poll on Project Readiness
17:42:03 <zxiiro> what about netide? they haven't fixed the compile issue yet so I don't think we can build RC0
17:42:23 <colindixon> #info colindixon notes that the major changes coming are either bugfixes (openflowplugin) or leaf projects, with the exception of yangtools
17:42:38 <anipbu> https://git.opendaylight.org/gerrit/#/c/42863/
17:42:56 <anipbu> https://lists.opendaylight.org/pipermail/netide-dev/2016-August/000102.html
17:43:23 <colindixon> #info colindixon thus feels like we're actually in pretty good shape about the RC0 build, assuming yangtools doesn't blow up
17:44:25 <colindixon> #info colindixon says that we've historically had no rules about what goes in after RCs, we've allowed non-blocker bugs and even API changes in the past
17:44:42 <colindixon> #info edwarnicke and colindixon say that we should strongly discourage churn for non-blocking issues, but not stop it
17:45:34 <colindixon> #action colindixon to send a mail to have discussion about if we should say blocking bug fixes only during RCs in carbon
17:46:21 <colindixon> #topic system integration and test, stable/beryllium, carbon
17:46:23 <colindixon> #info nothing here
17:46:29 <colindixon> #topic infrastructure
17:46:54 <colindixon> #info we are still seeing nexus timeouts, we don't have a guess as to what the problem is or how to debug it
17:47:16 <colindixon> #info tykeal is asking the rest of the LF sysadmin team about how to go debug it
17:48:52 <colindixon> #info there were issues with docker images in the public cloud, those seem to be fixed
17:49:13 <colindixon> #info it's not taking 6 minutes to get an ssh connection vs. less than 5 in the past
17:49:39 <zxiiro> #info validate-autorelease jobs replaced with freestyle ones and runs in 5 minutes instead of 10-15
17:49:53 <colindixon> thanks!
17:51:01 <colindixon> #topic archiving toolkit
17:51:11 <colindixon> #link https://wiki.opendaylight.org/view/Archive_Proposals/OpenDaylight_Toolkit
17:52:03 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-July/005646.html
17:52:29 <colindixon> #info of the 4 commiters, 2 voted +0, and one voted +1
17:52:58 <dfarrell07> Let's archive it
17:53:00 <colindixon> #startvote shall the TSC archive the toolkit project? -1,0,+1
17:53:00 <odl_meetbot> Begin voting on: shall the TSC archive the toolkit project? Valid vote options are -1, 0, +1.
17:53:00 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:53:08 <dfarrell07> #vote +1
17:53:08 <adetalhouet> #vote +1
17:53:09 <vishnoianil> #vote +1
17:53:10 <ChrisPriceAB> #vote +1
17:53:17 <mohnish__> #vote +1
17:53:17 <gkaempfer> #vote +1
17:53:19 <edwarnicke> #vote +1
17:53:19 <abhijitkumbhare> #vote +1
17:53:32 <colindixon> #vote +1
17:53:41 <colindixon> #chair anipbu phrobb
17:53:41 <odl_meetbot> Current chairs: anipbu colindixon phrobb
17:53:45 <colindixon> #endvote
17:53:45 <odl_meetbot> Voted on "shall the TSC archive the toolkit project?" Results are
17:53:45 <odl_meetbot> +1 (9): mohnish__, gkaempfer, adetalhouet, dfarrell07, ChrisPriceAB, edwarnicke, colindixon, abhijitkumbhare, vishnoianil
17:53:53 <colindixon> #agreed toolkit is archived
17:53:58 <dfarrell07> colindixon: you're doing great, running blind ;)
17:54:04 <vishnoianil> dfarrell07, :D
17:54:10 <colindixon> #action colindixon to add the relevant bits on the wiki to archive toolkit
17:54:14 <colindixon> #topic TSC elections
17:55:43 <colindixon> #Info dfarrell07 says we have four things to do: (1) agree on the frequency of elctions, (2) dealing with issue of people representing multiple groups or projects within a group, (3) edwarnicke and colindixon auditing the stuff, (4) voting on represented groups
17:55:54 <colindixon> #info dfarrell07 suggests that we vote on yearly frequency
17:56:19 <colindixon> #startvote shall the TSC agree on a yearly frequency of TSC elections going forward? -1,0,+1
17:56:19 <odl_meetbot> Begin voting on: shall the TSC agree on a yearly frequency of TSC elections going forward? Valid vote options are -1, 0, +1.
17:56:19 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:56:26 <dfarrell07> #vote +1
17:56:27 <colindixon> #vote +1
17:56:27 <edwarnicke> #vote +1
17:56:31 <adetalhouet> #vote +1
17:56:35 <vishnoianil> #vote +1
17:56:36 <abhijitkumbhare> #vote +1
17:56:42 <mohnish__> #vote +1
17:56:54 <uri> #vote +1
17:56:54 <ChrisPriceAB> #vote +1
17:56:56 <gkaempfer> #vote +1
17:57:06 <colindixon> #endvote
17:57:06 <odl_meetbot> Voted on "shall the TSC agree on a yearly frequency of TSC elections going forward?" Results are
17:57:06 <odl_meetbot> +1 (10): mohnish__, gkaempfer, adetalhouet, ChrisPriceAB, uri, dfarrell07, edwarnicke, colindixon, abhijitkumbhare, vishnoianil
17:57:08 <dfarrell07> #link https://wiki.opendaylight.org/view/TSC:Election_Proposal Framework proposal
17:57:16 <uri> do we want to tie it to release schedule at all?
17:57:18 <colindixon> #agreed future TSC elections will have a 1-year term
17:57:30 <edwarnicke> uri: I think the consensus is not to tie to release schedule
17:57:39 <uri> heard the concern about people delaying the realease, i don't see this as a real issue
17:57:47 <uri> ok
17:57:55 <colindixon> #info phrobb notes that we wanted to kick this election off immediately after Boron, so in a 2-3 week time frame, so make this a priority
17:58:11 <dfarrell07> uri: yeah, not a real issue imho, but if we moved to 2m releases that would be bad for TSC elections
17:58:30 <colindixon> #action everyone to review the other bits of the TSC elections, most noably the the represeting multiple groups or projects and picking represetned groups
17:58:33 <edwarnicke> dfarrell07: LOL... in spades, I don't think anyone wants to do elections that frequently ;)
17:58:43 <dfarrell07> edwarnicke: lol big +1 ;)
18:00:03 <colindixon> #info abhijitkumbhare asks if we have to elect PTLs first, colindixon points that we don't mandate when PTLs are elected, committers can call for it whenever has been how it's happening in the past
18:00:35 <colindixon> #action phrobb to send a mail to projects to note that who the PTL is at the end of boron has implications for the TSC election, so figured it out if you have to
18:00:44 <colindixon> #topic cookies
18:00:51 <colindixon> #endmeeting