/v1 returns 404, should maybe be json links

[Chris Dent]

A request to /v1 results in a 404 even though it is on the path to the total API. It might be better to have it returns a json representation of the resources "below" v1 for the sake of discoverability.

(A reasonable counter would be "URIs aren't hierarchical paths, you've asked for something that doesn't exist, you should get a 404". Which way to we want to go? Friendly to people exploring or "just use a client, dammit"?)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/210241
Committed: https://git.openstack.org/cgit/openstack/gnocchi/commit/?id=c8fb2af7b93620ab4cd675d95e41234f56a467b5
Submitter: Jenkins
Branch: master

commit c8fb2af7b93620ab4cd675d95e41234f56a467b5
Author: Mehdi Abaakouk <email address hidden>
Date: Fri Aug 7 09:28:48 2015 +0200

    rest: Add links to /v1 endpoint

    This change adds links to /v1 endpoint and
    return 200 instead of 400

    Change-Id: I41a09a12a53d33cbcdd38c27e6f367ee2b4d5e79
    Closes-bug: #1424627