17:00:35 <dfarrell07> #startmeeting tsc
17:00:35 <odl_meetbot> Meeting started Thu Mar 17 17:00:35 2016 UTC.  The chair is dfarrell07. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:00:35 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:35 <odl_meetbot> The meeting name has been set to 'tsc'
17:00:44 <dfarrell07> #chair phrobb
17:00:44 <odl_meetbot> Current chairs: dfarrell07 phrobb
17:01:02 <dfarrell07> ONS ppl are calling in now
17:01:55 <dfarrell07> #chair colindixon
17:01:55 <odl_meetbot> Current chairs: colindixon dfarrell07 phrobb
17:02:06 <edwarnicke> #info edwarnicke
17:02:10 <tykeal> dfarrell07: I spam tab to complete my sentences and get confused as to why it doesn't work sometimes ;)
17:02:16 <dfarrell07> #link https://wiki.opendaylight.org/view/TSC:Main#Agenda agenda
17:02:17 <gkaempfer> #info gkaempfer
17:02:30 <ChrisPriceAB> #info Chris Price
17:02:30 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-03-10-18.00.html last week's meeting minutes
17:02:33 <colindixon> #info colindixon
17:02:40 <dfarrell07> #info dfarrell07
17:02:42 <dfarrell07> 6
17:02:56 <colindixon> #action zxiiro will look more into maven central now that we're at least signing things
17:03:12 <edwarnicke> woot!
17:03:21 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
17:03:28 <colindixon> #action colindixon to follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future
17:03:31 <colindixon> #undo
17:03:31 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x11f7bd0>
17:03:39 <colindixon> #action colindixon to send mail about follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future
17:04:16 <phrobb_> We have dfarrell07 ChrisPriceAB colindixon edwarnicke ... not at quorum yet.. TSC members please #info in
17:04:26 <colindixon> #topic TSC elections
17:04:37 <colindixon> #info phrobb_ says there have been no new developments
17:04:42 <colindixon> #topic events
17:04:50 <colindixon> #link https://www.opendaylight.org/global-events
17:04:52 <dfarrell07> LuisGomez
17:04:57 <dfarrell07> phrobb_: we also have gkaempfer
17:04:57 <colindixon> #info many of us are at ONS
17:05:03 <LuisGomez> #info LuisGomez
17:05:08 <dfarrell07> 6 (actually now)
17:05:09 <colindixon> #Info there are people going to the collab summit at the end of this month
17:05:38 <colindixon> #info there's an SDN event in Beijing, then there's OpenStack in Austin
17:05:56 <colindixon> #info ChrisPriceAB asks if we have any OpenDaylight/OPNFV collaboration at OpenStack
17:06:20 <colindixon> #action ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presense at OpenStack
17:06:43 <colindixon> #topic boron
17:07:22 <colindixon> #link https://wiki.opendaylight.org/view/Weather#Unmerged_Patch_for_projects_to_test_OpenFlow_Plugin_default_design_to_Lithium projects can test with the new plugin, we're asking people to please test against it
17:07:43 <colindixon> #info boron M1 offset 1 milestones are due today
17:07:54 <colindixon> #link https://wiki.opendaylight.org/view/Weather#Bug_4527_Security_Groups_:_For_.22Other_Protocol.22_rule.2C_NeutronSecurityRule.getSecurityRuleProtocol.28.29_is_set_to_NULL neutron bug fixed
17:08:35 <colindixon> #info ChrisPriceAB asks if we're maintaining and deprecating all the external interfaces (APIs) or are we moving everything?
17:10:18 <colindixon> #Info abhijitkumbhare says that they have some patches for maintaining the older interfaces as well, but they have lower performance, abhijitkumbhare says that internal people should move if they can
17:11:48 <colindixon> #Info ChrisPriceAB notes (and colindixon endorses) that we should think about making sure we keep (even low-performance) versions of the old APIs, would be useful
17:12:29 <colindixon> #info abhijitkumbhare is asking to get initial tests back from things by next week
17:13:28 <colindixon> #topic stable/beryllium
17:13:48 <colindixon> #Info Beryllium-SR1 was supposed to happen today, but we're having test failures which are still under investigation
17:14:13 <colindixon> #info ChrisPriceAB has said we're still OK with providing something useful to OPNFV
17:14:25 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR1/Status#Status
17:14:38 <colindixon> #Info zxiiro says that boron is also failing with the same issues
17:14:48 <colindixon> #info anipbu seems to think it might be a regression in YANG parser
17:15:55 <colindixon> #info colindixon asks if we have the right people engaged, anipbu says it was only this morning that we thought it might be a yang parser issue, we're waiting on a response
17:16:09 <colindixon> #topic system integration and test
17:16:28 <colindixon> #info jamoluhrsen says that anipbu covered most of it above
17:16:52 <colindixon> #info jamoluhrsen says he'd like to a TWS on monday about possible changes to the process for integration and test in boron
17:16:58 <jamoluhrsen> #link https://lists.opendaylight.org/pipermail/release/2016-March/005993.html
17:17:22 <dfarrell07> #undo
17:17:22 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x13a5510>
17:17:31 <Badrinath> #info Badrinath attending on behalf of Mohnish  Anumala
17:17:32 <dfarrell07> #link https://lists.opendaylight.org/pipermail/release/2016-March/005993.html Int/Test reqs for tests
17:17:39 <colindixon> #topic infrastructure
17:17:44 <colindixon> Badrinath: welcome!
17:18:06 <colindixon> #info private cloud is coming up, zxiiro is moving the sandbox into the private cloud
17:19:30 <colindixon> #topic new committers on SXP
17:19:35 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004876.html
17:19:41 <colindixon> #undo
17:19:41 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x13a5850>
17:19:56 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004876.html Promotion of Martin Sunal, Abdelilah Essiari on SX
17:19:59 <colindixon> #undo
17:19:59 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x13a5a90>
17:20:01 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004876.html Promotion of Martin Sunal, Abdelilah Essiari on SXP
17:20:07 <dfarrell07> #info they have 2/2 votes from active committers (1 inactive)
17:21:02 <colindixon> #info they each have 5-7 merged commits, with non-trivial code
17:21:48 <colindixon> #startvote shall the TSC bless Martin Sunal, Abdelilah Essiar as committers on the SXP project? -1, 0, +1
17:21:49 <odl_meetbot> Begin voting on: shall the TSC bless Martin Sunal, Abdelilah Essiar as committers on the SXP project? Valid vote options are -1, 0, +1.
17:21:49 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:21:53 <ChrisPriceAB> #vote +1
17:21:53 <edwarnicke> #vote +1
17:21:54 <dfarrell07> #vote +1
17:21:54 <LuisGomez> #vote +1
17:21:55 <gkaempfer> #vote +1
17:21:55 <colindixon> #vote +1
17:22:04 <Badrinath> #vote +1
17:22:36 <colindixon> #endvote
17:22:36 <odl_meetbot> Voted on "shall the TSC bless Martin Sunal, Abdelilah Essiar as committers on the SXP project?" Results are
17:22:36 <odl_meetbot> +1 (7): gkaempfer, LuisGomez, dfarrell07, ChrisPriceAB, edwarnicke, colindixon, Badrinath
17:22:56 <colindixon> #agree Martin Sunal, Abdelilah Essiari are now committers on SXP
17:23:58 <colindixon> #topic HoneyComb/BridgeDomain creation review
17:24:08 <colindixon> #Link https://wiki.opendaylight.org/view/Project_Proposals:HoneyCombBridgeDomain
17:24:25 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:HoneyCombBridgeDomain#Project_overview
17:24:39 <colindixon> #undo
17:24:39 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x14607d0>
17:24:53 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:HoneyCombBridgeDomain#Project_overview slides are available for download here
17:25:19 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2016-February/000401.html proposed on 2/11/2016
17:27:42 <colindixon> #info this is largely a way to interact with the VPP dataplane in fd.io via the honeycomb local agent in fd.io
17:28:03 <colindixon> #info particularly to work on the bridge domain model/API provided by the honeycomb agent in fd.io
17:29:10 <colindixon> #info this project would then act as the orchestrator to manage multiple different honeycomb agents to provide virtual bridge domains across multiple VPP instances
17:32:41 <edwarnicke> colindixon offers EOPIaaS (Explaining Other Peoples Ideas as a Service)
17:32:53 <colindixon> pronounced you-piss
17:33:08 * edwarnicke would suggest you-pass ;)
17:33:20 <colindixon> #info phrobb_ notes that we'll have to do an IPR
17:34:11 <colindixon> #info colindixon asks if there are any trademark issues with names here, he suspects not and that it's all inside the LF, which probably helps
17:34:44 <colindixon> #startvote shall the TSC move the  HoneyComb/BridgeDomain to incubation? -1, 0, +1
17:34:44 <odl_meetbot> Begin voting on: shall the TSC move the  HoneyComb/BridgeDomain to incubation? Valid vote options are -1, 0, +1.
17:34:44 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:35:04 <dfarrell07> #vote +1
17:35:06 <colindixon> #vote +1
17:35:06 <ChrisPriceAB> #vote +1
17:35:08 <gkaempfer> #vote +1
17:35:18 <Badrinath> #vote +1
17:35:19 <LuisGomez> #vote +1
17:35:20 <edwarnicke> #vote +1
17:35:24 <colindixon> #endvote
17:35:24 <odl_meetbot> Voted on "shall the TSC move the  HoneyComb/BridgeDomain to incubation?" Results are
17:35:24 <odl_meetbot> +1 (7): gkaempfer, LuisGomez, dfarrell07, ChrisPriceAB, edwarnicke, colindixon, Badrinath
17:35:33 <colindixon> #agree the  HoneyComb/BridgeDomain is now an incubation project
17:36:09 <colindixon> #startvote shall the TSC allow the HoneyComb/BridgeDomain project to join the boron release at offset 1 despite this being 2 weeks late, technically? -1, 0, +1
17:36:09 <odl_meetbot> Begin voting on: shall the TSC allow the HoneyComb/BridgeDomain project to join the boron release at offset 1 despite this being 2 weeks late, technically? Valid vote options are -1, 0, +1.
17:36:09 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:36:22 <dfarrell07> #vote +1
17:36:23 <colindixon> #vote +1
17:36:23 <edwarnicke> #vote +1
17:36:28 <ChrisPriceAB> #vote +1
17:36:29 <gkaempfer> vote +1
17:36:35 <gkaempfer> #vote +1
17:36:35 <Badrinath> #vote +1
17:36:45 <colindixon> #endvote
17:36:45 <odl_meetbot> Voted on "shall the TSC allow the HoneyComb/BridgeDomain project to join the boron release at offset 1 despite this being 2 weeks late, technically?" Results are
17:36:45 <odl_meetbot> +1 (6): gkaempfer, ChrisPriceAB, dfarrell07, edwarnicke, colindixon, Badrinath
17:36:52 <LuisGomez> #vote +1
17:37:08 <colindixon> #agree the  HoneyComb/BridgeDomain project will be able to join Boron at offset 1
17:37:29 <abhijitkumbhare> Congrats HBD :)
17:37:30 <colindixon> #topic Infrastructure Utilities Project
17:37:40 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:Utilities
17:37:53 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000416.html proposed on 3/3/2016
17:38:26 <colindixon> #info this is a project looking to provide utilities that the proposers who have found to be very useful
17:39:10 <colindixon> #info they will start with two utilities: counters and Seamless Async Calls Utility
17:39:22 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:Utilities#Description see here?
17:40:30 <colindixon> #info the counters stuff works with YANG and JMX to provide useful counters to expose to others and monitor them
17:40:53 <colindixon> #info a lot of work with rovarga has happened here
17:41:12 <colindixon> #info colindixon notes that personally this counter stuff looks cool
17:42:03 <abhijitkumbhare> Should the repo name be similar to the way the Honeycomb virtual bridge domain has done? i.e. honeycomb/vbd. In that style you could do - utils/counters and utils/async?
17:42:13 <colindixon> #info colindixon has two worries: (1) the scope is currently limited to just these two utilities, which seems likely not quite what they want, (2) in the past projects which exist solely to aggregate things for other projects have had trouble, e.g., toolkit and coretutorials
17:42:32 <colindixon> abhijitkumbhare: I'd argue no, but it's an opinion of mine that we have way too many repos
17:42:54 <colindixon> #Info edwarnicke suggests to try to work in the normal development pattern, e.g., get involved in the archetypes
17:43:26 <abhijitkumbhare> My thought is if folks need to bring other utils - they should not be blocked by utils project
17:43:45 <edwarnicke> abhijitkumbhare: I definitely agree with you on non-blocking :)
17:46:10 <colindixon> #info the response is that this is the scope for the boron release, and it could be adjust in later times, and colindixon thinks that's fine and we shouldn't block it because of that
17:48:49 <tykeal> my cats are more likely to listen to you colin ;)
17:49:26 * edwarnicke is comforted to not that tykeal's cats take TSC Members seriously :)
17:49:48 <colindixon> #info phrobb_ asks if there's code that we need to do IPR on any incoming code
17:50:05 <phrobb_> thanks colindixon
17:50:31 <tykeal> edwarnicke: it's probably because I stand and pace during my phone meetings. They get more play time that way ;)
17:50:42 <colindixon> #info abhijitkumbhare asks if we should think about structuring this as a hierarchical project, e.g., infrautilities/counters, infrautilities/async,
17:51:07 <edwarnicke> tykeal: So you are saying that more meetings is the solution to being taken more seriously? ;)
17:51:18 <tykeal> haha, only by my cats
17:51:28 <edwarnicke> colindixon: I think abhijitkumbhare suggested utils/counters and utils/async
17:51:38 <tykeal> they're rather furry and don't help much with stuff
17:51:47 <edwarnicke> tykeal: Its the lack of opposable thumbs
17:52:56 <colindixon> #info abhijitkumbhare says maybe it would be group more things together
17:53:15 <tykeal> spinning out a project / subproject is something we've done before, it's always a valid idea down the road
17:53:17 <colindixon> #info colindixon says he feels a bit like we have too many repos already
17:53:30 <edwarnicke> #info please note we *do* have mechanisms in our lifecycle for a hiearchy of projects
17:53:33 <colindixon> #info ChrisPriceAB notes we can fix that problem in the future and we don't have it yet
17:54:10 <colindixon> #startvote shall the TSC move The Infrastrucure Utilities Project to incubation? -1, 0, +1
17:54:10 <odl_meetbot> Begin voting on: shall the TSC move The Infrastrucure Utilities Project to incubation? Valid vote options are -1, 0, +1.
17:54:10 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:54:12 <edwarnicke> #vote +1
17:54:13 <ChrisPriceAB> #vote +1
17:54:13 <dfarrell07> #vote +1
17:54:14 <gkaempfer> #vote +1
17:54:16 <colindixon> #vote +1
17:54:18 <LuisGomez> #vote +1
17:54:24 <Badrinath> #vote +1
17:54:27 <colindixon> #endvote
17:54:27 <odl_meetbot> Voted on "shall the TSC move The Infrastrucure Utilities Project to incubation?" Results are
17:54:27 <odl_meetbot> +1 (7): gkaempfer, ChrisPriceAB, LuisGomez, dfarrell07, edwarnicke, colindixon, Badrinath
17:54:39 <colindixon> #agree The Infrastrucure Utilities Project is now an incubation project pending IPR
17:55:29 <colindixon> #startvote shall the TSC allow The Infrastrucure Utilities Project to join the Boron offset 0 assuming they quickly send your M1? -1, 0, +1
17:55:29 <odl_meetbot> Begin voting on: shall the TSC allow The Infrastrucure Utilities Project to join the Boron offset 0 assuming they quickly send your M1? Valid vote options are -1, 0, +1.
17:55:29 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:55:38 <edwarnicke> #vote +1
17:55:39 <dfarrell07> #vote +1
17:55:40 <ChrisPriceAB> #vote +1
17:55:42 <colindixon> #vote +1
17:55:44 <gkaempfer> #vote +1
17:55:46 <Badrinath> #vote +1
17:55:53 <colindixon> #endvote
17:55:53 <odl_meetbot> Voted on "shall the TSC allow The Infrastrucure Utilities Project to join the Boron offset 0 assuming they quickly send your M1?" Results are
17:55:53 <odl_meetbot> +1 (6): dfarrell07, gkaempfer, ChrisPriceAB, edwarnicke, colindixon, Badrinath
17:56:05 <colindixon> #agree The Infrastrucure Utilities Project  can join boron at offset 0
17:56:29 <LuisGomez> #vote +1
17:56:41 <colindixon> #info LuisGomez has voted +1 every time so far for the record
17:56:48 <LuisGomez> i am kind of slow today
17:56:58 <abhijitkumbhare> Congrats utils
17:57:29 <phrobb_> #topic Removing Inactive Committers
17:57:39 <colindixon> #topic remove inactive committers
17:58:16 <colindixon> #info our charter allows PTLs  to forcibly remove inactive committers after an extended period of time, e.g., six months
17:59:18 <tykeal> IIRC charter doesn't require TSC approval for removal
17:59:20 <edwarnicke> #link https://www.opendaylight.org/tsc-charter < - "From the charter "A Committer who is disruptive, or has been inactive for an extended period (e.g., six or more months) may have his or her Committer status revoked by the project leads."
17:59:25 <colindixon> #info as long as projects make honest effort to contact inactive committers, the TSC feels this makes sense
18:02:28 <colindixon> #info as far a we're concerned projects can remove inactive committers, the TSC would like to be informed in these cases, and will handle disputes
18:04:07 <colindixon> #agree the TSC feels like this doesn't need a vote, PTLs can remove inactive committers at their discretion, but the TSC strongly encourages that people let the TSC know, and also notes the TSC can resolve any disputes of this
18:04:49 <colindixon> #action colindixon to start a mail about best practices about keeping committer lists clean
18:04:59 <colindixon> #topic cookies
18:05:03 <colindixon> #endvote
18:05:14 <colindixon> #endmeeting