On Wed, Mar 1, 2017 at 7:10 PM, Lance Bragstad <lbragstad at gmail.com> wrote: > During the PTG, Morgan mentioned that there was the possibility of > keystone removing the v2.0 API [0]. This thread is a follow up from that > discussion to make sure we loop in the right people and do everything by > the books. > > The result of the session [1] listed the following work items: > - Figure out how we can test the removal and make the job voting (does the > v3-only job count for this)? > We have two v3-only jobs, one only runs keystone's tempest plugin tests - which are specific to federation (it configures a federated environment using mod_shib) - and another one (non-voting) that runs tempest, I believe the later can be a good way to initially validate the v2.0 removal. > - Reach out to defcore and refstack communities about removing v2.0 (which > is partially what this thread is doing) > > Outside of this thread, what else do we have to do from a defcore > perspective to make this happen? > > Thanks for the time! > > [0] https://review.openstack.org/#/c/437667/ > [1] https://etherpad.openstack.org/p/pike-ptg-keystone-deprecations > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Rodrigo Duarte Sousa Senior Quality Engineer @ Red Hat MSc in Computer Science http://rodrigods.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170301/d05b4281/attachment.html>