On 08:49 Jun 23, Mike Perez wrote:
There was a bug raised [1] from some large deployments that the Cinder
client 1.2.0 and beyond is not working because of version discovery.
Unfortunately it's not taking into account of deployments that have a
proxy.
Cinder client asks Keystone to find a
On Mon, Jun 29, 2015 at 11:58 PM, Duncan Thomas duncan.tho...@gmail.com
wrote:
We already have an environment variable for version... 'auto'?
On 30 Jun 2015 07:57, John Griffith john.griffi...@gmail.com wrote:
On Mon, Jun 29, 2015 at 8:54 PM, Jay Bryant
jsbry...@electronicjungle.net
Sorry, I don't think I was entirely clear with my proposal - I meant that
we release a new current that will default to the old behavior, but allow
the new behavior to be tested by explicitly choosing the value 'auto'. This
allows people to test their config with version discovery, without
We already have an environment variable for version... 'auto'?
On 30 Jun 2015 07:57, John Griffith john.griffi...@gmail.com wrote:
On Mon, Jun 29, 2015 at 8:54 PM, Jay Bryant jsbry...@electronicjungle.net
wrote:
I too would prefer option 2. Would rather do the pack ports than remove
the
I too would prefer option 2. Would rather do the pack ports than remove the
functionality.
Jay
On Wed, Jun 24, 2015 at 9:40 AM Gorka Eguileor gegui...@redhat.com wrote:
On Tue, Jun 23, 2015 at 08:49:55AM -0700, Mike Perez wrote:
There was a bug raised [1] from some large deployments that the
On Mon, Jun 29, 2015 at 8:54 PM, Jay Bryant jsbry...@electronicjungle.net
wrote:
I too would prefer option 2. Would rather do the pack ports than remove
the functionality.
Jay
On Wed, Jun 24, 2015 at 9:40 AM Gorka Eguileor gegui...@redhat.com
wrote:
On Tue, Jun 23, 2015 at 08:49:55AM
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
Mike Perez wrote:
Two options:
1) Revert version discovery which was introduced in Kilo for Cinder client.
2) Grant exception on backporting [4] a patch that helps with this
problem, and introduces a config option that does not change default
behavior. I'm also not sure if this should be
On 2015-06-24 09:01:51 +0300 (+0300), Duncan Thomas wrote:
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.
[...]
Another silly idea from an end user of cinderclient here, but try
both
On 24 June 2015 at 14:34, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-06-24 09:01:51 +0300 (+0300), Duncan Thomas wrote:
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.
[...]
On Tue, Jun 23, 2015 at 08:49:55AM -0700, Mike Perez wrote:
There was a bug raised [1] from some large deployments that the Cinder
client 1.2.0 and beyond is not working because of version discovery.
Unfortunately it's not taking into account of deployments that have a
proxy.
A little bit
On 24 June 2015 at 16:42, Dave Walker em...@daviey.com 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
There was a bug raised [1] from some large deployments that the Cinder
client 1.2.0 and beyond is not working because of version discovery.
Unfortunately it's not taking into account of deployments that have a
proxy.
Cinder client asks Keystone to find a publicURL based on a version.
Keystone
[mailto:thin...@gmail.com]
Sent: 23 June 2015 16:50
To: OpenStack Development Mailing List
Cc: Jesse Keating
Subject: [openstack-dev] [cinder][stable] Cinder client broken in Juno
There was a bug raised [1] from some large deployments that the Cinder
client 1.2.0 and beyond is not working
On 06/23/2015 11:49 AM, Mike Perez wrote:
There was a bug raised [1] from some large deployments that the Cinder
client 1.2.0 and beyond is not working because of version discovery.
Unfortunately it's not taking into account of deployments that have a
proxy.
Cinder client asks Keystone to
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
My first choice here is to revert the version discovery. However, that may be
too disruptive. If it is too disruptive then the back port patch is the right
approach.
In either case this is unfortunate.
Sent via mobile
On Jun 23, 2015, at 12:30, Monty Taylor mord...@inaugust.com wrote:
17 matches
Mail list logo
