==========================
#opendaylight-meeting: tsc
==========================


Meeting started by colindixon at 17:00:14 UTC.  The full logs are
available at
http://meetings.opendaylight.org/opendaylight-meeting/2017/tsc/opendaylight-meeting-tsc.2017-04-13-17.00.log.html
.



Meeting summary
---------------

* roll call and agenda bashing  (colindixon, 17:00:22)
  * colindixon  (colindixon, 17:00:24)
  * skitt  (skitt, 17:00:44)
  * LINK:
    https://meetings.opendaylight.org/opendaylight-meeting/2017/tsc/opendaylight-meeting-tsc.2017-03-24-03.30.html
    last meeting's minutes (2 weeks ago)  (colindixon, 17:00:56)
  * anipbu  (anipbu, 17:01:06)
  * LINK:
    https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=53881#Agenda
    today's agenda  (colindixon, 17:01:09)
  * abhijitkumbhare  (abhijitkumbhare, 17:01:26)
  * Hideyuki  (hideyuki, 17:01:29)
  * LuisGomez  (LuisGomez, 17:01:38)
  * ACTION: colindixon, zxiiro and phrobb to come up with a proposal for
    tracking project activity in a positive way  (colindixon, 17:01:39)
  * ACTION: phrobb and tykeal to look into an ODL infra micro-datacenter
    in a box to make things work better at tutorials  (colindixon,
    17:01:39)
  * LINK: https://wiki.opendaylight.org/view/Events:Nitrogen_Dev_Forum
    <-- ddf  (jamoluhrsen, 17:02:23)
  * LINK: DDF discussion:
    https://lists.opendaylight.org/pipermail/tsc/2017-March/006851.html
    (skitt, 17:02:42)
  * lori  (lori, 17:02:46)
  * rovarga  (rovarga, 17:02:51)
  * Thanh  (zxiiro, 17:02:53)
  * jamoluhrsen  (jamoluhrsen, 17:02:57)
  * ACTION: katiezhang to follow up with validation of M4 and M5 Status
    per project  (colindixon, 17:03:24)
  * ACTION: colindixon to try to either find people to document how to
    be compatible with an OpenDaylight release with participating in the
    OpenDaylight simultaneous release  (colindixon, 17:04:15)
  * ACTION: colindixon to create postmortem topics for Carbon and add
    the clustering breakage to it  (colindixon, 17:04:16)
  * Anil VIshnoi  (vishnoianil, 17:05:06)
  * LINK: https://www.irccloud.com/pastebin/7GlaYAWH/  (CaseyODL,
    17:05:31)
  * CaseyODL would like the TSC to discussion choosing between BlueJeans
    and Zoom today  (colindixon, 17:05:31)
  * ACTION: colindixon to add the security mailing list to today's
    meeting or next meeting if we dont' have time  (colindixon,
    17:06:16)
  * ACTION: colindixon to add BlueJeans vs. Zoom today or next week if
    no time  (colindixon, 17:06:28)
  * ACTION: beryllium security release  (colindixon, 17:06:43)

* mailing list votes and discussions  (colindixon, 17:06:52)
  * shague  (shague, 17:06:58)
  * LINK:
    https://lists.opendaylight.org/pipermail/tsc/2017-April/006980.html
    Michael Vorburger and Stephen Kitt as committers on controller
    (colindixon, 17:07:02)
  * LINK:
    https://lists.opendaylight.org/pipermail/tsc/2017-April/006981.html
    Tomas Slusny as a committer on OpenFlow plugin  (colindixon,
    17:07:15)

* events  (colindixon, 17:07:56)
  * LINK: https://www.opendaylight.org/global-events  (colindixon,
    17:08:02)
  * LINK: https://wiki.opendaylight.org/view/Events:Main  (colindixon,
    17:08:07)
  * OPNFV summit in Beijgin in first week in June, Our DDF end of
    may/beginning of june in Santa Clara  (colindixon, 17:08:55)

* boron  (colindixon, 17:09:29)
  * Boron-SR3 was released last week  (colindixon, 17:09:40)

