Difference between revisions of "Manila/Debugging"
< Manila
m |
|||
| Line 3: | Line 3: | ||
1. Ensure your OpenStack environment has the pydevd library installed. This is distributed as an egg in the top level of the PyCharm installation directory; there are two separate eggs for Python 2.x and 3.x. For Python 2, just run "easy_install pycharm-debug.egg" to install it in your Python path. | 1. Ensure your OpenStack environment has the pydevd library installed. This is distributed as an egg in the top level of the PyCharm installation directory; there are two separate eggs for Python 2.x and 3.x. For Python 2, just run "easy_install pycharm-debug.egg" to install it in your Python path. | ||
| − | 2. Create a debug configuration in PyCharm. If PyCharm is running locally to OpenStack, create a local config: [[File:manila_debug_local.png|200px|thumb| | + | 2. Create a debug configuration in PyCharm. If PyCharm is running locally to OpenStack, create a local config: [[File:manila_debug_local.png|200px|thumb|right|Local debug config]] |
Revision as of 20:46, 23 June 2014
With the proposed changes in Manila, setting up source-level debugging should be straightforward. This page describes the process for PyCharm; feel free to enhance the content with other IDEs such as Eclipse/PyDev.
1. Ensure your OpenStack environment has the pydevd library installed. This is distributed as an egg in the top level of the PyCharm installation directory; there are two separate eggs for Python 2.x and 3.x. For Python 2, just run "easy_install pycharm-debug.egg" to install it in your Python path.
2. Create a debug configuration in PyCharm. If PyCharm is running locally to OpenStack, create a local config:
