settingsLogin | Registersettings

[openstack-dev] [keystone][defcore][refstack] Removal of the v2.0 API

0 votes

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)?
- 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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Mar 1, 2017 in openstack-dev by Lance_Bragstad (11,080 points)   2 3 6

2 Responses

0 votes

On Wed, Mar 1, 2017 at 7:10 PM, Lance Bragstad lbragstad@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@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


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 1, 2017 by Rodrigo_Duarte (1,760 points)   2
0 votes

On Mar 1, 2017, at 6:01 PM, Rodrigo Duarte rodrigodsousa@gmail.com wrote:

On Wed, Mar 1, 2017 at 7:10 PM, Lance Bragstad lbragstad@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)

Yup, we actually talked a bit about this in the past couple of weeks. I’ve CC'd Luz who is playing point on capabilities scoring for the 2017.08 Guideline for Identity to make extra sure she’s aware. =)

At Your Service,

Mark T. Voelker
InteropWG Co-chair

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@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


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 2, 2017 by Mark_Voelker (4,000 points)   2 3
...