remove v3 controller stub

[Brian Rosmaita]

The Mitaka release contained a stub controller to redirect calls from the experimental v3 API to the standalone Glare service. This is no longer required. Since the v3 API was clearly marked EXPERIMENTAL, it does not require a deprecation period. Further, this change would only affect deployments running the v3 API, which is very unlikely, as the standalone artifacts API is a bit different from v3, and hence anyone interested in artifacts is using Glare.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit a6740ac5e5277abb8ee3fe56fc18af8c0969c888
Author: Brian Rosmaita <email address hidden>
Date: Wed Dec 14 23:00:11 2016 -0500

    Remove v3 stub controller

    This patch removes the stub controller for v3 that was introduced
    in Mitaka when Glare became a standalone service. As the v3 API
    was always EXPERIMENTAL, this removal does not require a deprecation
    period. (Also, anyone interested in artifacts is using Glare, not
    the v3 API.)

    Change-Id: Ie16ba13c5970596eebf7b757c0712358c80f376e
    Closes-bug: #1650108

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/glance 14.0.0.0b3 development milestone.