<html><body><p>Thanks for bringing this up Sean.<br><br>I went ahead and documented all the way the projects/gates/clients broke in an etherpad: <a href="https://etherpad.openstack.org/p/v3-only-devstack">https://etherpad.openstack.org/p/v3-only-devstack</a><br><br>These are all the projects that I know that were affected, if someone knows others, please add your findings.<br><br>Sean, you can count me in on the volunteering effort to get this straightened out.<br><br>Steve<br><br><tt>Sean Dague <sean@dague.net> wrote on 2016/02/01 12:21:50 PM:<br><br>> From: Sean Dague <sean@dague.net></tt><br><tt>> To: openstack-dev <openstack-dev@lists.openstack.org></tt><br><tt>> Date: 2016/02/01 12:23 PM</tt><br><tt>> Subject: [openstack-dev] [all] towards a keystone v3 only devstack</tt><br><tt>> <br>> On Friday last week I hit the go button on a keystone v3 default patch<br>> change in devstack. While that made it through tests for all the tightly<br>> integrated projects, we really should have stacked up some other spot<br>> tests to see how this was going to impact the rest of the ecosystem.<br>> Novaclient, shade, osc, and a bunch of other things started faceplanting.<br>> <br>> The revert is here - <a href="https://review.openstack.org/#/c/274703/">https://review.openstack.org/#/c/274703/</a> - and will<br>> move it's way through the gate once the tests complete.<br>> <br>> Going forward I think we need a more concrete plan on this transition.<br>> I'm going to be -2 on any v3 related keystone changes in devstack until<br>> we do, as it feels like we need to revert one of these patches about<br>> every month for the last 6.<br>> <br>> I don't really care what format the plan takes, ML thread, wiki page,<br>> spec. But we need one, and an owner (probably on the keystone side) to<br>> walk us through how this transition goes. This is going to include some<br>> point in the future where:<br>> <br>> 1. devstack configures v3 and v2 always, and devstack issues a warning<br>> if v2 is enabled<br>> 2. devstack configures v3 only, v2 can be enabled and v2 enabled is a<br>> warning<br>> 3. devstack removes v2 support<br>> <br>> The transition to stage 2 and stage 3 requires using Depends-On to stack<br>> up some wider collection of tests to demonstrate that this works on<br>> novaclient, heat, shade, osc, and anything that comes forward as being<br>> broken by this last round. It's fine if we give people hard deadlines<br>> that they need to get their jobs sorted, but like the removal of<br>> extras.d, we need to be explicit about it.<br>> <br>> So, first off, we need a volunteer to step up to pull together this<br>> plan. Any volunteers here?<br>> <br>> -Sean<br>> <br>> -- <br>> Sean Dague<br>> <a href="http://dague.net">http://dague.net</a><br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>> <br></tt><BR>
</body></html>