[
https://issues.apache.org/jira/browse/LIBCLOUD-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791543#action_12791543
]
Jeremy Orem commented on LIBCLOUD-3:
------------------------------------
From: http://github.com/cloudkick/libcloud/issues/unreads#issue/9/comment/88895
I'm now going through some back-and-forth with Rackspace about what I think is
a bug on their end. It's at a time like this that it would be really handy to
have a complete HTTP transcript I can give them. Then it doesn't really matter
if libcloud is "unsupported", as I can simply refer to the actual API
interactions. It's also possible to check those against the API docs, making it
easier to find problems with libcloud.
> Add debug mode, showing HTTP bodies
> -----------------------------------
>
> Key: LIBCLOUD-3
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-3
> Project: Libcloud
> Issue Type: New Feature
> Reporter: Jeremy Orem
>
> From: http://github.com/cloudkick/libcloud/issues/unreads#issue/9
> I am having a problem with the Rackspace code, which I think is a problem
> with Rackspace (they don't show backups as images in the API, even though you
> can use them through the web interface). But Rackspace doesn't necessarily
> support libcloud, so it'd be nice if I could show the actual HTTP transaction
> that happened, to show the image isn't listed.
> It would be nice if there was a "debug" option for the driver that would
> display all the transactions. Or maybe slightly more general, a "record"
> option, which would be an object that would be called with records of all the
> requests and responses (which I could hook up to print or whatever).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
