Glance v2 API changes its behavior based on the is_public filter even tho that is not a valid optins in v2.

[John Bresnahan]

The v2 API changed its filter options from accepting the is_public filter to the visibility option. However, when the index request is received with the is_public= query parameter it alters the behavior of the service.

The v2 API should validate all parameters and throw an error if any invalid parameters are received.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit d8e3f873e01280d49602ce87bed4d1e08ff07640
Author: Mark J. Washenberger <email address hidden>
Date: Fri Mar 22 10:59:28 2013 -0700

    Make is_public an argument rather than a filter.

    There is disagreement between the v1 api and v2 api about what an
    'is_public' filter ought to mean. Version 1 uses 'is_public'
    to filter whether or not image.is_public == True or False. Version 2
    uses 'visibility' for this purpose. But in addition, it is theoretically
    possible that 'is_public' is a valid property filter in v2.

    With this change, v1 can pass is_public in as an argument to
    image_get_all. V2 will continue to pass is_public through filters.

    fixes bug: 1157988
    fixes bug: 1154760

    Change-Id: I716cb8b4f207f8526125ed360f5a24a6630c1e67