Glance needs a config option to limit the number of image members

[Brian Rosmaita]

Glance v2 allows users to put "members" on an image. There is no limit to the number of image members.

This is a (linear) DoS attack vector.

The fix for this should be done similar to the fix for https://bugs.launchpad.net/glance/+bug/1251518 to keep configuration consistent.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/59563
Committed: http://github.com/openstack/glance/commit/b13e10b5e594c2ad807006e10efdd6c941403d2b
Submitter: Jenkins
Branch: master

commit b13e10b5e594c2ad807006e10efdd6c941403d2b
Author: Alex Meade <email address hidden>
Date: Mon Nov 25 01:57:24 2013 +0000

    Add config option to limit image members

    This patch adds the image_member_quota config option. This allows a deployer
    to limit the number of image members allowed per image. The default value
    is 128, to be consistent with other quota defaults. Users will only be able
    to update an image if the result of the transaction would be under this limit.

    This is for both Glance v1 and v2

    Fixes bug 1252459
    docImpact

    Change-Id: I02f5e82ca4c4acf6cd7bc94f9b99086054a616c9