On 24 June 2015 at 16:42, Dave Walker <[email protected]> wrote: > > As Jeremy points out, I fail to see why fallback default behaviour > cannot be used.. Attempt to use version discovery feature, if fail - > fall back to legacy behaviour.. > > What are the issues associated with this? >
So the issue is that for pre-kilo deployments that use a load-balancer (or kilo+ deployments that use a load balancer and haven't set the correct config option to the address of their load balancer) the version discovery URL given out by cinder API points to a node behind the load balancer. Depending on how this node is firewalled (drop packets .v. send reset), an attempt to connect to this URL can take a long time to timeout. I *think* we can get the desired behaviour by looking at the entry in the catalogue, and if it has a trailing version number then don't do discovery, but I might be wrong... -- Duncan Thomas
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
