Well, for a non-interactive view of things, you can use the
openstack.common.report functionality. It's currently integrated into Nova,
and I believe that the other projects are working to get it integrated as well.
To use it, you just send a SIGUSR1 to any Nova process, and a report of the
current stack traces of threads and green threads, as well as the current
configuration options, will be dumped.
It doesn't look like exactly what you want, but I figured it might be useful to
you anyway.
Best Regards,
Solly Ross
- Original Message -
From: Chris Friesen chris.frie...@windriver.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Wednesday, March 12, 2014 12:47:32 PM
Subject: [openstack-dev] any recommendations for live debugging of openstack
services?
Are there any tools that people can recommend for live debugging of
openstack services?
I'm looking for a mechanism where I could take a running system that
isn't behaving the way I expect and somehow poke around inside the
program while it keeps running. (Sort of like tracepoints in gdb.)
I've seen mention of things like twisted.manhole and
eventlet.backdoor...has anyone used this sort of thing with openstack?
Are there better options?
Also, has anyone ever seen an implementation of watchpoints for python?
By that I mean the ability to set a breakpoint if the value of a
variable changes. I found
https://sourceforge.net/blog/watchpoints-in-python/; but it looks
pretty hacky.
Thanks,
Chris
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
