Remove Keystone V2 Support

Registered by Adam Young

Keystone V3 has been out and stable for several releases. There is nothing that V2.0 can do that cannot be done in V3. In addition, we don't want to limit functionality to only what can be done via V2.

Removing V2 support will simplify and shrink the code base, as well as pave the way for better Domain support.

Blueprint information

Status:
Not started
Approver:
Adam Young
Priority:
Undefined
Drafter:
Adam Young
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

stevemar: as of mitaka, v2 has been deprecated, it will not be removed until the Q release. we can start by refactoring the current code to call v3 functions instead of flat our removing the code.

further, this would just get bunched into the 'removed-as-of-relasename' blueprint that is created at the beginning of each cycle

and i just commented on a DOA blueprint, nice

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.