Alec,
Thanks for sharing the inputs. Actually, we discussed the second approach
(rather, a variation of the proposed approach)
1. using Test-Steps feature in VSPERF, and attempting to ‘stop’ the TGen
when an anomaly is detected.
2. using Interface-counters
But, what you have mentioned
Sorry I could not attend this morning. In general, I won’t be able to make it
regularly due to conflicts at this time slot (Wed 8am).
Because of TZ differences and other priorities for each of us, I think what
would help is to track better the progress of various tasks, either through
gerrit
Meeting Minutes can be found here:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-01-17-16.02.html
Thanks for the interesting discussion on long-duration tests.
Next week we will be discussing Traffic-Profile in VSPERF - Current and Future.
Alec, if
Hi All,
Agenda for this week's meeting:
1. Development Update.
2. Discussion - Topic: VSPERF-Long Duration Testing
Meeting minutes
* WW51
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-01-10-16.00.html
* WW50
