You need to apply the other 2 network context patches from the reviews I sent out Ajay
Sent from my iPhone On Sep 5, 2014, at 2:25 AM, "masoom alam" <[email protected]<mailto:[email protected]>> wrote: http://paste.openstack.org/show/106297/ On Fri, Sep 5, 2014 at 1:12 PM, masoom alam <[email protected]<mailto:[email protected]>> wrote: Thanks Ajay I corrected this earlier. But facing another problem. Will forward paste in a while. On Friday, September 5, 2014, Ajay Kalambur (akalambu) <[email protected]<mailto:[email protected]>> wrote: Sorry there was typo in the patch should be @validation and not @(validation Please change that in vm_perf.py Sent from my iPhone On Sep 4, 2014, at 7:51 PM, "masoom alam" <[email protected]> wrote: Why this is so when I patched with your sent patch: http://paste.openstack.org/show/106196/ On Thu, Sep 4, 2014 at 8:58 PM, Rick Jones <[email protected]> wrote: On 09/03/2014 11:47 AM, Ajay Kalambur (akalambu) wrote: Hi Looking into the following blueprint which requires that network performance tests be done as part of a scenario I plan to implement this using iperf and basically a scenario which includes a client/server VM pair My experience with netperf over the years has taught me that when there is just the single stream and pair of "systems" one won't actually know if the performance was limited by inbound, or outbound. That is why the likes of http://www.netperf.org/svn/netperf2/trunk/doc/examples/netperf_by_flavor.py and http://www.netperf.org/svn/netperf2/trunk/doc/examples/netperf_by_quantum.py apart from being poorly written python :) Will launch several instances of a given flavor and then run aggregate tests on the Instance Under Test. Those aggregate tests will include inbound, outbound, bidirectional, aggregate small packet and then a latency test. happy benchmarking, rick jones _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sent from noir
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