* Carbon  (colindixon, 17:09:47)
  * chasing projects that haven't gotten their milestones in
    (colindixon, 17:10:07)
  * the following projects are still absent: atrium capwap cardinal
    centinel next  yang-push  (colindixon, 17:10:47)
  * colindixon notes that he's pretty sure atrium, capwap, centinel, and
    yang-push have already left the Carbon release  (colindixon,
    17:11:42)
  * ACTION: colindixon to work with zxiiro and katie_ to figure out if
    we should drop next and cardinal  (colindixon, 17:12:03)
  * the following projects are still missing M5: dlux  faas genius lacp
    natapp next nic opflex ovsdb snbi snmp4sdn tsdr usecplugin yang-push
    (colindixon, 17:12:34)
  * projects having issues with karaf 4: federation alto BIER netconf
    (colindixon, 17:15:06)

* Karaf 4 migration risk and status  (colindixon, 17:15:24)
  * LINK:
    https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_9XugJp-6Qbbw20Omk/edit#gid=31712896
    (colindixon, 17:15:30)
  * LINK:
    https://lists.opendaylight.org/pipermail/tsc/2017-April/006957.html
    Mailing list thread on Karaf 4 risks and options  (colindixon,
    17:15:40)
  * during the kernel call on Tuesday, it seems as though very few
    projects have done very little testing of their Karaf 4
    distributions, the result is that other than green verify +1s, we
    have very little testing of Karaf 4 itself  (colindixon, 17:17:04)
  * it appears as though there's still less manpower than needed to
    drive this forward  (colindixon, 17:17:37)
  * restconf was broken in Karaf 4, but then was fixed, after that the
    upgrade to Karaf 4.0.9, but it seems to be a feature resolution
    issue in Karaf  (colindixon, 17:18:59)
  * anipbu says that this is our current status for Karaf 4 migration
    patches is: 11 Projects pending.  8 with pending patches.  3 without
    any patches.  3 nonleaf project cannot be dropped  (colindixon,
    17:19:54)
  * skitt asks if we could roll back to 4.0.7, rovarga says that might
    work  (colindixon, 17:20:37)
  * colindixon asks if we get restconf fixed (which seems plausible), we
    could then have a reasonable Karaf 4 distribution which we could
    test  (colindixon, 17:21:38)
  * ACTION: jamoluhrsen to talk to vrpolak about how to get Karaf 4
    distribution testing going along with perhaps LuisGomez
    (colindixon, 17:22:10)
  * LINK: https://bugs.opendaylight.org/show_bug.cgi?id=8208
    (jamoluhrsen, 17:22:57)
  * LINK: https://git.opendaylight.org/gerrit/53797  (vrpolak, 17:24:39)
  * ETA to merge: 1 week.  (vrpolak, 17:24:53)
  * jamoluhrsen and LuisGomez note that RC0 is supposed to be today and
    even if we were to unblock Karaf 4 distributions today, there's no
    way we could get all the jobs in place to meaningfully get carbon
    out the door  (colindixon, 17:25:03)
  * based on this assessment, we are 2-3 weeks behind where we would
    really like to be, but that's with zero system testing  (colindixon,
    17:27:13)
  * if system testing is mostly clean, that woiuld mean that was it,
    otherwise, that might be off by another 1-2 weeks as we figure
    things out  (colindixon, 17:27:38)
  * rovarga says his hope is that we should have much fewer issues once
    we get out toward leaf projects  (colindixon, 17:28:16)
  * lori has been testing Karaf 4, the distribution seems to build
    locally and come up fine, but the integration tests don't work
    locally, but do work in jenkins  (colindixon, 17:31:07)
  * skitt and rovarga note that pax-exam issues when moving to Karaf 4
    weren't trivial  (colindixon, 17:31:48)
  * colindixon notes that there is no way that we can have an RC0 today,
    next week would be as early as possible  (colindixon, 17:34:57)
  * we haven't started putting features into the Karaf 4 distribution
    yet, in part becuase we don't have a distribution check for our
    Karaf 4 distribution  (colindixon, 17:35:54)
  * from anipbu: Leaf projects with Karaf 4 Pending: cardinal, didm,
    iotdm, lacp, nic, snmp4sdn, unimgr.  Nonleaf projects with Karaf 4
    Pending: snmp, tsdr  (colindixon, 17:36:18)
  * vishnoianil asks if we could ship Karaf 3 in Carbon and switch to
    Karaf 4 in Carbon SR1  (colindixon, 17:39:16)
  * colindixon notes that given how much trouble we've had migrating
    from Karaf 3 to Karaf 4 internally, it seems like downstream users
    would find that super jarring  (colindixon, 17:42:30)
  * LINK:
    https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-carbon/
    (jamoluhrsen, 17:44:52)
  * colindixon asks if we have a Karaf 3 RC0 today if we wanted to do
    that, anipbu notes that we haven't had a succsessful carbon
    autorelease build since February  (colindixon, 17:45:41)
  * skitt notes that his feeling from the projects he touches is that
    Carbon is in generally better shape than Boron was going into RC0
    failing builds or not  (colindixon, 17:46:51)
  * colindixon asks if we can get autorelease building without leaf
    projects to see if we can cut out some noise  (colindixon, 17:49:41)
  * AGREED: colindixon says that as far as he understands we have
    repeatedly communicated to projects that Karaf 4 is required for
    Carbon participation, also we have given the integration and
    autorelease projects permission to remove projects which are
    interfering with the release to make progress knowing that projects
    which are truly participating can quickly fix issues and re-add
    themselves  (colindixon, 17:52:17)
  * ACTION: colindixon will look up the agreement that karaf4 is
    required for Simultaneous Release participation  (rovarga, 17:53:44)

