Re: [openstack-dev] [nova][cinder] Should nova just default to use cinder v3 in Pike?

2017-02-11 Thread John Griffith
On Sat, Feb 11, 2017 at 11:29 AM, Matt Riedemann wrote: > On 2/11/2017 11:47 AM, John Griffith wrote: > >> >> It seems like just moving Nova to V3 in Pike would alleviate quite a few >> snarls here. The fact that V3.0 is just pointing back to V2 for Cinder >> calls anyway

Re: [openstack-dev] [nova][cinder] Should nova just default to use cinder v3 in Pike?

2017-02-11 Thread Matt Riedemann
On 2/11/2017 11:47 AM, John Griffith wrote: It seems like just moving Nova to V3 in Pike would alleviate quite a few snarls here. The fact that V3.0 is just pointing back to V2 for Cinder calls anyway I'm uncertain there's a huge downside to this. Nova + Cinder V2 coverage is only an entry

Re: [openstack-dev] [nova][cinder] Should nova just default to use cinder v3 in Pike?

2017-02-11 Thread John Griffith
On Fri, Feb 10, 2017 at 1:33 PM, Matt Riedemann wrote: > While talking about [1] yesterday and trying to figure out how to > configure nova to use cinder v3 in the CI jobs in Pike, things got a bit > messy from the CI job configuration perspective. > > My initial plan was to