incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sang-Min Park <sang-min.p...@eucalyptus.com>
Subject Re: Debugging communication between Deltacloud and specific providers
Date Sat, 28 May 2011 12:12:36 GMT
Hi Justin,
Actually I'd use tcpdump as it worked pretty well for me. Try:
tcpdump -i eth0 -A -s 4096 -l 'tcp port [EC2 PORT #]'

On 5/28/11, David Lutterkort <lutter@redhat.com> wrote:
> On Sat, 2011-05-28 at 06:42 +1000, Justin Clift wrote:
>> Hi guys,
>>
>> Is there a way to turn on debug level logging verbosity
>> for the deltacloud daemon?  Trying to see what is actually
>> being sent to a cloud provider we're having trouble with (EC2),
>> and what is being returned. (ie ssl errors, error messages in
>> general, whatever)
>
> The Deltacloud code itself doesn't have any hooks to turn up logging;
> for EC2 specifically, we use the aws gem[1] - that might give you some
> ways to see in more details what's happening.
>
>> *Might* be able to use something like tcpdump, but that
>> seems pretty overkill and I'm not personally all that
>> familiar with it these days.
>>
>> Ideas?
>
> I'd use a reverse HTTP proxy and just turn logging on it up all the way
> to 11. Point the proxy at one of the Amazon URL's (e.g.,
> ec2.us-east-1.amazonaws.com) and then set the API_PROVIDER env variable
> to the URL of your proxy. Sadly, you can't provide URL's for ec2, s3 and
> elb in one fell swoop with this. We should look into enhancing the drive
> to support this.
>
> David
>
>
>

Mime
View raw message