#opnfv-cperf: cperf

Meeting summary

1. 1. We now have a Docker image with our test tools on DockerHub as opnfv/cperf, so `docker run -it opnfv/cperf` works (dfarrell07, 18:17:48)
   2. https://hub.docker.com/r/opnfv/cperf/ CPerf test tools Docker container on DockerHub (dfarrell07, 18:17:53)
   3. jamoluhrsen points out that next TODO is to install NSTAT on this test container (dfarrell07, 18:18:31)
   4. ACTION: dfarrell07 or Nikos to install NSTAT on test container (dfarrell07, 18:18:49)
   5. dfarrell07 and Al talk about Pharos reservation system and changes to how pods are managed (dfarrell07, 18:22:20)
   6. discussion about if POD 2 status (dfarrell07, 18:22:36)
   7. we're unsure how much of POD 2 works (dfarrell07, 18:22:48)
   8. dfarrell07 reports back on testing project progress at plugfest and docs given on this morning's OPNFV test call (dfarrell07, 18:24:50)
   9. https://wiki.opnfv.org/display/functest/Testing Carbon Functest testing overview wiki, recently updated by plugfest and Morgan (dfarrell07, 18:24:58)
   10. http://testresults.opnfv.org/testapi/test_projects/cperf API for CPerf's OPNFV tests (dfarrell07, 18:25:05)
   11. http://testresults.opnfv.org/testapi/test_projects/promise API for CPerf's OPNFV tests (dfarrell07, 18:25:11)
   12. Nikos has released an updated version of their perf paper https://raw.githubusercontent.com/wiki/intracom-telecom-sdn/nstat/files/ODL_performance_report_v1.2.pdf (dfarrell07, 18:30:54)
   13. dfarrell07 asks Nikos for overview of interesting results (dfarrell07, 18:31:42)
   14. Nikos asks for feedback about paper, which metrics and parts we cared about (dfarrell07, 18:31:55)
   15. Nikos points us at ex summery for highlights (dfarrell07, 18:32:06)
   16. Soon results are coming via dashboard, in more detail, live (dfarrell07, 18:32:22)
   17. Jamo points out that we can run tests in ODL infra using opnfv/cperf image, maybe more quickly/easily (dfarrell07, 18:35:26)
   18. Nikos saw OOM fails when running cbench test, but doesn't think it's ODL b/c JVM would limit RAM, not seeing same issues when using mini/multinet (dfarrell07, 18:37:00)
   19. Note that Nikos has stability tests in this report, which we don't in ODL report, so point people to this (dfarrell07, 18:37:23)
   20. Luis points out that it's good how they report RAM/CPU/etc info in report, we might start doing that in ODL whitepaper, Luis has intern who will work on similar (dfarrell07, 18:37:53)
   21. ACTION: dfarrell07 will work on adding NSTAT install to opnfv/cperf image (dfarrell07, 18:38:20)
   22. Nikos gives tip about using "flame graphs" in perf reporting and profiling (dfarrell07, 18:39:46)
   23. http://www.brendangregg.com/flamegraphs.html Flame graph tool Nikos has turned us on to (dfarrell07, 18:40:47)
   24. Luis is super excited about this Flame Graph thing ;) (dfarrell07, 18:43:41)
   25. Luis talks about 1.1 of perf whitepaper, which should come out Monday (dfarrell07, 18:44:34)
   26. There were some minor changes, but the general idea is the same - they perf about the same and work for the usecases being considered (dfarrell07, 18:45:01)
   27. Much better wording in second report, time to edit/iterate more (dfarrell07, 18:45:13)
   28. ONOS has reviewed paper, said yesterday they like it and are fine (dfarrell07, 18:45:35)
   29. Cluster testing and Java API testing are likely still going to be blogged about, not a big deal, flame war avoided (dfarrell07, 18:46:20)
   30. For future work, we've asked ONOS to join CPerf for collab, not testing them ourselves in our whitepapers (dfarrell07, 18:47:14)

Action items

1. dfarrell07 or Nikos to install NSTAT on test container
2. dfarrell07 will work on adding NSTAT install to opnfv/cperf image

Action items, by person

1. dfarrell07
   1. dfarrell07 or Nikos to install NSTAT on test container
   2. dfarrell07 will work on adding NSTAT install to opnfv/cperf image

People present (lines said)

1. dfarrell07 (32)
2. collabot` (3)
3. jamoluhrsen (1)