* zoom vs. bluejeans  (colindixon, 17:54:20)
  * edwarnicke says he's had trouble using bluejeans internationally,
    zoom doesn't seem to have those problems  (colindixon, 17:54:36)
  * edwarnicke says echos, latency, etc.  (colindixon, 17:54:52)
  * skitt notes Red Hat has had no such issues despite using
    internationally  (colindixon, 17:55:17)
  * to be clear this is informational, not decisive in my mind
    (colindixon, 17:58:49)
  * VOTE: Voted on "(anyone, not just TSC members please also chime in)
    do people prefer bluejeans, zoom, or don't care?" Results are,
    bluejeans: 5, either: 4, zoom: 1  (colindixon, 17:59:36)
  * ACTION: CaseyODL to send mail to disucss@ tsc@ saying what the
    time-frame  (colindixon, 18:02:23)

* cookies  (anipbu, 18:04:21)



Meeting ended at 18:04:31 UTC.



Action items, by person
-----------------------

* CaseyODL
  * CaseyODL to send mail to disucss@ tsc@ saying what the time-frame
* colindixon
  * colindixon, zxiiro and phrobb to come up with a proposal for
    tracking project activity in a positive way
  * colindixon to try to either find people to document how to be
    compatible with an OpenDaylight release with participating in the
    OpenDaylight simultaneous release
  * colindixon to create postmortem topics for Carbon and add the
    clustering breakage to it
  * colindixon to add the security mailing list to today's meeting or
    next meeting if we dont' have time
  * colindixon to add BlueJeans vs. Zoom today or next week if no time
  * colindixon to work with zxiiro and katie_ to figure out if we should
    drop next and cardinal
  * colindixon will look up the agreement that karaf4 is required for
    Simultaneous Release participation
* jamoluhrsen
  * jamoluhrsen to talk to vrpolak about how to get Karaf 4 distribution
    testing going along with perhaps LuisGomez
* katie_
  * colindixon to work with zxiiro and katie_ to figure out if we should
    drop next and cardinal
* LuisGomez
  * jamoluhrsen to talk to vrpolak about how to get Karaf 4 distribution
    testing going along with perhaps LuisGomez
* vrpolak
  * jamoluhrsen to talk to vrpolak about how to get Karaf 4 distribution
    testing going along with perhaps LuisGomez
* zxiiro
  * colindixon, zxiiro and phrobb to come up with a proposal for
    tracking project activity in a positive way
  * colindixon to work with zxiiro and katie_ to figure out if we should
    drop next and cardinal
* **UNASSIGNED**
  * phrobb and tykeal to look into an ODL infra micro-datacenter in a
    box to make things work better at tutorials
  * katiezhang to follow up with validation of M4 and M5 Status per
    project
  * beryllium security release



People present (lines said)
---------------------------

* colindixon (80)
* skitt (28)
* anipbu (16)
* odl_meetbot (12)
* jamoluhrsen (9)
* rovarga (5)
* zxiiro (5)
* afredette (4)
* dfarrell07 (4)
* abhijitkumbhare (3)
* katie_ (3)
* vrpolak (2)
* shague (2)
* hideyuki (2)
* vishnoianil (2)
* LuisGomez (1)
* edwarnicke (1)
* lori (1)
* CaseyODL (1)



Generated by `MeetBot`_ 0.1.4