17:01:01 <colindixon> #startmeeting tsc
17:01:01 <odl_meetbot> Meeting started Thu Oct 13 17:01:01 2016 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:01:01 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:01 <odl_meetbot> The meeting name has been set to 'tsc'
17:01:06 <colindixon> #topic agenda bashing and roll call
17:01:09 <rovarga> #info rovarga for jmedved
17:01:10 <colindixon> TSC members please #info in
17:01:15 <rovarga> #info rovarga for jmedved
17:01:20 <rovarga> (too fast :-P)
17:01:24 <Prem_> #info Prem_ for Chris Price
17:01:26 <colindixon> #info colindixon
17:01:30 <adetalhouet> #info adetalhouet
17:01:41 <colindixon> #Link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=50953#Agenda the agenda in it's usual place
17:01:51 <abhijitkumbhare> #info abhijitkumbhare
17:01:54 <colindixon> https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-10-13-17.01.log.txt
17:02:24 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc_meeting_oct_6__2016/opendaylight-meeting-tsc_meeting_oct_6__2016.2016-10-06-17.02.html last week's meeting minutes
17:02:59 <colindixon> #link colindixon started a thread on when you need to be a committer/PTL/project to participate in the elections
17:03:04 <colindixon> #undo
17:03:04 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2aeee50>
17:03:11 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-October/006124.html colindixon started a thread on when you need to be a committer/PTL/project to participate in the elections
17:03:34 <vishnoianil> #info Anil Vishnoi
17:03:43 <colindixon> #info LuisGomez, colindixon, jamoluhrsen, phrobb, and tykeal have talked about where to put CSIT for Carbon, it looks like we'll try to migrate to the second availability zone as we build it out
17:04:03 <colindixon> #action colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
17:04:24 <colindixon> #action colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs
17:04:40 <edwarnicke> #info edwarnicke
17:04:43 <colindixon> #action dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
17:05:11 <colindixon> #info rovarga says that we do have a jenkins log analyzer plugin, it's just a matter of extending it
17:06:08 <rovarga> #link https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer is what we have deployed, we need to populate its knowledge base
17:06:10 <colindixon> #action rovarga to send details about the jenkins log analyzer plugin
17:06:14 <colindixon> #undo
17:06:14 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x2b25650>
17:06:59 <colindixon> #action phrobb to get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/
17:07:26 <colindixon> #action phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
17:08:00 <jamoluhrsen> #info jamoluhrsen
17:08:41 <colindixon> #topic TSC mailing list votes and discussions
17:08:51 <colindixon> #Info we have the above mentioned when things have to happen to participate in elections
17:09:01 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-October/006101.html  Future Summit structure suggestions/feedback
17:09:11 <colindixon> #Info it seems like the developer community would really like an extra day
17:10:19 <colindixon> #info phrobb says he'll make it work to have an extra day if it makes sense and we'll try to keep it within costs
17:11:33 <colindixon> #info abhijitkumbhare asks if we could just move the last day of the DDF to a company site given that we'll be in the south bay anyway
17:11:51 <colindixon> #topic events
17:11:52 <colindixon> #link https://www.opendaylight.org/global-events
17:12:11 <colindixon> #Info OpenStack summit in Barcelona is on 10/24
17:12:23 <colindixon> #info OpenDaylight India Forum on 11/16
17:12:38 <colindixon> #info CaseyODL and phrobb are looking for demos for the booth at OpenStack, please reach out
17:12:53 <colindixon> #topic boron
17:13:03 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-October/008419.html   <--- The Boron Autorelease job failed to build vbd modules.  A patch fixing the issues have been merged.
17:13:08 <colindixon> #chair phrobb anipbu
17:13:08 <odl_meetbot> Current chairs: anipbu colindixon phrobb
17:13:19 <anipbu> #info Boron-SR1 is in two weeks on October 27 with a cutoff on 10/23 23:59 UTC.
17:13:35 <anipbu> #link https://git.opendaylight.org/gerrit/#/q/status:open+branch:stable/boron   <--- 29 patches pending for stable/boron
17:13:55 <anipbu> #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:13:55 <anipbu> (6917, 6575) for Boron.  Kindly ask projects to please fix or retarget blocker bugs before the cutoff.
17:14:21 <anipbu> #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   <--- 27 patches modifying yang files without API Freeze Waiver between Boron Release and Boron SR1
17:15:38 <abhijitkumbhare> #info Bug 6575 is fixed (depends on bug 6710 in mdsal)
17:15:51 <colindixon> #info colindixon notes that YANG file changes in SRs are problematic if not done in backward compatible ways for users
17:16:33 <colindixon> #topic stable/beryllium
17:16:42 <anipbu> #info Beryllium-SR4 is in one week on October 20 with a cutoff this Sunday at 10/16 23:59 UTC.
17:16:49 <anipbu> #link https://git.opendaylight.org/gerrit/#/q/status:open+branch:stable/beryllium   <--- 63 patches pending for stable/beryllium
17:16:56 <anipbu> #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=Beryllium&v2=---   <--- Zero blocker bugs targeted for
17:16:56 <anipbu> Beryllium.  Kindly ask projects to please raise blocker bugs if any identified for tracking purposes.
17:17:16 <anipbu> #link https://git.opendaylight.org/gerrit/#/dashboard/?title=Beryllium+Status&Yang+File+Changes+Since+Beryllium+SR3=branch:stable/beryllium+status:merged+file:%22%255E.%252Byang%22+after:2016-07-28   <--- 10 patches modifying yang files without API Freeze Waiver between Beryllium SR3 and Beryllium SR4
17:18:44 <colindixon> #info colindixon notes that SR4 is the last scheduled release, so if there are patches you care about in the 63 above, get them in
17:18:51 <colindixon> #topic carbon
17:18:59 <anipbu> #link https://lists.opendaylight.org/pipermail/project-proposals/2016-September/000525.html   <--- Kindly remind projects to submit project proposals for Carbon Offset 2 by 10/20/2016
17:19:20 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan#M0:_Declare_Intent   <--- We are currently missing M0 status from 21 projects: atrium, capwap, cardinal, centinel, didm, dlux, docs, eman, iotdm, natapp, next, nic, openflowjava, sdninterfaceapp, snbi, snmp, ttp, usecplugin, vtn, yang-push, yangide
17:19:29 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Per-Project_Carbon_Release_Plan_Template   <--- Carbon M1 Offset 0 is quickly approaching next week.  Kindly remind offset 0 projects to begin creating their draft release plan.
17:19:48 <anipbu> #info We have completed cleaning up the Weather page with 7 pending weather items still open and the rest archived.
17:20:02 <colindixon> #link https://wiki.opendaylight.org/view/Weather
17:20:04 <anipbu> #link https://lists.opendaylight.org/pipermail/netconf-dev/2016-October/000669.html   <--- The Carbon Autorelease job failed to build netconf modules.  A pacth fixing the issues have been merged.
17:20:45 <colindixon> #topic system integration and test
17:20:58 <colindixon> #info we're still seeing some ssh issues in infra and we're working on it, but it's not fixed yet
17:21:03 <colindixon> #topic infra
17:21:08 <colindixon> #undo
17:21:08 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x2b01750>
17:21:26 <colindixon> #topic infra
17:21:27 <colindixon> #info nothing this week, tykeal is out on PTO
17:21:51 <colindixon> #topic TSC elections
17:22:19 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-October/006136.html the board has approved the elections and we're ready to go
17:22:30 <colindixon> #link https://wiki.opendaylight.org/view/TSC:2016_Election this is the tracking page phrobb set up
17:22:57 <colindixon> #info it currently proposses starting nominations today and having them last a week
17:25:09 <colindixon> #info edwarnicke asks if starting on Monday might make sense so that notifications aren't lost in the weekend, rovarga says he agrees, colindixon says as long as it's measured in weeks it's probably fine
17:26:04 <colindixon> #info zxiiro asks if we want a longer nomination period, colindixon agrees
17:27:42 <colindixon> we will open the nomination period today (10/13) and close and close it at 23:59 UTC 10/26 wednesday, so that we can have the results for the 10/27 TSC call
17:28:13 <colindixon> #agreed we will open the nomination period today (10/13) and close it at 23:59 UTC 10/26 wednesday, so that we can have the results for the 10/27 TSC call
17:28:44 <rovarga> #info depends whether it is a Closeable or an AutoCloseable :)
17:29:23 <colindixon> we will have voting last 2 weeks spanning 10/27 to 23:59 UTC 11/9 wednesday, so we can have results for the 11/10 TSC call
17:29:51 <colindixon> #agreed we will have voting last 2 weeks spanning 10/27 to 23:59 UTC 11/9 wednesday, so we can have results for the 11/10 TSC call
17:32:18 <colindixon> #info abhijitkumbhare asks if it's really the case that you can only run in one RG, colindixon says yes and it's to avoid weird incentives and behavior around which one you would choose to win in if you won two
17:32:54 <colindixon> #action phrobb to kick off the TSC elecition nomination period
17:35:30 <colindixon> #info vishnoianil asks if we want to resolve when people need to be PTLs and/or committers to nominate themselves or vote
17:35:42 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-October/006124.html this thread
17:35:52 <colindixon> #info we have two options listed in that mail
17:36:50 <colindixon> #Info edwarnicke says (what colindixon thinks he's heard as mostly consensus) which is if you're eligible to participate in the window and get the vote/nominatino off in time, it's valid
17:37:05 <edwarnicke> #info colindixon heard edwarnicke correctly :)
17:37:19 <colindixon> #info rovarga poitns out we would want to wait to freeze things for a bit even if we froze them because we have no mdsal or controller PTL at the moment
17:37:20 <vishnoianil> +1 to the first proposal
17:45:37 <colindixon> #info edwarnicke points out that there are two ideas: 1.) you must be a committer at the opening of the vote to vote or 2.) you must be a comitter at some point during the vote to vote, both deal with removal in clean ways, by ignoring it
17:46:13 <colindixon> #startvote when do peopel have to be a committer to vote in the CAL elections: 1.) you must be a committer at the opening of the vote to vote or 2.) you must be a comitter at some point during the vote to vote? 1 or 2
17:46:13 <odl_meetbot> Begin voting on: when do peopel have to be a committer to vote in the CAL elections: 1.) you must be a committer at the opening of the vote to vote or 2.) you must be a comitter at some point during the vote to vote? Valid vote options are 1, or, 2.
17:46:13 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:46:26 <abhijitkumbhare> #vote 1
17:46:27 <edwarnicke> #vote 2
17:46:28 <adetalhouet> #vote 2
17:46:28 <colindixon> #vote 2
17:46:32 <jamoluhrsen> #vote 1
17:46:34 <rovarga> #vote 1
17:46:35 <Prem_> #vote 1
17:46:35 <vishnoianil> #vote 2
17:47:01 <jamoluhrsen> lol
17:47:28 <colindixon> #vote 1
17:47:40 <colindixon> #endvote
17:47:40 <odl_meetbot> Voted on "when do peopel have to be a committer to vote in the CAL elections: 1.) you must be a committer at the opening of the vote to vote or 2.) you must be a comitter at some point during the vote to vote?" Results are
17:47:40 <odl_meetbot> 1 (5): rovarga, colindixon, abhijitkumbhare, Prem_, jamoluhrsen
17:47:40 <odl_meetbot> 2 (3): vishnoianil, edwarnicke, adetalhouet
17:48:00 <colindixon> #agreed  you must be a committer at the opening of the vote to vote
17:48:29 <colindixon> #agreed as long as you are eligible and get your nomination e-mail out in time, you can nominate yourself even if you qualify after the window for nomination opens
17:48:43 <colindixon> #topic ExIm creation review
17:48:55 <colindixon> #linkhttps://wiki.opendaylight.org/view/Project_Proposals:Data_Export_Import
17:49:05 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:Data_Export_Import project proposal
17:49:14 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2016-September/000528.html proposed on 9/22/2016
17:50:48 <colindixon> #Info this is trying to provide an administration feature that's easy for devops or admins to use to deal with data store data with a particular focus on migrating data between major version updates or between models
17:51:30 <colindixon> #info can also be used to chagne things like shard configuration and suck the data out and put it back in
17:52:26 <colindixon> #Info the basic idea is relatively simple: do an export: gives you a models declaration file and the actual data stored per the netmod-yang-json RFC
17:52:50 <colindixon> #info the models declaration file allows you to make sure that the models you need are available when importing data
17:53:22 <colindixon> #Info on import we have two guardrails: 1.) models declaration file and 2.) as you put the data in there's checking that data comes in
17:53:59 <colindixon> #info exports data in a single transaction to get a pretty close to sane snapshot of data, but that's not flawless given that there's no administrative freeze on writes
17:54:35 <colindixon> #info all data is loaded into the MD-SAL in a single transaction
17:55:09 <colindixon> #info david points out that the data stored in netmod-json-yang format is version independent in terms of the data, so it's easier to migrate from models to models
17:56:08 <colindixon> #info rovarga asks what models are actually exported? if it's just the global schema context, that's not so much individual models as it is the almagmation of things
17:56:11 <colindixon> #ndo
17:56:12 <colindixon> #undo
17:56:12 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2864310>
17:56:34 <colindixon> #info rovarga asks what models are actually exported? if it's just the global schema context, that's not so much individual models as it is the almagmation of things in the running controller, not just YANG files
17:57:11 <colindixon> #info david notes that it can exclude modules by name or datastore (e.g., config or operational)
17:58:49 <colindixon> #info rovarga notes that model exclusion might go wrong if you exclude a model that another model uses a grouping from
17:59:26 <colindixon> #info colindixon notes that there are also issues where importing from json doesn't guarantee that the data will be the same in the YANG sense as when it was exported
17:59:40 <colindixon> #info edwarnicke also notes that it might be nice to be able to exclude from a point in the tree
18:00:58 <colindixon> #info Prem_ asks if they've looked at encryption, david says it's exported to the local filesystem, so not right now
18:02:01 <colindixon> #link rovarga asks that people do the schema context export in a way that's compatible with https://bugs.opendaylight.org/show_bug.cgi?id=2880
18:02:11 <colindixon> #startvote shall the TSC approve the Data Export Import as an incubation project? -1,0,+1
18:02:11 <odl_meetbot> Begin voting on: shall the TSC approve the Data Export Import as an incubation project? Valid vote options are -1, 0, +1.
18:02:11 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:02:19 <edwarnicke> #vote +1
18:02:27 <abhijitkumbhare> #vote +1
18:02:38 <colindixon> #vote +1
18:02:44 <Prem_> #vote +1
18:02:45 <adetalhouet> #vote +1
18:02:52 <jamoluhrsen> #vote +1
18:02:56 <vishnoianil> #vote +1
18:03:11 <rovarga> #vote +1, if encoding is scratched from scope
18:03:11 <odl_meetbot> rovarga: +1, if encoding is scratched from scope is not a valid option. Valid options are -1, 0, +1.
18:03:18 <rovarga> #vote +1
18:03:22 <colindixon> #endvote
18:03:22 <odl_meetbot> Voted on "shall the TSC approve the Data Export Import as an incubation project?" Results are
18:03:22 <odl_meetbot> +1 (8): rovarga, adetalhouet, edwarnicke, colindixon, jamoluhrsen, Prem_, vishnoianil, abhijitkumbhare
18:03:35 <colindixon> #info rovarga's +1 was " if encoding is scratched from scope"
18:03:47 <rovarga> #info because it is a subset of BUG-2880
18:03:51 <colindixon> #agreed Data Exim is an incubation project
18:04:06 <colindixon> #topic cookies
18:04:08 <colindixon> #endmeeting