16:59:14 <colindixon> #startmeeting tcc
16:59:14 <odl_meetbot> Meeting started Thu Jun  4 16:59:14 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:59:14 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:59:14 <odl_meetbot> The meeting name has been set to 'tcc'
16:59:20 <colindixon> #topic agenda bashing and roll call
16:59:23 <colindixon> #info colindixon
16:59:50 <edwarnicke> #info edwarnicke
17:00:01 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=30884#Agenda the agenda, fixed in history
17:00:25 <cdub> #info Chris Wright
17:00:27 <ChrisPriceAB> #info chris price partially
17:00:42 <dlenrow> #info dlenrow
17:01:17 <colindixon> nobody can hear me I take it?
17:01:27 <cdub> i can't
17:01:36 <ebrjohn> I heard you when you said its a quiet day
17:01:45 <odlcasey> #info Casey Cain
17:01:49 <ebrjohn> but nothing since
17:02:10 <tbachman> #link https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-28-16.59.html Minutes from last week’s meeting
17:02:20 <tykeal> odlcasey: you shouldn't be #info in this meeting unless you're a TSC member ;)
17:02:25 * tbachman wonders if Casey Cain is a new TSC member?
17:02:40 <odlcasey> Ok.
17:03:01 <cdub> tbachman: new odl person (as in project)
17:03:05 * ebrjohn isnt he a DJ?
17:03:23 <tbachman> cdub: thx!
17:03:29 <tbachman> odlcasey: welcome! :)
17:03:39 * tbachman hasn’t been around for a bit
17:03:39 <odlcasey> Thanks.  :)
17:03:51 <tykeal> sounds like a radio running in the background
17:03:55 <phrobb1> tbachman:  no, casey is a new OpenDaylight employee helping to herd the cats :-)… he doesn't know the protocol yet....
17:04:10 <phrobb1> odlcasey:  we only have TSC members #info in
17:04:11 <tbachman> ebrjohn: wrong Casey: http://en.wikipedia.org/wiki/Casey_Kasem
17:04:21 <tbachman> phrobb1: ah, good to know — thx!
17:04:29 * ebrjohn knows, but was just wondering who would catch it ;)
17:04:43 <odlcasey> lol
17:05:06 <jmedved> #info jmedved
17:05:08 <tbachman> :(
17:05:14 <tbachman> tykeal: super-powers
17:05:24 <phrobb1> #endmeeting
17:05:25 <tbachman> redo!
17:05:27 <tbachman> mulligan
17:05:40 <dfarrell07> tykeal: should chair phrobb1 so he can do that
17:05:45 <tbachman> tykeal: waiting on those super-powers
17:05:55 <tbachman> lol
17:05:59 <tbachman> he’s back!
17:06:03 <gzhao> :)
17:06:09 * alagalah Where in the world is Carman SanDeDixon
17:06:21 <ChrisPriceAB> Abhijitkumbhare you online?
17:06:33 * edwarnicke is in Seattle ;)
17:06:43 <tbachman> edwarnicke: sleepless? ;)
17:06:52 <edwarnicke> tbachman: Sleeping very well
17:07:04 <tbachman> :)
17:07:13 * tbachman can’t topic
17:07:45 <tbachman> #info we’re unfortunately short a chair — Topic is now Events
17:07:52 <tykeal> dfarrell07: you've got chair
17:08:09 <tbachman> #info phrobb1 says the ONS is on the 14th
17:08:13 <dfarrell07> #chair tbachman phrobb1
17:08:23 <tykeal> :-/ you should have had chair...
17:08:34 <tbachman> #info phrobb1 asks folks to register for the develoment summit at the end of the week of the ODL summit
17:08:40 <mohnish> #info mohnish anumala
17:08:42 <tbachman> dfarrell07: thx!
17:08:47 <tbachman> #topic Events
17:08:49 <dfarrell07> tbachman: It didn't work, lol
17:08:51 <tbachman> ah
17:08:54 <tykeal> *sigh*
17:09:07 <tbachman> the ‘ol “trick chair” again, eh? ;)
17:09:17 <dfarrell07> lol
17:09:20 <tykeal> #chair tbachman phrobb dfarrell07
17:09:20 <odl_meetbot> Current chairs: colindixon dfarell07 dfarrell07 phrobb tbachman tykeal
17:09:21 <tbachman> well oiled machine today
17:09:22 <tbachman> nice!
17:09:23 <tykeal> there we go
17:09:24 <dfarrell07> nice
17:09:34 <tbachman> #topic Lithium updates
17:09:37 <tbachman> :(
17:09:45 <tykeal> hah! that's why I messed up your nick via the backchannel
17:09:51 <dfarrell07> #topic Lithium updates
17:09:54 <dfarrell07> ??
17:09:58 * tbachman is chairless
17:10:07 <dfarrell07> #chair tbachman
17:10:07 <odl_meetbot> Current chairs: colindixon dfarell07 dfarrell07 phrobb tbachman tykeal
17:10:13 <phrobb1> OK, did we want to kill and restart this meeting with the proper name?… or is it too late and we'll live with it?
17:10:15 <tbachman> dfarrell07: thx!
17:10:23 <dfarrell07> tbachman: we'll see if it works, lol
17:10:25 <tykeal> dfarrell07: apparently I missed an r in your nick the first time I tried to chair you via the admin commands ;)
17:10:26 <tbachman> I don’t think we have too much here
17:10:38 <tbachman> we could probably recreate it pretty quickly
17:10:41 <tbachman> we have fast typers :)
17:10:44 <dfarrell07> #info zxiiro et al encurage everyone to test RC0
17:11:15 <tbachman> #info LuisGomez points out that testing takes time — just got RC0
17:11:50 <tbachman> #info colindixon says that for previous releases in between the RC<n> offsets, builds were made so that projects could tell to see if their bugs had been fixed
17:12:26 <ebrjohn> lots of static from ed
17:12:53 <tbachman> #info edwarnicke says that for Helium, we were building a daily RC<n> release, which people could use to verify fixes
17:13:18 <tbachman> #info gzhao says that in Helium, there was a daily helium build which triggered integration tests, but didn’t publish the results of the tests
17:13:33 <Youcef> #info Youcef Laribi
17:13:40 <tbachman> #info zxiiro says autorelease has two jobs: daily and release
17:14:01 <tbachman> #info zxirro says the daily doesn’t create a staging repo
17:14:15 <zxiiro> #link https://jenkins.opendaylight.org/releng/view/autorelease/
17:14:22 <tbachman> #undo
17:14:22 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1bac790>
17:14:37 <tbachman> #link https://jenkins.opendaylight.org/releng/view/autorelease/ Link to the autorelease jenkins page
17:15:09 <tbachman> #info colindixon asks if there are any new blocking bugs to be addressed, or new items on the weather page
17:15:19 <tbachman> #link https://wiki.opendaylight.org/view/Weather Current weather page for ODL Lithium
17:16:00 <phrobb1> #info LuisGomez asks when do we cut RC1?  Answer - we will cut RC1 in one week and acknowledge we are a week behind in RC testing
17:16:06 <tbachman> #info LuisGomez asks if we should update the release plan to reflect the right dates
17:16:11 <tbachman> phrobb1: thx!
17:16:22 <tbachman> #info colindixon says that probably makes sense
17:16:38 <colindixon> #info colindixon
17:17:46 <tbachman> #info gzhao says he’d like the TSC to schedule some time for the release plan review — notes that we have over 40 projects
17:18:17 <tbachman> #info gzhao says that given that ONS is June 14-18, which is RC3 timeframe, it might be challenging to do the reviews and meet the 25th release
17:18:30 <tbachman> #action gzhao and phrobb1 to find suitable times for Lithium release reviews
17:19:12 <phrobb1> thanks tbachman… fyi my audio has gone unusable… so if someone asks me a question… do it in irc also please
17:19:15 <tbachman> #info edwarnicke says he’d like to walk through the weather report
17:19:18 <tbachman> phrobb1: no problem!
17:19:25 <tbachman> (and will do ;) )
17:20:10 <tbachman> #info edwarnicke says that an email was sent out on the pattern matching bug
17:20:15 <tbachman> #link https://lists.opendaylight.org/pipermail/release/2015-June/002578.html email from rovarga_ on the patch
17:20:35 <tbachman> #info edwarnicke says there are some items that they’re chasing on Neutron, which may be issues on the openstack side
17:21:05 <tbachman> #info edwarnicke would like folks to have a look at the “to verify” blockers, to see if they’re truly resolved and can be removed from the weather page
17:21:21 <tbachman> #info tykeal says that on Monday there was an issue with the host that ran the VM for our gerrit system.
17:21:36 <tbachman> #info tykeal says they have a new VM in place, and are working to move the current gerrit system onto this VM
17:21:45 <gzhao> #info it is recommended always have current handler filled for blocking bugs, so /me can chase current handler
17:22:11 <tbachman> #info tykeal says that this morning the jenkins system could no longer talk to the API system. This has been fixed ,but the build queue is rather large
17:22:24 <tbachman> #info tykeal is talking to rackspace to see if we can get the API limits increased
17:22:55 <tbachman> #info colindixon asks if we’ve done any cursory examinations to see how many projects have merged their patches across to stable/lithium?
17:24:12 <tbachman> #info colindixon asks if it makes sense to walk through to see if there are any obvious places that haven’t been fixed in stable/lithium before we merge the fix in yangtools to stable/lithium
17:24:51 <tbachman> #info edwarnicke says that projects must have fixed in master in order to do their version bumps; these could be easily cherry-picked
17:25:05 <tbachman> #info colindixon asks if we can run the CSIT tests to uncover any such bugs?
17:25:12 <tbachman> #info ttkacik1 says we’d also have to run the autorelease tests
17:26:03 <tbachman> #action colindixon to follow-up offline to see if we can prevent breakage before the patch gets merged
17:26:39 <tbachman> #topic Integration and Test
17:26:50 * tbachman is having audio problems
17:27:09 <tbachman> #info colindixon asks how many projects haven’t yet bumped
17:27:22 * tbachman is missing a bunch of this :(
17:27:54 <zxiiro> colindixon: docs is built by autorelease now
17:28:10 <colindixon> zxiiro: understood
17:28:10 <colindixon> I can fix that today then
17:28:40 <zxiiro> #action colindixon to bump and branch docs
17:28:44 * tbachman couldn’t hear the bulk of that last section
17:28:59 <tbachman> #topic Creation Review for NETCONF/MD-SAL Spinout Projects
17:29:09 <gzhao> #info DIDM, Persistence, Reservation, SNMP4SDN, SNBI need to complete branching and version bump
17:29:18 <colindixon> can somebody #info the list of projects that haven’t bumped
17:29:30 <gzhao> colindixon: just did
17:29:43 <tbachman> #link https://lists.opendaylight.org/pipermail/project-proposals/2015-June/000319.html email thread on spin-out of NETCONF/MD-SAL
17:29:44 <colindixon> gzhao: thanks!
17:29:57 <colindixon> #undo
17:29:57 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1b7dcd0>
17:30:00 <colindixon> can we get a #topic
17:30:05 <gzhao> #info gzhao to follow up D4A for stable branch and version bump
17:30:13 * tbachman did a topic?
17:30:21 <colindixon> ok
17:30:23 <colindixon> I’m lagging
17:30:24 <tbachman> ah
17:30:27 <tbachman> I had two
17:30:31 <colindixon> I’m goin gto need to wait
17:30:32 <ChrisPriceAB> #info abhijitkumbhare will stand for me today, have Arno activities consuming my time.
17:30:36 <phrobb1> #topic NetCONF Creation Review
17:30:41 <tbachman> phrobb1: thx!
17:30:53 <colindixon> #chair phrobb1
17:30:53 <odl_meetbot> Current chairs: colindixon dfarell07 dfarrell07 phrobb phrobb1 tbachman tykeal
17:30:58 <odlcasey> ... beat me to it
17:30:59 <colindixon> try again
17:31:10 <mohnish> any link?
17:31:11 <phrobb1> #topic Creation Review for Netconf
17:31:19 <tbachman> #info ttkacik1 says the reason for splitting out netconf/restconf is that they’re not core to the controller functionality
17:31:22 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:Netconf he proposal
17:31:36 <mohnish> colin:thanks
17:31:43 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2015-February/000253.html propsed on 2/17/2015
17:32:16 * tbachman wonders how colindixon finds those so quickly
17:32:21 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2015-May/003141.html a mail with links to lots of discussion here
17:32:28 <colindixon> tbachman: on the TSC agenda
17:32:32 <tbachman> lol
17:32:33 <tbachman> :)
17:33:31 <tbachman> #info LuisGomez asks if this will be an offset 0 or 1 project
17:33:43 <tbachman> #info ttkacik1 says they’re aiming for an offset 0 project
17:33:44 <colindixon> #info ttkacik1 says he’s aiming for offset 0
17:33:46 <colindixon> #undo
17:33:46 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1b6fe50>
17:33:57 <cdub> ttkacik1: you are committer but not committed
17:34:28 <tbachman> #info colindixon says there are only two committers on the project, and are in the same time zone
17:34:46 <colindixon> cdub: good point
17:35:01 <tbachman> #info ttkacik1 says there will be a third committer as well, but they currenlty will be in the same time zones
17:35:55 <tbachman> #info colindixon asks if they’re looking to be a core feature to the controller
17:36:02 <colindixon> #info colindixon asks if they will be moving to mature with stable feautes, ttkacik1 says yes they aim to
17:36:09 <tbachman> colindixon: thx
17:36:41 <tbachman> #info colindixon asks what the ramifications are of the spinout on downstream projects
17:37:06 <ebrjohn> so, it will be both netconf and restconf breaking out into one project?
17:37:09 <tbachman> #info colindixon says this will change the group ID, and maybe the package names
17:37:14 <tbachman> ebrjohn: that’s the proposal
17:37:34 <cdub> will struggle to be mature w/out more diverse contributors
17:37:39 * tbachman is confused
17:37:57 <colindixon> cdub: noted
17:38:10 * tbachman is losing audio again
17:38:50 <colindixon> #Info cdub points out that with the current committer list they will have difficulty to be mature if diversity is a requirement
17:39:01 <tbachman> #info gzhao asks if we have the email for the committers?  We only have the user IDs, which makes it hard to contact them
17:39:09 <tbachman> #info ttkacik1 says they’ll provide the emails
17:39:48 <colindixon> #info mohnish asks if the user would be able to issue netconf/restconf commands from the Karaf CLI
17:40:06 <colindixon> #info ttkacik1 says that it’s not currently planned, but he’d be happy to help out and there is some code that would help
17:40:23 <colindixon> #info rovarga_ says to ask during project release planning beryllium
17:40:32 * tbachman wonders if colindixon’s internet woes are contagious — terrible audio atm
17:41:03 <abhijitkumbhare> tbachman - its contagious if you share the same ISP :)
17:41:10 <tbachman> lol
17:41:16 * tbachman is tethering on verizon
17:41:21 <cdub> 2.3.3 Promotion Review
17:41:39 <cdub> Diverse community of committers and contributors
17:41:58 <colindixon> cdub: that’s to go from mature => core
17:42:00 <tbachman> #info jmedved says that there are opportunities in beryllium for the community to provide patches and become committers
17:42:00 <colindixon> technically
17:42:08 <edwarnicke> cdub: 2.3.3 Promotion review is Mature -> Core ;)
17:42:19 <edwarnicke> cdub: 2.2.2 Graduation Review is for the transition to Mature
17:42:33 <edwarnicke> Sorry, 2.3.2
17:42:49 <cdub> ack
17:42:51 <alagalah> Is the horse dead yet ?
17:43:01 <tbachman> alagalah: that’s 2.3.1
17:43:04 * odlcasey gets a bat
17:43:10 <tbachman> dfarrell07: you queued up?
17:43:33 <phrobb1> #startvote Shall the TSC approve the Netconf project to the Incubation Lifecycle State? -1, 0, +1
17:43:33 <odl_meetbot> Begin voting on: Shall the TSC approve the Netconf project to the Incubation Lifecycle State? Valid vote options are -1, 0, +1.
17:43:33 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:43:34 <tbachman> #startvote Shall the TSC vote to approve splitting out NETCONF/RESTCONF into a separate project? +1, 0, -1
17:43:34 <odl_meetbot> Already voting on 'Shall the TSC approve the Netconf project to the Incubation Lifecycle State'
17:43:37 <tbachman> ah
17:43:39 <tbachman> sorry
17:43:44 <tbachman> phrobb1: thx
17:43:55 <colindixon> #vote +1
17:43:55 <edwarnicke> #vote +1
17:43:56 <LuisGomez> #vote +1
17:43:59 <dlenrow> #vote +1
17:43:59 <tbachman> I think we’re already voting — should be okay
17:43:59 <mohnish> #vote +1
17:44:00 <abhijitkumbhare> #vote +1
17:44:01 <jmedved> #vote +1
17:44:06 <cdub> #vote +1
17:44:11 <Youcef> #vote +1
17:44:12 <phrobb1> #endvote
17:44:12 <odl_meetbot> Voted on "Shall the TSC approve the Netconf project to the Incubation Lifecycle State?" Results are
17:44:12 <odl_meetbot> +1 (9): dlenrow, jmedved, LuisGomez, edwarnicke, cdub, mohnish, colindixon, abhijitkumbhare, Youcef
17:44:14 <gzhao> tbachman: meetbot is pretty smart.
17:44:18 <tbachman> :)
17:44:31 <tbachman> #topic MD-SAL Creation Review Proposal
17:44:33 <phrobb1> smarter than us tbachman ;-)
17:44:35 <tbachman> ah
17:44:36 <tbachman> darn
17:44:37 <tbachman> #undo
17:44:37 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x1b94690>
17:44:52 <tbachman> #agreed the  TSC approve the Netconf project to the Incubation Lifecycle State
17:45:03 <tbachman> : #topic MD-SAL Creation Review Proposal
17:45:06 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:MD-SAL md-sal spinout project proposal
17:45:29 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2015-February/000268.html proposed on 2/19/2015
17:45:46 <abhijitkumbhare> Question - what is left in the "controller" project if MD-SAL is moved?
17:46:01 <abhijitkumbhare> OK - ttkacik1 is answering
17:46:34 <edwarnicke> abhijitkumbhare: Not that it completely answers your question, but there is a list of the directories in the proposal if you'd like a little more precision on the inverse of your question ;)
17:46:44 <colindixon> abhijitkumbhare: config subsystem, some karaf magic parents, the MD-sal implementation, clsutering
17:46:50 <tbachman> #info ttkacik1 says there are 4 implementations of the MD-SAL; the spinout is of the DOM APIs, and also the Java binding APIs and adapters, which can be put on top of any other MDSAL implementation
17:47:15 <tbachman> #info abhijitkumbhare asks what is left in the "controller" project if MD-SAL is moved?
17:47:36 <tbachman> #info colindixon says the config subsystem, the MD-SAL data implementation, clustering, and karaf;
17:47:56 <tbachman> #info ttkacik1 says there are some applications on top of the MD-SAL (e.g. xSQL) and protocol frameworks
17:48:16 <colindixon> #undo
17:48:16 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1ba95d0>
17:48:18 <colindixon> #info ttkacik1 also says apps on top of the MD-SAL: toaster, xsql, protocol frameworks, message bus
17:48:26 <tbachman> colindixon: thx
17:48:29 <colindixon> tbachman: thanks!
17:48:34 <tbachman> np!
17:49:00 <colindixon> #info abhijitkumbhare asks if the name should be mdsal-api, not mdsal
17:49:27 <tbachman> #info abhijitkumbhare asks if most of the MD-SAL is still in the controller project
17:49:31 <colindixon> #info ttkacik1 says it’s not just the API since it contains the SPIs, implementations of the MD-SAL binding impls, and a few things
17:49:47 <tbachman> #info rovarga_ says it’s an implementation of the MD-SAL that’s left
17:50:43 <tbachman> #info there are core pieces and SPIs that are reusable across multiple implementations, which is what they’re proposing be split out
17:52:54 <colindixon> #info the general guidelines are to put things that would be needed for *all* mdsal implementations in the mdsal project and then leave the details of the current implementat(s) in controller (and yangtools)
17:54:21 <colindixon> #info rovarga_ says that historically yangtools has taken on a lot of code that argualby should have been in the controller, this helps with some of that
17:55:15 <colindixon> #info mohnish asks if these projects will interact with each other differently from other projects, e.g., other projects interact via YANG and the MD-SAL, but these will have to interact in lower-level OSGi ways
17:55:55 <colindixon> what are the dependencies goign to be between mdsal, yangtools and controller after this?
17:56:24 <colindixon> it’s pretty clear that netconf/restconf depends on controller which depends on yangtools
17:56:30 <colindixon> it’s less clear with mdsal
17:58:08 <colindixon> #link what are the dependencies goign to be between mdsal, yangtools and controller after this?
17:58:21 <colindixon> #info rovarga_ says mdsal will depend on yangtools, but not controller
17:58:28 * tbachman has to drop… terrible audio anyway :(
17:58:35 <colindixon> #info rovarga_ controller will depend on both yangtools and mdsal
17:59:19 <colindixon> #info restconf/netconf will likely be dependent on all three others (yangtools, controller, mdsal) and aaa
17:59:40 <abhijitkumbhare> I am still not convinced if the naming is not confusing : MD-SAL implementation in controller and a separate project with the name MD-SAL
17:59:42 <mohnish> Would it possible to add some of the details into a wiki page? Thanks.
18:00:01 <phrobb1> #startvote Shall the TSC approve the MD-SAL project to the incubation lifecycle state? -1, 0, +1
18:00:01 <odl_meetbot> Begin voting on: Shall the TSC approve the MD-SAL project to the incubation lifecycle state? Valid vote options are -1, 0, +1.
18:00:01 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:00:12 <edwarnicke> #vote +1
18:00:14 <jmedved> #vote +1
18:00:20 <mohnish> #vote +1
18:00:25 <dlenrow> #vote +1
18:00:27 <cdub> #vote +1
18:00:27 <Youcef> #vote +1
18:00:31 <LuisGomez> #vote +1
18:00:31 <colindixon> #vote +1
18:00:32 <abhijitkumbhare> #vote +1
18:00:37 <phrobb1> #endvote
18:00:37 <odl_meetbot> Voted on "Shall the TSC approve the MD-SAL project to the incubation lifecycle state?" Results are
18:00:37 <odl_meetbot> +1 (9): dlenrow, jmedved, LuisGomez, edwarnicke, cdub, mohnish, colindixon, abhijitkumbhare, Youcef
18:00:38 <cdub> i think we'll learn a lot from this
18:00:49 <colindixon> cdub: may you live in interesting times?
18:01:00 <phrobb1> #agreed the MD-SAL project is approved to the incubation lifecycle state
18:01:04 <cdub> yeah
18:01:08 <rovarga_> thanks :-)
18:01:20 <phrobb1> #topic cookies!
18:01:26 <colindixon> #endmeeting