Barbican client has to be Keystone V3.0 API complaint
Keystone has deprecated Keystone V2.0 API and V2.0 API will be de commissioned by "K" release. Barbican client has to sync up with Keystone V3.0 API ASAP.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Arvind Tiwari
- Direction:
- Needs approval
- Assignee:
- Guang Yee
- Definition:
- Obsolete
- Series goal:
- Proposed for juno
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Douglas Mendizábal
Related branches
Related bugs
Sprints
Whiteboard
After some brainstorming after reviewing the proposed change, I think that adding the Auth Plugin layer of abstraction to Keystone is the wrong approach for integration with keystone, as we are required to write a facade that is smart enough to deal with different versions of the keystone client.
The pain of maintaining this abstraction layer is not justified, and I think that to be able to easily support keystone moving forward, we should abandon the Auth Plugin layer, and instead consume Keystone client objects directly. See https:/
I think that a better approach for this is to allow barbicanclient.
This would include deprecating the following classes:
* barbicanclient.
* barbicanclient.
Changes will also need to be made in barbicanclient.
(dmend) I'm closing this BP since it applies to python-