#opendaylight-meeting: tsc

Meeting started by colindixon at 16:59:48 UTC (full logs).

Meeting summary

  1. roll call and agenda bashing (colindixon, 16:59:54)
    1. colindixon (colindixon, 16:59:57)
    2. edwarnicke (edwarnicke, 17:00:13)
    3. dlenrow (dlenrow, 17:00:58)
    4. Chris Price (ChrisPriceAB, 17:01:05)
    5. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-14-17.00.html last week’s meeting minutes part 1 (colindixon, 17:01:24)
    6. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-14-17.51.html last week’s meeting minutes part 2 (colindixon, 17:01:50)
    7. ChrisPriceAB says the he intends to bring up the topic of Lithium “isotoping” after we get through this (colindixon, 17:02:21)
    8. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade (colindixon, 17:03:00)
    9. ACTION: LuisGomez and tykeal and jamoluhrsen to work out retaining the performance metrics for as long as we can (colindixon, 17:03:48)
    10. LuisGomez will join now (LuisGomez, 17:05:16)
    11. jmedved (on irc only for now) (jmedved, 17:05:20)
    12. maple and plugin2oc have both withdrawn from lithium, sxp it’s unclear about (colindixon, 17:05:27)
    13. ACTION: phrobb and gzhao to keep talking to SXP and possibly start a conversation on the TSC list on how lenient to be (colindixon, 17:05:50)
    14. ACTION: colindixon and phrobb will try to compile it (with notes where things still need more detail and discussion) into a more complete release plan (colindixon, 17:06:15)
    15. dfarrell07 for cdub (dfarrell07, 17:06:40)

  2. events (colindixon, 17:07:20)
    1. we’re at openstack (colindixon, 17:07:41)
    2. http://www.opendaylight.org/news/events/ the usual events place (colindixon, 17:07:51)
    3. nothing major new (colindixon, 17:08:18)

  3. lithium updates (colindixon, 17:08:23)
    1. gzhao is missed (edwarnicke, 17:08:26)
    2. https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=676729675 blocking bugs (colindixon, 17:08:32)
    3. lots of things going wrong with cutting RC0, they are being tracked in the blocking bugs spreadsheet (colindixon, 17:09:13)
    4. zxiiro says he found issues with autorelease (tbachman, 17:09:37)
    5. https://lists.opendaylight.org/pipermail/release/2015-May/002414.html email from zxiiro on autorelease issues (tbachman, 17:09:44)
    6. rovarga says the openflowplugin has agreed to cut the release branch as soon as the IPv6 prefix issues are fixed — maybe within 24 hrs (tbachman, 17:11:11)
    7. [19:09] <abhijitkumbhare> #agreed we should go ahead with branch cutting given that Ipv?prefix issue is fixed in He code base (rovarga, 17:11:34)
    8. phrobb asks LuisGomez if we have everything we need for RC0 testing (tbachman, 17:12:01)
    9. <abhijitkumbhare> #agreed we will still stick to both the implementation (He (default) and Li) (abhijitkumbhare, 17:12:20)
    10. LuisGomez gives encouraging update on status of testing efforts. tl;dr is that we're adding tests at a high rate, pretty good coverage on OFPlugin, tests inbound for other SBs (dfarrell07, 17:14:11)
    11. rovarga says the new plugin fixes issues with problems with statistics, and uncovered issues with the older version of OVS (2.0) (tbachman, 17:14:46)
    12. LuisGomez says there’s not enough time to upgrade the CI to OVS, as it also requires updating all the tests. He hopes to set something up to test the new version in one VM by sometime next week (tbachman, 17:15:23)
    13. ACTION: LuisGomez to work on getting OVS 2.3 to work in our CSIT infrastructure (colindixon, 17:15:29)
    14. LuisGomez if things look good, then we can migrate to the new version (tbachman, 17:15:34)
    15. Integration has an active TODO to get latest-OVS box for testing. dfarrell07 has been mentoring new-ish person to get it done, LuisGomez just bumped prio today and jumped on card himself, should be done soon. (dfarrell07, 17:15:39)

  4. infrastructure (colindixon, 17:16:45)
    1. colindixon says the jenkins resource tapping issues were just upgraded (tbachman, 17:17:06)
    2. https://lists.opendaylight.org/pipermail/tsc/2015-May/003097.html just fixed jenkins resource capping issues (colindixon, 17:17:06)
    3. tykeal says he’s reached out to Rackspace on resource caps, who has already responded — we now have 1-1/4 TB of RAM in our pool (tbachman, 17:17:32)
    4. tykeal says we now have a dedicated rep from Rackspace (tbachman, 17:18:03)
    5. it’s unclear if we can stay in their public cloud vs. moving to one of their managed private clouds (colindixon, 17:18:33)
    6. this might have added advantages that it might give us better control of our images (colindixon, 17:19:02)
    7. for example, this might make getting Ubuntu images much easier (colindixon, 17:19:20)
    8. phrobb says he needs to work with tykeal on any pricing changes as we range our caps (tbachman, 17:19:39)
    9. rovarga says we get some amount of jitter in the 20% area — is it posible to get network isolated VMs? (tbachman, 17:20:18)
    10. tykeal says we can’t do that in the public coud (tbachman, 17:20:34)
    11. ChrisPriceAB says OPNFV has a lot of infrastructure (tbachman, 17:21:16)
    12. ChrisPriceAB says they have about 20 more labs, and could set up some 3rd party CI to support more predictable testing (tbachman, 17:21:47)
    13. ACTION: ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and testing (tbachman, 17:22:29)

  5. florin corsas as a committer on LISP flow mapping (colindixon, 17:23:45)
    1. https://lists.opendaylight.org/pipermail/lispflowmapping-dev/2015-May/000274.html voting thread (colindixon, 17:23:51)
    2. http://spectrometer.opendaylight.org/?metric=commits&user_id=florin.coras&module=lispflowmapping spectrometer data (about a month out of date) (colindixon, 17:24:07)
    3. vina_ermagan says that florin corsas started as an intern, and is now active providing features and core infrastructure for LISP (tbachman, 17:24:16)
    4. https://git.opendaylight.org/gerrit/#/q/project:lispflowmapping+owner:%22Florin+Coras+%253Cfcoras%2540cisco.com%253E%22+status:merged gerrit data (colindixon, 17:24:20)
    5. VOTE: Voted on "shall we move Florin Corsas as a committer on LISP flow mapping?" Results are, +1: 7 (colindixon, 17:26:07)

  6. cookies! (tbachman, 17:28:04)


Meeting ended at 17:28:25 UTC (full logs).

Action items

  1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade
  2. LuisGomez and tykeal and jamoluhrsen to work out retaining the performance metrics for as long as we can
  3. phrobb and gzhao to keep talking to SXP and possibly start a conversation on the TSC list on how lenient to be
  4. colindixon and phrobb will try to compile it (with notes where things still need more detail and discussion) into a more complete release plan
  5. LuisGomez to work on getting OVS 2.3 to work in our CSIT infrastructure
  6. ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and testing


Action items, by person

  1. ChrisPriceAB
    1. ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and testing
  2. colindixon
    1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade
    2. colindixon and phrobb will try to compile it (with notes where things still need more detail and discussion) into a more complete release plan
  3. jmedved
    1. ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and testing
  4. LuisGomez
    1. LuisGomez and tykeal and jamoluhrsen to work out retaining the performance metrics for as long as we can
    2. LuisGomez to work on getting OVS 2.3 to work in our CSIT infrastructure
  5. phrobb
    1. phrobb and gzhao to keep talking to SXP and possibly start a conversation on the TSC list on how lenient to be
    2. colindixon and phrobb will try to compile it (with notes where things still need more detail and discussion) into a more complete release plan
  6. rovarga
    1. ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and testing
  7. tykeal
    1. LuisGomez and tykeal and jamoluhrsen to work out retaining the performance metrics for as long as we can


People present (lines said)

  1. tbachman (42)
  2. colindixon (42)
  3. dfarrell07 (15)
  4. odl_meetbot (12)
  5. edwarnicke (5)
  6. LuisGomez (4)
  7. rovarga (3)
  8. alagalah (3)
  9. dlenrow (2)
  10. jmedved (2)
  11. ChrisPriceAB (2)
  12. abhijitkumbhare (2)
  13. tykeal (2)
  14. phrobb1 (2)
  15. vina_ermagan (1)
  16. phrobb (0)


Generated by MeetBot 0.1.4.