#opendaylight-integration: Integration Team Weekly Meeting

Meeting started by dfarrell07 at 15:02:13 UTC (full logs).

Meeting summary

    1. jamoluhrsen running the meeting for Luis today (dfarrell07, 15:02:36)
    2. https://trello.com/b/ACYMpTVD/opendaylight-integration Trello (dfarrell07, 15:04:32)
    3. https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Controller-Cluster_Deployment New clustering wiki to review/edit (dfarrell07, 15:09:47)
    4. Everyone should raise tasks that they think should be done in Be via Trello (dfarrell07, 15:11:55)
    5. Build boxes will be upgraded to Cent7 in the next few weeks (huzzah!) (dfarrell07, 15:13:47)
    6. https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-1node-cds-netvirt-only-master/7/robot/report/log.html (grmontpetit, 19:54:17)
    7. https://wiki.opendaylight.org/view/RelEng/Builder/Jenkins#Patch_Test_Job (LuisGomez, 18:06:10)
    8. jenkins had issues last night b/c of left over java and mininet processes (tbachman, 15:03:22)
    9. zxiiro cleaned that up this morning (tbachman, 15:03:29)
    10. zxiiro says one of the problems with the jclouds plugin is that it doesn’t have a concept of state — it doesn’t know how many VMs are spun up, and just uses the rackspace API to spin up VMs (tbachman, 15:03:57)
    11. zxiiro says nodepool has a concept of state, to track which VMs are active, so it doesn’t need to keep calling the rackspace APIs (tbachman, 15:04:16)
    12. zxiiro says tykeal is on PTO, but is going to look into this when he gets back (tbachman, 15:04:32)
    13. Note that this is the Integration Team's weekly meeting, "TSC" in the title was a silly mistake on my part (dfarrell07, 15:04:45)
    14. LuisGomez asks about whether or not the LF has brought a resource online outside of North American time zones (tbachman, 15:06:02)
    15. zxiiro says there is someone who’s coming online soon (tbachman, 15:06:12)

  2. News (tbachman, 15:08:59)
    1. To submit tickets to the helpdesk (for stuff like Jenkins outages) email helpdesk@opendaylight.org (dfarrell07, 15:09:03)
    2. LuisGomez asks if anyone has gotten feedback on using Lithium (tbachman, 15:09:18)
    3. dfarrell07 says there’s all kinds of activity on twitter about people using it (tbachman, 15:09:35)
    4. LuisGomez says docs got negative feedback for the Helium release, and asked if anyone has had the chance to look at documentation for Lithium (tbachman, 15:10:12)
    5. Integration should expect a continued flow of patches into Integration as projects catch up on test code (dfarrell07, 15:11:17)
    6. jamoluhrsen asks how much longer we want to keep the stable/helium and stable/lithium jobs around (tbachman, 15:12:39)
    7. LuisGomez says stable/helium will be put in an End of Support (EOS) state now that Lithium out, though there are SR4 and SR5 releases scheduled (tbachman, 15:13:30)
    8. Note that the TSC will vote to officially EOS/EOL Helium in a few months. At that point, we can remove stable/helium jobs. (dfarrell07, 15:15:56)
    9. LuisGomez says the distribution code for stable/lithium is frozen for now; only changes supported now are in master (tbachman, 15:18:01)
    10. Integration committers should cherry-pick *testing* code from master to Lithium for now, to keep max testing there. Once that becomes too complex (subjective, expect emails and other discussion), we can stop cherry-picking to Lithium. Distribution code should only go to master. (dfarrell07, 15:18:36)
    11. LuisGomez notes that we’ve had to remove projects from a stable/<n> release in the past due to projects being abandoned; in these cases, the TSC has to make this decision (tbachman, 15:19:45)
    12. vratko asks about what if a projects breaks something just before an SR but is slow in responding/fixing the breakage (tbachman, 15:20:33)
    13. Vratko asks if it's possible to rename jobs, and if it can be automated. zxiiro says JJB doesn't support renaming jobs. A discussion (generally around branching/jobs) continues. (dfarrell07, 15:23:25)
    14. Vratko clarifies that it's totally possible to change Jenkins names via the UI (not supported by JJB, as noted above) (dfarrell07, 15:26:15)

  3. Trello updates (dfarrell07, 15:26:31)
    1. https://trello.com/b/ACYMpTVD/opendaylight-integration Trello board (dfarrell07, 15:26:46)
    2. LuisGomez is going to push a job for stability testing sometime today — one day longevity test for openflow (tbachman, 15:27:09)
    3. LuisGomez says that job will probably run on the weekend — maybe Saturdays (tbachman, 15:27:28)
    4. PhilShea has his last fix for clustering tests, and is waiting for that gerrit/job to be merged (tbachman, 15:28:26)
    5. PhilShea has been working hard on cluster tests, he reports that they are ready for review/merge (/me is excited) (dfarrell07, 15:28:37)
    6. We have a newly open TODO around the DSBenchmark test (Datastore Benchmark, via Jan and other Cisco test ppl I think), the person working on it is no longer working on ODL Integration (dfarrell07, 15:30:54)
    7. Radhika is interested in working on the DSBenchmark test (dfarrell07, 15:31:47)
    8. LuisGomez recommends running the DSBenchmark test as a single-node instance before trying a multi-node test (tbachman, 15:32:44)
    9. https://git.opendaylight.org/gerrit/#/c/23928/ (PhilShea, 15:36:53)

  4. Veryx demo of PktBlaster (tbachman, 15:38:24)
    1. PktBlaster is a software based solutino that runs on x86, with support for OpenFlow 1.0/1.3, REST API support for automation (tbachman, 15:39:01)
    2. It can do performance testing and network emulation (tbachman, 15:39:12)
    3. A test setup is shown using an Intel i7 server, 8GB of RAM connected to a DELL R420 2 CPU Xeon with 16GB RAM, which implements the server (tbachman, 15:40:08)
    4. jamoluhrsen asks if just REST calls can be used (i.e. not TCL) (tbachman, 15:40:38)
    5. The REST calls are wrapped into TCL scripts (tbachman, 15:40:49)
    6. the demo requires 1) setting the controller and configuration; 2) select network configuration; 3) select the test type, duration, and number of iterations (tbachman, 15:41:58)
    7. LuisGomez asks what’s expected if an errored packet is received (tbachman, 15:45:42)
    8. The controller should be (silently) dropping the errored packet (tbachman, 15:45:52)


Meeting ended at 16:19:26 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. odp-gerritbot (105)
  2. LuisGomez (64)
  3. tbachman (44)
  4. ChUsama (39)
  5. dfarrell07 (33)
  6. grmontpetit (29)
  7. jamoluhrsen (21)
  8. PhilShea (18)
  9. icbts (14)
  10. raphaelamorim (13)
  11. odl_meetbot (7)
  12. catohornet (4)
  13. tykeal (2)
  14. mgkwill (2)
  15. zxiiro (2)
  16. kailash (1)


Generated by MeetBot 0.1.4.