Over the past couple of weeks I've walked a number of folks through
debugging when their devstack / tempest jobs fail, and how to get to the
fact that their patch may very well be the cause of the failure. It
became a quick realization that their is way too much tribal knowledge
in my head about how the whole system works, and there should be a
better way to get this info out to people.
If you've gone to a log listing in the past day, you'll see the first
attempt at that. Instead of putting this info in the wiki, we've put it
front and center on the log pages themselves. The theory being put
information directly where it's most needed. Samples of this are here:
http://logs.openstack.org/29184/8/gate/gate-tempest-devstack-vm-quantum/23537/
and here:
http://logs.openstack.org/29184/8/gate/gate-tempest-devstack-vm-quantum/23537/logs/
These are managed by the use of the ReadmeName stanza in apache as part
of the openstack-infra/config project, and the source for the files is
listed at the bottom of each of them.
These are by no ways complete, but hopefully a useful starting point. It
also means that first timers following the link will have an entry point
to getting to the bottom of issues found in the gate.
Help is always appreciated in fleshing these out with more tribal
knowledge, but it is a beginning.
-Sean
--
Sean Dague
http://dague.net
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
