Open Stack

Hi Aimee,

Thanks for digging into it!

Here¹s my understanding of our conventions (and I¹m happy to hear from
others).

a. If you think it¹s just a straightforward change with zero to minimal
impact on architecture, users, and devs, then it makes sense to file a bug
or just submit a patch.
b. If you think it warrants deeper discussion in terms of design, impact,
etc., then the process is to create a spec and associated blueprint. See
this wiki for more details:
https://wiki.openstack.org/wiki/Blueprints#Spec_.2B_Blueprints_lifecycle

In case (b), the change should target the O-cycle because we¹re past
feature-freeze in N.
In case (a), it may make sense to get it in during the N-cycle if it has
minimal impact and will help us in the N-cycle QA process.

My guess is we¹re in case (a) because we can make sure changes have no
impact without a special flag. But I¹d also like to understand a little
better the impact of eventlet.monkey_patch(thread=False) as done in the
Keystone patch (https://review.openstack.org/#/c/18404/3/bin/keystone-all).

Enjoy the time holidays!

On 9/1/16, 11:45 AM, "Aimee Ukasick" <aimeeu.opensource at gmail.com> wrote:

>HI all - I've been trying to configure remote debugging with PyCharm
>and DevStack. It looks like some tiny modifications need to be made to
>the Congress code (3-4 files) to support remote debugging via pydevd.
>
>As far as I can tell, support has been added to Keystone, Glance,
>Nova, and Manilla (and I'm sure others).
>
>Keystone patch: https://review.openstack.org/#/c/18404/3
>Glance patch: https://review.openstack.org/#/c/18748/5
>
>I think it would be very beneficial to support remote debugging, and
>I'm willing to implement the changes needed. Should I create a bug for
>this or draft a blueprint?
>
>I'm out of office 2-5 Sept for the US Labor Day holiday, so I could
>start on this on 6 Sept.
>
>As always, I appreciate all your comments.
>
>Thanks.
>
>aimee
>
>irc:aimeeu
>
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev