solidfire drivers generate request id is not usable

[John Griffith]

The SolidFire driver generates a request-id for each API call by converting a UUID into an int. Unfortunately if you're using an "int" for request ID in the Solidfire API it actually needs to be limited to an int.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/36154
Committed: http://github.com/openstack/cinder/commit/723486b120f3b2cc106c94191e8de9dc0b4c185f
Submitter: Jenkins
Branch: master

commit 723486b120f3b2cc106c94191e8de9dc0b4c185f
Author: John Griffith <email address hidden>
Date: Mon Jul 8 19:22:34 2013 -0600

    SolidFire API RequestID is useless.

    The SolidFire API can take an int or a string for a request-id,
    when using an int however it needs to actually be a valid int.

    The driver currently was doing an int(uuid) which is too large and
    as a result get's truncated making it difficult or impossible to track
    request-ids.

    This patch chanes the generate request-id to form a hash of the uuid so
    that it can be tracked.

    Fixed bug: 1199198

    Change-Id: I38d5e3d189e679678898c329a9fa173a47853d47