Open Stack

The problem there is that it takes (significant) time for the connection
attempt to time out - every cinder command taking several minutes is not
acceptable.

Obviously this depends on the network setup of the cloud - I can only talk
about the case we saw
On 24 Jun 2015 00:25, "Jeremy Stanley" <fungi at yuggoth.org> wrote:

> On 2015-06-23 08:49:55 -0700 (-0700), Mike Perez wrote:
> [...]
> > Cinder client asks Keystone to find a publicURL based on a version.
> > Keystone will gather data from the service catalog and ask Cinder for
> > a list of the public endpoints and compare. For the proxy cases,
> > Cinder is giving internal URLs back to the proxy and Keystone ends up
> > using that instead of the publicURL in the service catalog. As a
> > result, clients usually won't be able to use the internal URL and
> > rightfully so.
> [...]
>
> It seems like there would be an option #3: add a fallback behavior
> to cinderclient to try its old connection method if it fails to
> reach the "discovered" URL. I'm guessing there's some specific
> reason that's impossible, or it would have already been in the
> works?
> --
> Jeremy Stanley
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150624/1f39e3e7/attachment.html>