Limit value None in the message controller in a pooled marconi deployment

[Prashanth Raghu]

Limit values are appearing as None in place of the default storage values provided in the storage driver when marconi is used in a pooled context.

Was observed in the : message and queue controllers.

[Allele Dev (alleledev)]

Does the affect the behavior of the message controller in a sharded context, i.e., is the user able to exceed the default limit or the configuration time limit?

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/102457
Committed: https://git.openstack.org/cgit/openstack/marconi/commit/?id=b3274e3857369b2cd29fbf00821863116ca905f9
Submitter: Jenkins
Branch: master

commit b3274e3857369b2cd29fbf00821863116ca905f9
Author: Nataliia Uvarova <email address hidden>
Date: Wed Jun 25 10:26:57 2014 +0300

    Make storage/pooling reflect storage/base

    Controllers wrappers for pooled context wasn't fully compatible with the
    APIs defined in storage/base. Order of parameters was different and
    default values was not specified or specified incorrectly. In
    particular in pooled setup default limits were None in message and claim
    controllers. This commit changes them to be the same as in non-pooled
    setup.

    Also tests for testing default limits were added.

    Change-Id: I2b83383975986179813df7a897d78852a532564e
    Closes-bug: #1324587