Regards _Sugesh From: Daniele Di Proietto [mailto:diproiet...@ovn.org] Sent: Wednesday, May 25, 2016 9:38 PM To: Chandran, Sugesh <sugesh.chand...@intel.com> Cc: discuss <discuss@openvswitch.org> Subject: Re: [ovs-discuss] OVS-DPDK usability debug-tool script
Hi Sugesh, Thanks for working on this, I think this is going to be very useful. You may want to take a look at ovs-bugtool (in utilities/bugtool), it performs many of the tasks you're mentioning. It should be easily extendable with plugins, I can imagine a few DPDK (or OVS-DPDK) specific. What do you think? [Sugesh] Hi Daniele, I was not aware about the bugtool before, so thank you for the information. I tried out the bug tool locally and as you mentioned, we could definitely add OVS-DPDK relevant plug-ins to it than writing a new script. A couple of questions about the tool, 1) It doesn’t support OVS custom installation/ovs-run from the source tree. I feel it would be great having this support as well, so that developers can also make use of the tool. What do you think?? 2) Currently the tool has to be invoked manually by user. What about trigger it when the ovs-vswitchd /pmd thread crashes. It would be nice if we can add the core dump as well along with the current set of information. Any suggestions/comments? Daniele 2016-05-24 14:05 GMT-07:00 Chandran, Sugesh <sugesh.chand...@intel.com<mailto:sugesh.chand...@intel.com>>: Hi, I am planning to write a usability debug-tool script for OVS-DPDK. The script can collect and report all the relevant system information that can be used to debug most of the possible OVS-DPDK issues remotely. A basic implementation of the script and a sample dump-log file produced by the script are attached with this mail for a reference. Its also possible to extend the scope of the script to use in the event of OVS crash for collecting core dump along with all the relevant system information. The produced log-file information is really helpful to debug any misconfiguration/hardware/performance issues easily without so many mail interactions. Please let me know comments/suggestions/inputs on this proposal. Regards _Sugesh _______________________________________________ discuss mailing list discuss@openvswitch.org<mailto:discuss@openvswitch.org> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
