<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 11, 2017 at 11:29 AM, Matt Riedemann <span dir="ltr"><<a href="mailto:mriedemos@gmail.com" target="_blank">mriedemos@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2/11/2017 11:47 AM, John Griffith wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It seems like just moving Nova to V3 in Pike would alleviate quite a few<br>
snarls here. The fact that V3.0 is just pointing back to V2 for Cinder<br>
calls anyway I'm uncertain there's a huge downside to this. Nova +<br>
Cinder V2 coverage is only an entry point issue IIUC (V3.0 points to<br>
Cinder V2 API server calls anyway based on what I was looking at). So<br>
it's more an issue of cinderclient and what it's set up at no?<br>
Honestly, this is another one of those things we probably need to unwind<br>
together at PTG. The V3 Cinder thing has proven to be quite thorny.<br>
<br>
<br>
</blockquote>
<br></span>
Scott's nova patch to support cinder v3 is dependent on a python-cinderclient change for version discovery for min/max versions in the v3 API. Once that's released we just bump the minimum required cinderclient in global-requirements for pike and we should be good to go there.<br>
<br>
But overall yeah I like the idea of just defaulting to cinderv3 in Pike, as long as we can still get cinderv2 coverage in CI in master, which I think we can do via grenade jobs.</blockquote><div><br></div><div class="gmail_default" style="font-family:monospace,monospace">+1</div><div class="gmail_default" style="font-family:monospace,monospace"></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
-- <br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>