Redis driver doesn't explicitly validate UUIDs

[Kurt Griffiths]

For claim and message IDs, as well as as client_uuids, the driver does not always validate that they are real UUIDs. This should not pose a problem, assuming redis-py sanitizes key names, but it would be good to do our own checking just to be certain.

[Flavio Percoco (flaper87)]

Should this be done as a falcon hook?

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Akanksha Srivastava (<email address hidden>) on branch: master
Review: https://review.openstack.org/166565
Reason: Uploaded by mistake. Dont review.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/164671
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=6c4bb628bee66c131150d696a61eb1f6e793a84a
Submitter: Jenkins
Branch: master

commit 6c4bb628bee66c131150d696a61eb1f6e793a84a
Author: Masaki Matsushita <email address hidden>
Date: Mon Mar 16 21:22:17 2015 +0900

    Validate UUIDs before the driver sends them

    Redis driver does not always validate UUIDs (claim ID, message ID
    and client_uuid). This commit introduces validation of them before the
    driver sends them.

    Closes-Bug: #1367024
    Change-Id: I08eaa7df1f6887224edd0a3324ee4e5db3f6c229