Would the effort to do the following be substantial ? - Nova doing the intelligent thing (i.e. choosing the best one for the job) by default - An operator override (do what I tell you in the config file)
Examples where I would want to use the operator override are - If I upgrade Glance to the latest version, I may want to run with the v1 API for a bit and then do the upgrade to v2 at a later stage - In testing, I want to validate the latest Nova code against a v1 glance API running on the latest glance server code base Planning multi-component upgrades is tough and it would be good to have some overrides in the event that some features don't work quite as we want but still avoid a code roll back. Tim > -----Original Message----- > From: Russell Bryant [mailto:rbry...@redhat.com] > Sent: 17 October 2013 20:01 > To: OpenStack Development Mailing List > 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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
