#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 16:59:59)
    1. dlenrow (dlenrow, 17:00:13)
    2. colindixon (colindixon, 17:00:32)
    3. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-21-16.59.html minutes to previous meeting (tbachman, 17:00:39)
    4. https://wiki.opendaylight.org/view/TSC:Main#Agenda Agenda for today’s meeting (tbachman, 17:00:55)
    5. edwarnicke (edwarnicke, 17:01:10)
    6. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade (colindixon, 17:01:51)
    7. mohnish anumala (mohnish, 17:02:52)
    8. ACTION: LuisGomez and tykeal and jamoluhrsen to work out getting a patch merged in openstack to view all historical performance data (colindixon, 17:03:06)
    9. LuisGomez (LuisGomez, 17:03:28)
    10. Chris Price (ChrisPriceAB, 17:03:53)
    11. https://lists.opendaylight.org/pipermail/release/2015-May/002443.html Email from phrobb on Beryllium release plan proposal (tbachman, 17:04:06)
    12. Chris Wright (cdub, 17:04:14)
    13. ACTION: ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and (tbachman, 17:04:31)
    14. jmedved (jmedved, 17:05:09)

  2. events (colindixon, 17:05:11)
    1. phrobb says ONS is coming up in a few weeks (tbachman, 17:05:27)
    2. http://www.opendaylight.org/news/events/ the events page in it’s usually place (colindixon, 17:05:36)
    3. phrobb says they’re looking at shifting some things around for the summit — going to put out an agenda for the developer forum shortly after the Lithium release (tbachman, 17:05:56)
    4. colindixon asks for additional topics (tbachman, 17:06:30)
    5. edwarnicke says he’d like to discuss the IPv6 issues with respect to branch-cutting (tbachman, 17:06:48)
    6. rovarga says he doesn’t see the restconf/netconf and other creation reviews (breakout projects) (tbachman, 17:07:57)
    7. colindixon says he’ll schedule this for next week, given the time frame (tbachman, 17:08:06)

  3. Lithium and stable/helium updates (tbachman, 17:08:19)
    1. colindixon asks zxiiro what the status is of autorelease and branch cutting (tbachman, 17:08:43)
    2. zxiiro says autorelease is failing b/c l2switch is trying to build a distribution that no longer exists (tbachman, 17:09:00)
    3. https://bugs.opendaylight.org/show_bug.cgi?id=3398 bug against l2switch building old distribution (tbachman, 17:09:24)
    4. edwarnicke says l2switch is trying to build a hydrogen style distribution, but that distribution no longer exists (tbachman, 17:09:42)
    5. colindixon asks if downstream projects should wait to bump their versions (tbachman, 17:11:10)
    6. rovarga says until we perform the bumps, we don’t have visibility into what breakages are present (tbachman, 17:12:07)
    7. rovarga says we shouldn’t be shipping Lithium until the corresponding patch in yangtools is merged (cherry-picked) into stable/lithium (tbachman, 17:13:28)
    8. colindixon asks if downstream projects do bump their versions, will this cause issues using two different versions of yangtools (tbachman, 17:13:52)
    9. edwarnicke says this will definitely cause issues (tbachman, 17:14:01)
    10. colindixon says lithium isn’t blocked on this, but the ability to expose bugs in downstream projects is limited (tbachman, 17:14:36)
    11. edwarnicke says cutting master without version bumps is meaningless (tbachman, 17:15:55)
    12. edwarnicke also highlights that a lot of downstream projects feel pressure to "cut" (alagalah, 17:16:18)
    13. https://git.opendaylight.org/gerrit/#/c/21268/ <- l2switch stable/lithium should not be blocking autorelease anymore (edwarnicke, 17:17:51)
    14. The view of the TSC at this point is that the stable/lithium branch cutting does not block the ability to cut RC<n> releases (tbachman, 17:17:57)
    15. dbainbri asks if there is (a) no requirement to create stable/lithium and (b) we should not version bump (tbachman, 17:19:08)
    16. colindixon says there is currently no value in cutting stable/lithium unless you bump on master; if you cannot bump all your versions on master, you should not cut stable/litihium b/c you get no value, but does increase complexity (tbachman, 17:19:54)
    17. colindixon says that not bumping master, you have two things publishing artifacts to nexus, with no way of saying which one ‘wins’ (tbachman, 17:20:58)
    18. looking at OFP master, I see ./parent/pom.xml: <yangtools.version>0.8.0-SNAPSHOT</yangtools.version> (rovarga, 17:21:16)
    19. ACTION: zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping (tbachman, 17:22:47)
    20. ebrjohn says that SFC has already cut stable/lithium and not bumped versions (tbachman, 17:23:04)
    21. colindixon says you technically shouldn’t merge to master w/o the version bump (tbachman, 17:23:18)
    22. edwarnicke says it may be easier for SFC to delete the current stable/lithium branch, and then redo it when you’re ready to version bump (tbachman, 17:23:52)
    23. https://git.opendaylight.org/gerrit/#/c/20316/ patch from edwarnicke that bumped yangtools version in openflowplugin (tbachman, 17:25:09)
    24. LuisGomez says that integration already did their branch — without the branch, there’s no way they can do their testing (tbachman, 17:25:34)
    25. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Project_Dependency_Diagram (colindixon, 17:27:46)
    26. edwarnicke says there are a lot of projects that depend on OVSDB, so it’s probably the next project that needs to cut and bump (tbachman, 17:27:53)
    27. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-daily-master/lastFailedBuild/artifact/dependencies.log (zxiiro, 17:28:09)
    28. ACTION: zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux (colindixon, 17:30:33)
    29. rovarga suggests that we force merge the version bump on master and then deal with the issue later to return the build to normal, edwarnicke sees dragons there (colindixon, 17:32:08)
    30. https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=676729675 blocking bugs (colindixon, 17:34:21)
    31. https://wiki.opendaylight.org/view/Weather link to weather map page (tbachman, 17:34:39)

  4. System Integration and Test (tbachman, 17:35:59)
    1. OVS 2.3 is working in CI, yay! (colindixon, 17:36:15)
    2. LuisGomez says they cut stable/lithium yesterday (tbachman, 17:36:43)
    3. LuisGomez says their main issue is that all their triggers are “weird” now, so when something fails, it’s hard to know whether it was from stable/lithium or from master (tbachman, 17:37:22)
    4. the key issue is that cross-project triggers are still intra-branch, e.g., master triggerst master, stable/lithium triggers stable/lithium, but that’s not the reality on the ground at the moment (colindixon, 17:37:44)
    5. ACTION: colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions (colindixon, 17:40:27)
    6. ACTION: colindixon to add bug 3051 the the blocker list and get robert edit access (colindixon, 17:40:43)

  5. Infrastructure (tbachman, 17:41:00)
    1. tykeal says last night there were issues with slaves not working right — resulting in a huge queue today (tbachman, 17:41:29)
    2. colindixon asks how long until this this resolves itself (tbachman, 17:41:43)
    3. tykeal says maybe by midnight — but hard to know for sure (tbachman, 17:41:54)
    4. rovarga asks if we could expand the support staff so that we could reach peopel for issues 24x7 (colindixon, 17:42:56)
    5. ACTION: colindixon to take the issue of more staff for added hours to board (colindixon, 17:43:24)
    6. https://lists.opendaylight.org/pipermail/tsc/2015-May/003109.html email from ttkacik about LF infra (tbachman, 17:44:09)

  6. Beryllium Release Planning and Board Requests (tbachman, 17:44:44)
    1. https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan the draft release plan (colindixon, 17:44:52)
    2. colindixon asks people to look over it and comment on mailing lists (tbachman, 17:45:13)
    3. colindixon says there’s also an issue that some of the document may not reflect the project lifecycle changes (tbachman, 17:45:46)
    4. ACTION: colindixon to draft changes to language around project lifecycles (tbachman, 17:45:56)
    5. edwarnicke says he feels very bad about voting on that by next Wednesday, as he’s been heads down in development mode (tbachman, 17:46:29)

  7. Moving to Jira (tbachman, 17:47:34)
    1. https://lists.opendaylight.org/pipermail/tsc/2015-February/002554.html mailing list thread started here (colindixon, 17:48:07)
    2. rovarga says he’d like to get feedback from the community about using bugzilla vs. Trello vs. other tools (tbachman, 17:48:07)
    3. https://lists.opendaylight.org/pipermail/tsc/2015-March/002730.html and moved here (colindixon, 17:48:13)
    4. https://lists.opendaylight.org/pipermail/tsc/2015-May/003106.html before ending here (colindixon, 17:48:21)
    5. alagalah would use JIRA for GBP if ODL got a FOSS license from Atlassian (alagalah, 17:49:26)
    6. rovarga says this discussion has been brought up on the mailing lists 2 or 3 times, and has stalled each time; would like to get closure on this — worth moving to Jira? Too much of a disturbance, etc.? (tbachman, 17:49:37)
    7. rovarga also would like to know how the TSC and PTLs feel about using Jira (tbachman, 17:49:57)
    8. edwarnicke says we can split this into two things: can we switch from bugzilla to jira; the other is: how do we manage migrating from bugzilla to jira (tbachman, 17:50:29)
    9. colindixon says there’s another piece — running and operating jira (tbachman, 17:50:47)
    10. colindixon says there’s a cost to migrate from bugzilla to jira, and an operational cost for running jira (tbachman, 17:51:05)
    11. edwarnicke says that in the absence of the cost, there’s the question of using jira vs. bugzilla (tbachman, 17:51:33)
    12. colindixon says that his perception from the mailing list was that people preferrred Jira, but there’s a big cost (tbachman, 17:52:41)
    13. colindixon asks that cost aside, are folks opposed to moving to Jira (tbachman, 17:53:09)
    14. alagalah asks if we’d adopt it to everything, or just use it for bug-tracking (tbachman, 17:53:20)
    15. rovarga says we could start with bug-tracking, and add features as the community becomes more comfortable with it (tbachman, 17:53:44)
    16. ChrisPriceAB recommends using Jira for planning as well (tbachman, 17:54:18)
    17. colindixon says that his understanding is that not all plugins are available for opensource (tbachman, 17:54:34)
    18. abhijitkumbhare says that most people have used bugzilla but not used Jira (tbachman, 17:55:41)
    19. dneary says that bugzilla has difficulties related to scalability as you get more projects, versions, workflows (tbachman, 17:56:29)
    20. tykeal notes that they run several jira instances for various projects (tbachman, 17:56:37)
    21. rovarga recommends setting up some sort of sandbox where people can try out how their workflows would be (tbachman, 17:57:03)
    22. ACTION: phrobb to investigate what it takes to get to the license, and what the licence would be for (colindixon, 17:57:08)
    23. What tykeal meant is that dneary said that most of Bugzilla complaints are related to the UI failing to scale well to many projects, versions, complex workflows, etc (dneary, 17:57:46)
    24. we’d like to set up a sandbox and maybe do a TWS call where we show it off (colindixon, 17:58:10)


