Open Stack

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 100% without a manual override available if at all possible. I'm thinking particularly for testing or upgrade evaluation scenarios. For example, you want to turn on v2 in glance and evaluate it for a bit before committing to using it for all of your nova nodes.

The current patch also had a couple of comments from Dan Prince and Chris Behrens early on when this was brought up there supporting the use of a config value.

From the implementation side of things, to do this properly would require some changes to the glanceclient to allow querying of available versions. Lacking that ability currently is one reason this is currently a config value. Once the client supports this, the nova side change would likely be quite small.

Might I propose a compromise?

1) For the VERY short term, keep the config value and get the change otherwise reviewed and hopefully accepted.

2) Immediately file two blueprints:
   - python-glanceclient - expose a way to discover available versions
   - nova - depends on the glanceclient bp and allowing autodiscovery of glance version
            and making the config value optional (tho not deprecated / removed)

Thanks,

Eddie Sheffield

-----Original Message-----
From: "Russell Bryant" <rbryant at redhat.com>
Sent: Thursday, October 17, 2013 2:00pm
To: "OpenStack Development Mailing List" <openstack-dev at 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/+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 Nova just discover which versions and pick one (v2) ?  And if you
don't like the way Nova picks one, a deployer can just only expose one
of the APIs on the API endpoint that Nova uses.

Thoughts?

-- 
Russell Bryant

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev