Discovery of Sahara API versions incorrectly requires authentication

[Jeremy Freudberg]

That's bad, because keystoneauth (which is the reference implementation of how to version discovery the right way) expects that it can discover versions without having to authenticate first.

It has to do with how our Paste pipeline works -- every request passes through keystonemiddleware regardless of path. We can tweak this!

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/536002
Committed: https://git.openstack.org/cgit/openstack/sahara/commit/?id=b1503b36c4441a07e5a842276a5fc7229d733ce3
Submitter: Zuul
Branch: master

commit b1503b36c4441a07e5a842276a5fc7229d733ce3
Author: Jeremy Freudberg <email address hidden>
Date: Sat Jan 20 03:25:21 2018 +0000

    Tweak Sahara to make version discovery easier

    Or at least, tweak Sahara to be more accomodating to keystoneauth's way
    of doing version discovery.

    * Don't require auth to do version discovery
    * Make project ID in URL optional for APIv1 (and also for APIv2, but
      don't go around advertising that... *wink*)

    Change-Id: Idb6f734aee26cab5bd629963a66ba01c92760864
    Closes-Bug: #1744350

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/sahara 8.0.0.0b3 development milestone.