On Wed, Oct 19, 2016 at 2:27 PM, Brian Curtin <br...@python.org> wrote: ...
> > This started back in August when it came up that we didn't know where > that Keystone v3 endpoint was. After talking with a few people, Steve > Martinelli mentioned that at least as of then, hitting the unversioned > endpoint was the way to solve that. It being unlisted anywhere was > something for me to figure out (via that path manipulation from the > given v2), but it was later mentioned that ideally they would like to > have unversioned endpoints in the catalog anyway. devstack now sets up the identity/keystone endpoints as unversioned. So you get an endpoint with "http://192.168.122.102:5000"; for example. So this is what we're testing with now and you're lucky if a versioned endpoint works at all ;). > I'm talking to Steve > now and perhaps I took that too far in extrapolating which direction > things were going in reality, but it was a solution that had to be > undertaken nonetheless and was seen as the best way forward at the > time. It's also the only one that mostly works at the moment. > > In the end, I'll take listing major versions as long as it's accurate > and complete, but I'll also take listing the service root even if it > means an extra request for me to determine those versions. > > -- - Brant
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
