add retry support to python-quantumclient

[dan wendlandt]

This was already done for melange: https://review.openstack.org/#change,4027

A similar mechanism can be used for Quantum

[Maru Newby (maru)]

A few questions:

 - The melange change is for nova. Is this bug intended to fix nova as well?
 - The melange change was to was nova/network/quantum/melange_connection.py. Should the quantum change target nova/network/quantum/quantum_connection.py or some other module?

[dan wendlandt (danwent)]

It actually might be better to add configurable retry support to the Quantum client library itself: https://github.com/openstack/python-novaclient .

Currently, QuantumManager in Nova has its own copy of the Quantum client, but we'll remove that early in Folsom and replace it with a dependency on python-quantumclient. Would be good to add support to the client lib itself, then add a flag to nova to pass to the client lib.

Adding it to the client lib also means that other code using the client lib can benefit from it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/4847

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/4847
Committed: http://github.com/openstack/python-quantumclient/commit/36fd3ac6c12b3b786c5a7d8fa958b523a7af111c
Submitter: Jenkins
Branch: master

commit 36fd3ac6c12b3b786c5a7d8fa958b523a7af111c
Author: Maru Newby <email address hidden>
Date: Fri Mar 2 15:44:51 2012 -0800

    Add retry support to the quantum client.

     * Based on the retry support in nova's melange_connection
       and glance
     * Retry configuration is defined during Client instantiation and
       only applied to idempotent GET requests
     * Updated all api methods to call http method helpers (delete/get/post/put)
       rather than do_request to ensure consistent behavoir for a given http
       method.
     * Fixed bug in quantum.common.exceptions.QuantumClientException that
       was unnecessarily overriding class's 'message' attribute.
     * Resolves bug 937379

    Change-Id: Iab4e2ccf97937502ee0df58dba1e2dca30a36df8