#opnfv-testperf: Test and Performance Weekly Meeting

Meeting started by mbeierl at 13:56:59 UTC (full logs).

Meeting summary

  1. Roll Call (mbeierl, 13:57:37)
    1. Mark Beierl (StorPerf) (mbeierl, 13:57:47)
    2. Yujun Zhang (yujunz, 13:58:17)
    3. Morgan Richomme (morgan_orange, 13:58:55)
    4. Daniel Farrell (CPerf) (dfarrell07, 14:00:45)
    5. agenda https://wiki.opnfv.org/display/meetings/TestPerf (morgan_orange, 14:01:51)
    6. yuyang (yuyang, 14:02:50)
    7. http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2016/opnfv-testperf.2016-08-18-13.59.html (morgan_orange, 14:05:25)
    8. AP1 done (morgan_orange, 14:05:35)
    9. AP2 mail sent to Frank (morgan_orange, 14:05:47)
    10. AP3 pending but we will have more time after C release (morgan_orange, 14:06:10)
    11. ACTION: initiate a wiki page on POD allocation for test projects (short/mid/long term) after the C release (morgan_orange, 14:06:19)
    12. Al Morton (acm, 14:07:15)
    13. kubi (kubi001, 14:07:21)
    14. David McBride (dmcbride, 14:07:35)
    15. GTM audio issues - meeting moved to IRC only (mbeierl, 14:07:43)
    16. on functest we already consider no-ha on virtual environment - e.g. os-odl_l2-moon on virtual env (morgan_orange, 14:13:16)
    17. some consensus that it's okay from dfarrell07, kubi001, yuyang, morgan_orange (dfarrell07, 14:14:01)
    18. morgan_orange and kubi001 note that some projects are already conducting testing in virtual-only environments (e.g. Moon) (dmcbride, 14:16:38)
    19. morgan_orange says: for generic scenario (nosdn, odl_l2, onos, ..) it is better to test on target BM env (dmcbride, 14:18:10)
    20. morgan_orange for specific scenario it is acceptable to test on virtual env, it can be indicated in the release note (morgan_orange, 14:19:06)
    21. all the test projects branched (morgan_orange, 14:24:24)
    22. StorPerf update: intern project is wrapping up this week, with the branch created as of Monday (morgan_orange, 14:24:46)
    23. A general question: what exactly does stable mean? It should be only bug fixes, correct? (mbeierl, 14:25:21)
    24. CPerf doesn't have a C branch, but it's intentional (working from master, not in C-release, previously discussed) (dfarrell07, 14:25:42)
    25. dmcbride confirms only bug fixes are allowed on stable branch (yujunz, 14:26:50)
    26. only fixes for *documented* bugs (dmcbride, 14:27:24)
    27. Functest, branched on the 22nd, troubleshooting in progress on different scenarios with different feature projects. Problems identified in JIRA (jenkins stability in multisite, tempest issues on different scenarios, healthcheck issue with joid/lxd scenarios due to difference in lxc cirrios image,...) (morgan_orange, 14:40:23)
    28. Yardstick , branched on this Monday, fixed all the bugs from yardstick side which we have known,Yardstick created a wiki page to trace the Yardstick ci job status of stable branch. https://wiki.opnfv.org/display/yardstick/Yardstick+Colorado+CI+Status. Now we are work together with onos team to help them to do some debug work. (morgan_orange, 14:45:23)
    29. qtip skipped release C and is preparing for release D (yujunz, 14:46:32)
    30. vsperf has added some new tests in C, and support for two new traffic generator/test systems (acm, 14:48:08)
    31. bottlenecks has updated the docs, fixed the bugs from its side and already stable branched (yuyang, 14:49:19)
    32. in Functest we distinguish dashboarding and automatic reporting (morgan_orange, 14:52:06)
    33. automatic reporting = http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-fuel.html (morgan_orange, 14:52:29)
    34. based on test results stored in the DB and the criteria field (PASS/FAILED) we build automatically these pages to give a consistent view directly from CI/DB (morgan_orange, 14:53:04)
    35. dashboarding is more test =f (time), we decided for C release to move from home based solution to ELK framework (morgan_orange, 14:53:28)
    36. we are able to export mongo results into elasticsearch (morgan_orange, 14:53:39)
    37. we had some issues with elastic search addons (under license) => fixed now (morgan_orange, 14:54:01)
    38. https://git.opnfv.org/cgit/releng/tree/utils/test/reporting/functest (morgan_orange, 14:56:03)
    39. https://wiki.opnfv.org/display/yardstick/Yardstick+Colorado+CI+Status (mbeierl, 14:59:50)
    40. http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-fuel.html (mbeierl, 14:59:50)
    41. http://testresults.opnfv.org/reporting/index-colorado.html (morgan_orange, 15:00:31)
    42. ACTION: morgan_orange prepare short presentation on automatic reporting (morgan_orange, 15:02:13)
    43. ACTION: kubi001 morgan_orange plan an update on grafana/ELK in September (morgan_orange, 15:02:32)
    44. we have no chair for next week (morgan_orange, 15:03:25)
    45. ACTION: mbeierl to summarize stable branch guidelines for testperf members (mbeierl, 15:07:45)


Meeting ended at 15:08:44 UTC (full logs).

Action items

  1. initiate a wiki page on POD allocation for test projects (short/mid/long term) after the C release
  2. morgan_orange prepare short presentation on automatic reporting
  3. kubi001 morgan_orange plan an update on grafana/ELK in September
  4. mbeierl to summarize stable branch guidelines for testperf members


Action items, by person

  1. kubi001
    1. kubi001 morgan_orange plan an update on grafana/ELK in September
  2. mbeierl
    1. mbeierl to summarize stable branch guidelines for testperf members
  3. morgan_orange
    1. morgan_orange prepare short presentation on automatic reporting
    2. kubi001 morgan_orange plan an update on grafana/ELK in September


People present (lines said)

  1. morgan_orange (72)
  2. mbeierl (71)
  3. dmcbride (25)
  4. dfarrell07 (24)
  5. kubi001 (23)
  6. yujunz (17)
  7. acm (8)
  8. yuyang (4)
  9. collabot (3)


Generated by MeetBot 0.1.4.