15:02:54 <srao> #startmeeting vSwitchperf
15:02:54 <collabot`> Meeting started Wed Jul 17 15:02:54 2019 UTC.  The chair is srao. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:54 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:02:54 <collabot`> The meeting name has been set to 'vswitchperf'
15:03:06 <srao> #topic Development Update.
15:04:01 <srao> #info Integrating VPP-Monitoring with VSPERF.
15:04:12 <srao> #info Reuse existing project
15:04:47 <srao> #info Monitors VPP and sends metrics over same Collectd publishing channel.
15:06:01 <srao5> #info Use COllectd's 'exec' plugin to grab metrics from the 'magent' (VPP monitor).
15:07:13 <srao5> #info Requires addition in (a) Grafana (b) Jupyter Notebook.
15:07:43 <srao5> #topic Containerization of VSPERF.
15:08:42 <srao5> #info System Configuration APIs are completed - Check Dependencies, configuration
15:08:50 <srao5> #info Cleanup APIs are completed.
15:09:34 <acmacm16> #info Al Morton
15:09:46 <srao5> #info Start-Test stability improvement Started.
15:13:14 <srao5> #info Kibana Dashboard for VSPERF Test-Status.... Under exploration.
15:14:54 <srao5> #topic VSPERF-CNTT F2F meeting.
15:18:50 <srao5> #info ETSI NFV Test WG Chairs is meeting with GSMA in preparation for F2F meeting.
15:20:38 <srao5> #info Al: Re-look Previous effort - ETSI INF-010
15:26:18 <srao5> #info How this RI will be provided? Possibility: A vendor may offer - A hardware/software vendors..
15:36:24 <srao5> #info Al: VSPERF should focus on "validating" Reference implementation - Running tests and confirming with the "defined" (in the profile) metrics.
15:38:25 <srao5> #info AL: VSPERF should focus on Validating Hardware reference implementation. Here Hardware really means hardware + minimal Software. Minimal = OS, Hypervisor, Container-engine, VSwitch, TestVNF, etc..
15:39:44 <srao5> #info If SDN Controller inclusion is expected - VSPERF can work towards that.
15:40:58 <srao5> #info Should VSPERF support in "Creating" Reference implementation?
15:44:41 <srao5> #info AL: we should be prepared to test it. Creating may not be its focus. Of course, we can contribute in terms of Low-Level configuration.
15:48:43 <srao5> #info Question: Once the Ref. Implementation is validated and Ready - Should VSPERF play role in (a) NVFI compliance, verification, and cerification of S/W and H/W (b) VNF compliance validation and cerification.
15:52:38 <acmacm16> #info GSMA is looking for per VNF-C and vNIC and vCPU
15:53:32 <acmacm16> #info what range of VNF-C should we test over? we currently test 1 or 2...
15:54:35 <acmacm16> #info  PVP throughput goes down when running PVVP
15:55:07 <srao5> #info PVVP with MemIf does not have this issue.
15:55:45 <acmacm16> #info we need the range of VNF scale to test. Per VNF-C performance will be different if the range is 20 or 50 VNF
16:03:02 <srao5> #info Take-away Points: (1) VSPERF play role in Testing and Validation of a Reference implementation (b) VSPERF can go beyond baremetal with used with other projects - Functest, YS, NFVBench.
16:04:42 <acmacm16> #info VNF Scale Ranges determined by Profile (S,M,L Tee-shirts), so we have three ranges to test, and someone must decide the range
16:09:46 <acmacm16> #info CNTT doc https://cntt-n.github.io/CNTT/doc/ref_model/chapters/chapter03.html#3.3.2
16:13:47 <srao5> #endmeeting