Hello Tracy,
some of the problem I faced, to execute different nova cli(s), i required
to restart nova service every-time.
Nova service needs to fully start/realize, before debugging can start.
import pydev; works as break-point for debugger, needs to add at all the
places.
For ex: in case one wants to debug nova boot flow end-to-end.
needs to know, the exact code location to put break-point in
each service.
Regards,
Yatin
On Mon, Nov 25, 2013 at 10:43 PM, Tracy Jones <tjo...@vmware.com> wrote:
> Thanks Yatin - that is the change I am proposing in my patch
>
>
> On Nov 25, 2013, at 9:09 AM, yatin kumbhare <yatinkumbh...@gmail.com>
> wrote:
>
> Hi,
>
> http://debugopenstack.blogspot.in/
>
> I have done Openstack remote debugging with eclipse and pydev.
>
> only change is to exclude python thread library from monkey patch at
> service start up.
>
> Regards,
> Yatin
>
>
> On Mon, Nov 25, 2013 at 9:10 PM, Russell Bryant <rbry...@redhat.com>wrote:
>
>> On 11/25/2013 10:28 AM, Tracy Jones wrote:
>> > Hi Folks - i am trying to add a patch to enable remote debugging in the
>> > nova services. I can make this work very simply, but it requires a
>> > change to monkey_patching - i.e.
>> >
>> > eventlet.monkey_patch(os=False, select=True, socket=True,
>> thread=False,
>> > time=True, psycopg=True)
>> >
>> > I’m working with some folks from the debugger vendor (pycharm) on why
>> > this is needed. However - i’ve been using it with nova-compute for a
>> > month or so and do not see any issues which changing the
>> > monkey-patching. Since this is done only when someone wants to use the
>> > debugger - is making this change so bad?
>> >
>> > https://review.openstack.org/56287
>>
>> Last I looked at the review, it wasn't known that thread=False was
>> specifically what was needed IIRC> That's good progress and is a bit
>> less surprising than the change before.
>>
>> I suppose if the options that enable this come with a giant warning,
>> it'd be OK. Something like:
>>
>> WARNING: Using this option changes how Nova uses the eventlet
>> library to support async IO. This could result in failures that do
>> not occur under normal opreation. Use at your own risk.
>>
>> --
>> Russell Bryant
>>
>> _______________________________________________
>> 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
