#opnfv-cperf: cperf

Meeting summary

1. 1. mattw4 is up for vote as PTL of CPerf, has Jamo/Luis/Marcus vote, missing Tim, dfarrell07 will ping (dfarrell07, 18:19:23)
   2. mattw4 is up to 210 nodes on scale tests, now that he's actually placing the nodes deliberately (dfarrell07, 18:19:49)
   3. mattw4 has some container patch merged, next up is ansible deployment stuff (dfarrell07, 18:20:08)
   4. mattw4 is doing some cleanup of ansible, dfarrell07 and mattw4 talk about where to put it once ready, seems like merge into ansible-odl (dfarrell07, 18:25:06)
   5. https://git.opendaylight.org/gerrit/gitweb?p=integration/packaging/ansible-opendaylight.git;a=tree ansible-opendaylight role (dfarrell07, 18:25:16)
   6. jamoluhrsen is using CPerf's docker image downstream again, so will have feedback maybe (dfarrell07, 18:26:00)
   7. sai talks about next round of carbon testing RH will do, planning what focus will be (dfarrell07, 18:27:55)
   8. will be using 50+ compute, control plane tests, longevity tests, will try to check longevity issues cable labs has been reporting (dfarrell07, 18:28:29)
   9. sai expects first iteration of testing will start in early september, if you have issues/ideas please report them ASAP (dfarrell07, 18:28:54)
   10. mattw4 asks sai about how they are spreading out openstack services (dfarrell07, 18:29:15)
   11. sai talks about first model, HA with 3 controllers all openstack services on the box, 2nd with ODL on bare metal nodes and ODL isolated, will try to figure out at what scale ODL needs to be on dedicated hardware nodes (dfarrell07, 18:30:56)
   12. mattw4 is basically planning the same thing, currently running ODL on shared box w/ openstack, looking to try ODL on isolated box (dfarrell07, 18:31:18)
   13. big focus in these next tests will be to check for RAM issue, which we saw last time, make sure we get RAM dumps to analyze (dfarrell07, 18:31:42)
   14. mattw4 talks about standard model being compute nodes in containers, one instance per compute node (dfarrell07, 18:32:15)
   15. mattw4 clarifies that it's a real instance VM via qemu (dfarrell07, 18:33:16)
   16. jamoluhrsen bets anyone a case of beer that there's a RAM issue, they are seeing in CI with fairly simple tests (dfarrell07, 18:33:36)
   17. jamoluhrsen also expects there will be big perf hit when running in a cluster (dfarrell07, 18:33:48)
   18. sai says they will only be deploying with a clustered ODL, will only use single node once stuff breaks (dfarrell07, 18:34:14)
   19. jamoluhrsen says it would be helpful to see comparison of cluster and non-cluster for many tests, (dfarrell07, 18:34:44)

Action items

1. (none)

People present (lines said)

1. dfarrell07 (22)
2. collabot (4)
3. LuisGomez (1)
4. mattw4 (1)
5. sai (0)
6. mgkwill (0)
7. jamoluhrsen (0)