Glance needs a config option to limit the number of additional image locations

[Feilong Wang]

This is a similar bug as https://launchpad.net/bugs/1251518, https://launchpad.net/bugs/1252337 and https://launchpad.net/bugs/1252459, given the original concern of this issue is to avoid filling garbage for Glance db. So it's necessary to limit the number of image locations because image locations table has two TEXT(64k) column, 'value' and 'metadata'.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/64702
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=5f9831768461c34533ff93f32b31e095b57d82d1
Submitter: Jenkins
Branch: master

commit 5f9831768461c34533ff93f32b31e095b57d82d1
Author: Fei Long Wang <email address hidden>
Date: Sun Dec 29 17:18:58 2013 +0800

    Add config option to limit image locations

    This patch adds the image_location_quota config option. This allows
    a deployer to limit the number of image locations allowed on an image.
    The default value is 10. Users will only be able to update an image
    if the result of the transaction would be under this limit. This
    behavior is intended to be similar to 'quota_metadata_items' in Nova.

    We have implemented the same limit for image properties, members and tags,
    see:
    https://review.openstack.org/#/c/56981/
    https://review.openstack.org/#/c/59563/
    https://review.openstack.org/#/c/58056/

    docImpact
    Closes-Bug: #1259031

    Change-Id: I0e0033a1d11be267144e8e10b730bb6331263d4c