Open Stack

On 6/8/2016 6:50 AM, Sean Dague wrote:
> On 06/07/2016 04:55 PM, Matt Riedemann wrote:
>> I tested the glance v2 stack (glance v1 disabled) using a devstack
>> change here:
>>
>> https://review.openstack.org/#/c/325322/
>>
>> Now that the changes are merged up through the base nova image proxy and
>> the libvirt driver, and we just have hyper-v/xen driver changes for that
>> series, we should look at gating on this configuration.
>>
>> I was originally thinking about adding a new job for this, but it's
>> probably better if we just change one of the existing integrated gate
>> jobs, like gate-tempest-dsvm-full or gate-tempest-dsvm-neutron-full.
>>
>> Does anyone have an issue with that? Glance v1 is deprecated and the
>> configuration option added to nova (use_glance_v1) defaults to True for
>> compat but is deprecated, and the Nova team plans to drop it's v1 proxy
>> code in Ocata. So it seems like changing config to use v2 in the gate
>> jobs should be a non-issue. We'd want to keep at least one integrated
>> gate job using glance v1 to make sure we don't regress anything there in
>> Newton.
>
> Honestly, I think we should take the Nova defaults (which will flip to
> v2 shortly) and move forward. v1 usage in Nova will be deprecated in a
> week. It will default to v2 for people in Newton and they will have to
> manually change it to go back. And because we did the copy / paste
> approach instead of common dynamic code, the chances for a v1 regression
> that is not caught by our unit tests is very very small. It's basically
> frozen code.
>
> And we're going to delete the v1 code paths entirely in September. By
> the time anyone deploys the Newton code the master v1 code will be
> deleted. And our answer is going to be move to v2 for everyone.
>
> It doesn't make sense to me to drive up the complexity by testing both
> paths. We'll have a new tested opinionated default that we lead with.
>
> 	-Sean
>

I'm OK with making it the default stack in devstack, but it's also 
trivial to just run at least one job (the weirdo postgres job?) with v1 
enabled so we're at least covered in the gate before we remove it in 
Ocata. I don't see harm in that.

nova-network is deprecated and we haven't gone through and dropped that 
from all of our gate jobs.

-- 

Thanks,

Matt Riedemann