create a keystone.version package

[Steve Martinelli]

the logic for handling the way keystone builds a WSGI app per API interface + version (v2 vs v3) should be isolated to it's own package in keystone (such as keystone.version).

there are entry points for these files in keystone-paste.ini (pre-Liberty) and setup.cfg (as of Liberty), so we need to make sure this work is tracked and documented.

[Lance Bragstad (lbragstad)]

This is being addressed by - https://review.openstack.org/#/c/203262/

[Dolph Mathews (dolph)]

Marking this as "Wishlist" because it'll introduce deprecation warnings when people's paste.ini files are not already consuming entrypoints from setup.cfg, and thus should be communicated in release notes.

[Dolph Mathews (dolph)]

Steve: I revised the bug description to better reflect your intent here. I originally read the bug description as "client-side handling of multiple API versions being moved into it's own pypi package." Hopefully the bug description now reflects that this is simply refactoring keystone's WSGI application factories into a new subpackage of keystone (*not* a new top-level package).

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/203262
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=64c491f9328f4bd0f594356730c4e96f72e8f6df
Submitter: Jenkins
Branch: master

commit 64c491f9328f4bd0f594356730c4e96f72e8f6df
Author: Steve Martinelli <email address hidden>
Date: Fri Jul 17 15:17:08 2015 -0700

    Create a version package

    There are files hanging around the top level directory that only
    handle the versioning routes of keystone (/v2.0 and /v3).

    These should be moved to their own package to further isolate
    these APIs.

    Closes-Bug: #1504892
    DocImpact

    Change-Id: Ica0ddcbeb6f7fc00a4ad3919fa16bf135637a607

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/keystone 9.0.0.0b1 development milestone.