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 make the nova-next (formerly "placement" job [2])
use cinder v3 but that breaks down a bit when that job runs on
stable/newton where nova doesn't support cinder v3.
So when the cat woke me up at 3am I couldn't stop thinking that we
should just default "[cinder]/catalog_info" in nova.conf to cinderv3 in
Pike. Then CI on master will be running nova + cinder v3 (which should
be backward compatible with cinder v2). That way I don't have to mess
with marking a single CI job in master as using cinder v3 when by
default they all will.
We'll still want some nova + cinder v2 coverage and I initially though
grenade would provide that, but I don't think it will since we don't
explicitly write out the 'catalog_info' value in nova.conf during a
devstack run, but we could do that in stable/ocata devstack and then it
would persist through an upgrade from Ocata to Pike. There are other
ways to get that coverage too, that's just my first thought.
Anyway, I just remembered this and it was middle-of-the-night thinking,
so I'm looking to see if this makes sense or what is wrong with it.
[1] https://review.openstack.org/#/c/420201/
[2] https://review.openstack.org/#/c/431704/
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
