eucalyptus/eutester — Issue #10: Create a standard set of debug tools available when tests fail
Author: mchua
Created: 2012-01-26 22:36:29+00:00
State: open

When a eutester test fails, we need to provide a standard set of debugging tools back to the user. This debug info should include as much as is necessary to find the possible cause of the behavior. Currently, the Eutester class provides a very basic framework for this, but we'd like to expand it.

Some feature ideas for the debug tools set (not the final list):

* grep (already implemented)
* euca-describe-* (get a listing of all resources in the system)
* get_all_everything in boto
* get logs
* get topology
* get distro
* get build information
* get environment (cpu, mem, etc)
* euca-describe-everything
* get test script used
* self replicating code
* yum
* tar
* graceful error messages (for instance, some tools may only work with root privs -- so we need a nice "you don't have the privs to do that" message for non-root users, instead of spewing gibberish.)

So step 1 is presumably to figure out what the final list is. :) We may need to break this into separate tickets if implementing some of these turn out to be less trivial than others.