barbican resource calls fail with 404

[Steve Heyman]

Running CloudCafe tests, 189 failures due to a bug introduced in:

   Barbican should not do rbac on version api call
   Closes-Bug: #1290445

   Change-Id: Idcd52600542b017f54c25a75ec0ab37348eb109d

The version call is correct, but all others end up with double "/v1" on the URL which results in a 404.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/82623
Committed: https://git.openstack.org/cgit/stackforge/barbican/commit/?id=b347eb4f052eaac81a82f16cc9a523069e9eed66
Submitter: Jenkins
Branch: master

commit b347eb4f052eaac81a82f16cc9a523069e9eed66
Author: Douglas Mendizabal <email address hidden>
Date: Mon Mar 24 16:50:52 2014 -0500

    Remove v1 from the falcon app route

    This bug was introduced by a recent change
    "Barbican should not do rbac on version api call"
    Where the main barbican app was split up into two falcon apps,
    one for the version resource, and another for the rest of the
    calls.

    In the paste file, the latter app was mounted on 'v1' but
    because the routes in the falcon app also map to 'v1' this resulted
    in all calls being routed to 'v1/v1/{tenant}/...'

    This change removes the routes from the app, so that only the
    'v1' in the paste configuration is mapped, which fixes the
    double v1 route.

    Change-Id: I05746f11d262ec7aa4f60aeb44e41217e8bc8a44
    Closes-Bug: #1296969