#opnfv-meeting: Weekly Technical Discussion

Meeting summary

1. New Project Proposal NFVBench (bh526r, 13:02:55)
   1. (acm, 13:03:40)
   2. Al Morton (acm, 13:03:53)
   3. Trevor Cooper (trevor_intel, 13:03:55)
   4. https://wiki.opnfv.org/pages/viewpage.action?spaceKey=nfvbench&title=NFVbench+Project+Proposal (bh526r, 13:03:57)
   5. Thaj (thaj, 13:04:19)
   6. It is about a toolkit that allows developers, integrators, testers and customers to measure and assess the L2/L3 forwarding performance of an NFV-infrastructure solution stack (i.e. OPNFV scenario) using a black-box approach. (bh526r, 13:04:41)
   7. Trevor Cooper asked if to develop some workload or what is the workload? (bh526r, 13:14:44)
   8. Alec said it can specify a limited number of simple flows at the first stage (bh526r, 13:15:41)
   9. More complicated flow can be specified later stage (bh526r, 13:16:01)
   10. Simple traffic pattern today already gave us lots of thing to play with (bh526r, 13:16:36)
   11. Brian Skerry asked why it cannot be part of Vsperf project (bh526r, 13:17:18)
   12. Alec said Vsperf programs vswitch directly, but this project uses a different approach, not to program vswitch directly (bh526r, 13:17:56)
   13. Considering timing and urgency of taking it to TSC for participating in E Release, Frank asked if there is any concern to take it to TSC (bh526r, 13:50:40)
   14. All agreed to recommend it for TSC Creation review on May 2 (bh526r, 13:55:10)
   15. Meeting adjourned (bh526r, 13:55:20)

Action items

1. (none)

People present (lines said)

1. bh526r (14)
2. collabot (3)
3. acm (2)
4. thaj (1)
5. trevor_intel (1)