On 11/22/2013 09:07 PM, Matt Riedemann wrote:
On Friday, November 22, 2013 5:52:17 PM, Russell Bryant wrote:
On 11/22/2013 06:01 PM, Christopher Yeoh wrote:
On Sat, Nov 23, 2013 at 8:33 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com mailto:mrie...@linux.vnet.ibm.com wrote:
...
On Fri, 2013-11-22 at 20:07 -0600, Matt Riedemann wrote:
On Friday, November 22, 2013 5:52:17 PM, Russell Bryant wrote:
On 11/22/2013 06:01 PM, Christopher Yeoh wrote:
On Sat, Nov 23, 2013 at 8:33 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com mailto:mrie...@linux.vnet.ibm.com wrote:
On Thursday, November 21, 2013 9:56:41 AM, Matt Riedemann wrote:
On 11/3/2013 5:22 AM, Joe Gordon wrote:
On Nov 1, 2013 6:46 PM, John Garbutt j...@johngarbutt.com
mailto:j...@johngarbutt.com wrote:
On 29 October 2013 16:11, Eddie Sheffield
eddie.sheffi...@rackspace.com
On Sat, Nov 23, 2013 at 8:33 AM, Matt Riedemann
mrie...@linux.vnet.ibm.comwrote:
...
21:51:42 dolphm i just hope that the version discovery mechanism is
smart enough to realize when it's handed a versioned endpoint, and happily
run with that
...
21:52:00 dolphm (by calling that endpoint and
On 11/3/2013 5:22 AM, Joe Gordon wrote:
On Nov 1, 2013 6:46 PM, John Garbutt j...@johngarbutt.com
mailto:j...@johngarbutt.com wrote:
On 29 October 2013 16:11, Eddie Sheffield
eddie.sheffi...@rackspace.com mailto:eddie.sheffi...@rackspace.com
wrote:
John Garbutt j...@johngarbutt.com
Hi all,
I see you are discussing that enabling glance API in Nova using Keystone
catalog. I think there is one topic related to it that needs to be
mentioned here. Hope we can take consideration. Current, Nova use config
value glance_api_servers to talk to Glance, but there is one limitation
On Nov 1, 2013 6:46 PM, John Garbutt j...@johngarbutt.com wrote:
On 29 October 2013 16:11, Eddie Sheffield eddie.sheffi...@rackspace.com
wrote:
John Garbutt j...@johngarbutt.com said:
Going back to Joe's comment:
Can both of these cases be covered by configuring the keystone
catalog?
On 29 October 2013 16:11, Eddie Sheffield eddie.sheffi...@rackspace.com wrote:
John Garbutt j...@johngarbutt.com said:
Going back to Joe's comment:
Can both of these cases be covered by configuring the keystone catalog?
+1
If both v1 and v2 are present, pick v2, otherwise just pick what is
Mark Washenberger mark.washenber...@markwash.net said:
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I am not a fan of all the specific talk to glance code we
On Wed, Oct 30, 2013 at 9:04 AM, Eddie Sheffield
eddie.sheffi...@rackspace.com wrote:
Mark Washenberger mark.washenber...@markwash.net said:
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Going back to Joe's comment:
Can both of these cases be covered by configuring the keystone catalog?
+1
If both v1 and v2 are present, pick v2, otherwise just pick what is in
the catalogue. That seems cool. Not quite sure how the multiple glance
endpoints works in the keystone catalog, but
I haven't look at the review proposed yet one week ago, but some time ago,
we needed something similar for Ironic (nova, ironic and cinder share
almost the same code for the glance driver), but didn't make it.
In case someone wants to take a look:
https://review.openstack.org/#/c/33327/
I'll
John Garbutt j...@johngarbutt.com said:
Going back to Joe's comment:
Can both of these cases be covered by configuring the keystone catalog?
+1
If both v1 and v2 are present, pick v2, otherwise just pick what is in
the catalogue. That seems cool. Not quite sure how the multiple glance
I am not a fan of all the specific talk to glance code we have in
nova, moving more of that into glanceclient can only be a good thing.
For the XenServer itegration, for efficiency reasons, we need glance
to talk from dom0, so it has dom0 making the final HTTP call. So we
would need a
I'd just like to echo Tim Bell's comments.
From a rolling upgrade perspective where you have Glance nodes behind
a load balancer we'd probably need a way to manually 'hold back' on v1
until all nodes are upgraded to support v2 aswell.
(Otherwise your auto-discovery may hit an upgraded node
The following blueprint has been proposed for Nova:
https://blueprints.launchpad.net/nova/+spec/use-glance-v2-api
It proposes a new config option for Nova to allow choosing whether Nova
should use v1 or v2 of the Glance API. I'd like to know if we can do
this without a config option.
Can
...@redhat.com
Sent: Thursday, October 17, 2013 2:00pm
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova
The following blueprint has been proposed for Nova:
https://blueprints.launchpad.net/nova
On 10/17/2013 03:12 PM, Eddie Sheffield wrote:
I don't oppose having the version autodiscovered. But I do feel the option
should be available to override if desired. I've had many problems with over
the years with autoconfiguring systems not doing what I need to be willing to
depend on them
18 matches
Mail list logo