dbf754655f
For compliance with the Project Testing Interface [1] as described in [2] [1] https://governance.openstack.org/tc/reference/project-testing-interface.html [2] http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html doc8 command is dropped from docs tox envs. So this affect nothing and run in PEP8. Related-Bug: #1765348 Depends-On: Icc7fe3a8f9716281de88825e9d5b2fd84de3d00a Change-Id: Idf9a16111479ccc64004eac9508da575822a3df5
1.9 KiB
Using Kolla For OpenStack Development
Kolla-ansible can be used to deploy containers in a way suitable for doing development on OpenStack services.
Note
This functionality is new in the Pike release.
Heat was the first service to be supported, and so the following will use submitting a patch to Heat using Kolla as an example.
Only source containers are supported.
Warning
Kolla dev mode is intended for OpenStack hacking or development only. Do not use this in production!
Enabling Kolla "dev mode"
To enable dev mode for all supported services, set in
/etc/kolla/globals.yml:
kolla_dev_mode: trueTo enable it just for heat, set:
heat_dev_mode: trueUsage
When enabled, the source repo for the service in question will be
cloned under /opt/stack/ on the target node(s). This will
be bind mounted into the container's virtualenv under the location
expected by the service on startup.
After making code changes, simply restart the container to pick them up:
docker restart heat_apiDebugging
remote_pdb can be used to perform debugging with Kolla
containers. First, make sure it is installed in the container in
question:
docker exec -it -u root heat_api pip install remote_pdbThen, set your breakpoint as follows:
from remote_pdb import RemotePdb
RemotePdb('127.0.0.1', 4444).set_trace()Once you run the code(restart the container), pdb can be accessed
using socat:
socat readline tcp:127.0.0.1:4444Learn more information about remote_pdb.