Meeting ended at 17:59:14 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 getting a patch merged in openstack to view all historical performance data
  3. ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and
  4. zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping
  5. zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux
  6. colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions
  7. colindixon to add bug 3051 the the blocker list and get robert edit access
  8. colindixon to take the issue of more staff for added hours to board
  9. colindixon to draft changes to language around project lifecycles
  10. phrobb to investigate what it takes to get to the license, and what the licence would be for


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
  2. colindixon
    1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade
    2. colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions
    3. colindixon to add bug 3051 the the blocker list and get robert edit access
    4. colindixon to take the issue of more staff for added hours to board
    5. colindixon to draft changes to language around project lifecycles
  3. gzhao
    1. zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping
    2. zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux
    3. colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions
  4. jmedved
    1. ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and
  5. LuisGomez
    1. LuisGomez and tykeal and jamoluhrsen to work out getting a patch merged in openstack to view all historical performance data
  6. rovarga
    1. ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and
  7. tykeal
    1. LuisGomez and tykeal and jamoluhrsen to work out getting a patch merged in openstack to view all historical performance data
  8. zxiiro
    1. zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping
    2. zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux
    3. colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions


People present (lines said)

  1. tbachman (117)
  2. colindixon (32)
  3. alagalah (18)
  4. ChrisPriceAB (12)
  5. edwarnicke (11)
  6. cdub (11)
  7. odl_meetbot (8)
  8. rovarga (7)
  9. tykeal (7)
  10. zxiiro (5)
  11. snoble (5)
  12. dbainbri (4)
  13. dneary (4)
  14. dfarrell07 (3)
  15. abhijitkumbhare (3)
  16. ebrjohn (2)
  17. gzhao (1)
  18. dlenrow (1)
  19. jmedved (1)
  20. mohnish (1)
  21. LuisGomez (1)


Generated by MeetBot 0.1.4.