Open Stack

On Mon, Feb 3, 2014 at 1:50 PM, Adam Young <ayoung at redhat.com> wrote:
>
> HACK:  In a new client, look at the URL.  If it ends with /v2.0, chop it
> off and us the substring up to that point.
>
> Now, at this point you are probably going:  That is ugly, is it really
> necessary?  Can't we do something more correct?
>

At this point I think we are stuck with hard-coding some legacy
compatibility like this for the near future.  Fortunately Identity is an
easy one to handle, Compute is going to be a #$^%! as the commonly
documented case has a version not at the end.

I've been playing with variations on this strategy and I think it is our
least bad option...

Can we accept that this is necessary, and vow to never let this happen
> again by removing the versions from the URLs after the current set of
> clients are deprecated?
>

+1

There is another hack to think about:  if public_endpoint and/or
admin_endpoint are not set in keystone.conf, all of the discovered urls use
localhost: http://localhost:8770/v2.0/.  Discovery falls over aga

I don't know how common this is but I have encountered it at least once or
twice.  Is this the only place those config values are used?  It seems like
a better default could be worked out here too;  is 'localhost' ever the
right thing to advertise in a real-world deployment?

dt

-- 

Dean Troyer
dtroyer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140203/365d266c/attachment.html>