As a wrap up session to the QA track I want to discuss ways to increase debuggability in the gate. As our tooling gets more complicated, and parallel testing gets more rigorous, being able to understand the output of gate testing is more and more critical. We need to push towards a world where an issue is debuggable with first fail capture in the logs.

This will be a brain storm and wrap up session to enumerate some priorities on debuggability, changes to tempest, the gate, tools that understand the gate artifacts, and core projects that could get us a better debugging story.

*Log Harmonization between of services
	* Volunteers: Joe, sdague, chris buccella
	* Something that works - demonstrate crazy things in the logs
	* guidelines
	* debug vs debug_all

Logstash complexity

examples:
	* Glance has separate option to specify sqlalchemy log level instead of using oslo logging option for it

*Cross Service Ids
	* Volunteers: cyeoh, chris buccella
	* swalsh generating ceilometer notifications based on this - contingent on ceilometer working on the gate

*Replicating Gate Env locally
State of the art is devstack-gate README http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/README.rst#n100
break config variants out of code into localrcs

An output at the end of the run "to reproduce this do the following"


*Diagnostics API project on stackforge