deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-44) Deltacloud daemon needs debug level verbosity options to allow effective diagnosis of communications problems
Date Wed, 21 Mar 2012 20:18:40 GMT


Ronelle Landy commented on DTACLOUD-44:

Looking at deltacloud git commit version 7e372dfca79c02a799046287e5936129216b781b, it looks
like Deltacloud does provider this log information in either the server trace or, in the case
of Conductor, /var/log/deltacloud-core.

For example, a timestamp trace of errors and other return codes captured in the server trace: - - [21/Mar/2012 12:30:36] "POST /api/instances?format=json HTTP/1.1" 500 130 5.8312 - - [21/Mar/2012 14:06:50] "GET /api/instances?format=xml HTTP/1.1" 500 7024 0.0394 - - [21/Mar/2012 14:09:19] "GET /api/instances?format=xml HTTP/1.1" 200 65 0.5734 - - [21/Mar/2012 15:28:05] "GET /api/instances HTTP/1.1" 401 8839 0.1051 - - [21/Mar/2012 15:28:05] "GET /api/instances HTTP/1.1" 401 8839 0.1076
RbVmomi::Fault:InvalidLogin: Cannot complete login due to an incorrect user name or password.

I emailed the JIRA reporter to ask if he agreed that Deltacloud now provides the requested
functionality. I am closing this JIRA as 'Fixed'. If there is still outstanding functionality
that is not available with the current Deltacloud version, please reopen this ticket or file
a new JIRA specific to the functionality requested.

> Deltacloud daemon needs debug level verbosity options to allow effective diagnosis of
communications problems
> -------------------------------------------------------------------------------------------------------------
>                 Key: DTACLOUD-44
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Justin Clift
>            Assignee: David Lutterkort
> At present, when communication problems seem to be occurring between Deltacloud and any
given Cloud provider, debugging them is very difficult/opaque.
> As a step towards making this practical to work with in the Real World, having deltacloudd
log (debug level) information to a log file would be beneficial.
> By "debug level" I'm meaning logging all communications to any given cloud provider (timestamped),
including sensitive info (usernames, passwords, etc), and also logging all return information
(status codes, data, etc).
> This debug level verbosity would not be something left on in most circumstances, as the
volume of data could be massive for some things (image transfers?), but some mechanism to
assist in debugging connection/weird problems is needed. Sooner rather than later.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message