Deprecate in favour of keystoneauth

Registered by Jamie Lennox

Keystoneauth is sufficiently ready that we should start using it instead of the relevant keystoneclient bits. This will involve deprecating the session, auth plugins, service catalog, access info etc components.

It turns out to be way to difficult to put a direct dependency on all these pieces from keystoneclient to keystoneauth. Instead we are just going to mark them all deprecated and expect people to switch to keystoneauth.

Blueprint information

Status:
Started
Approver:
Steve Martinelli
Priority:
Medium
Drafter:
Jamie Lennox
Direction:
Approved
Assignee:
Jamie Lennox
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Good progress
Milestone target:
None
Started by
Steve Martinelli

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/deprecate-to-ksa,n,z

Addressed by: https://review.openstack.org/258692
    Deprecate Session

Addressed by: https://review.openstack.org/258693
    Deprecate auth plugins from keystoneclient

Addressed by: https://review.openstack.org/258741
    Replace TestResponse with requests_mock

Addressed by: https://review.openstack.org/258742
    Deprecate adapter

Addressed by: https://review.openstack.org/258743
    Deprecate the baseclient.Client

Addressed by: https://review.openstack.org/258230
    Seperate Client base test class

Addressed by: https://review.openstack.org/117089
    Make tests run against original client and sessions

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.