Unhandled Exception Trace in logs from taskflow when reqesting volume create with invalid (non-int or zero) size

[John Griffith]

Good dsvm-full runs have c-api logs full of this:
http://logs.openstack.org/24/121224/1/gate/gate-tempest-dsvm-full/c4e6121/logs/screen-c-api.txt.gz#_2014-09-17_20_16_12_507

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by John Griffith (<email address hidden>) on branch: master
Review: https://review.openstack.org/122276
Reason: Seems hub isn't pulling in the latest somehow, abandoning and trying from a fresh clone

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/122306
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=7ed28d1c1eea6f6394a412b6a6634a7eb9585753
Submitter: Jenkins
Branch: master

commit 7ed28d1c1eea6f6394a412b6a6634a7eb9585753
Author: John Griffith <email address hidden>
Date: Wed Sep 17 21:16:18 2014 -0600

    Verify requested size in volume.api create

    Currently we're not checking that the input value requested
    for size on volume create is valid, but taskflow portion of
    the code expects it to be and as a result when it receives invalid
    input we litter the logs with Trace messages.

    This patch adds a check that verifies that if we pass in a
    size to create_volume in the volume.api that it is in fact
    an int or a string representation of an int.

    Worst commit ever

    Change-Id: I81bf515360eacf63e6f3cdb672ec7f37001aa4fb
    Closes-Bug: 1370773