<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="margin: 0px;"><div id="bloop_customfont" style="margin: 0px;"><div id="bloop_customfont" style="margin: 0px;">The Keystone team would like to announce the official split of python-keystoneclient and the Keystone middleware code.</div><div id="bloop_customfont" style="margin: 0px;">Over time the middleware (auth_token, s3_token, ec2_token) has developed into a fairly expansive code base and</div><div id="bloop_customfont" style="margin: 0px;">includes dependencies that are not necessarily appropriate for the python-keystoneclient library and CLI tools. Combined</div><div id="bloop_customfont" style="margin: 0px;">with the desire to be able to release updates of the middleware code without requiring an update of the CLI and</div><div id="bloop_customfont" style="margin: 0px;"> python-keystoneclient library itself, we have opted to split the packaging of the middleware.</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Launchpad Project (bug/bp tracker): https://launchpad.net/keystonemiddleware</div><div id="bloop_customfont" style="margin: 0px;">Repository: git://git.openstack.org/openstack/keystonemiddleware</div><div id="bloop_customfont" style="margin: 0px;">Repository (Browsable): https://git.openstack.org/cgit/openstack/keystonemiddleware</div><div id="bloop_customfont" style="margin: 0px;">PyPI location: https://pypi.python.org/pypi/keystonemiddleware</div><div id="bloop_customfont" style="margin: 0px;">Open Reviews in Gerrit: https://review.openstack.org/#/q/status:open+project:openstack/keystonemiddleware,n,z</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Detailed information on the approved specification for this split: https://review.openstack.org/#/c/95987/</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Middleware code that has been included in the new repository:</div><div id="bloop_customfont" style="margin: 0px;"> * auth_token middleware</div><div id="bloop_customfont" style="margin: 0px;"> * ec2_token middleware</div><div id="bloop_customfont" style="margin: 0px;"> * s3_token middleware</div><div id="bloop_customfont" style="margin: 0px;"> * memcache_crypt (utility code)</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Impact for deployers:</div><div id="bloop_customfont" style="margin: 0px;"> * New keystonemiddleware package will need to be installed (once released)</div><div id="bloop_customfont" style="margin: 0px;"> * Paste pipelines will need to be updated to reference the keystonemiddleware package instead of keystoneclient</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Impact for Projects and Infra:</div><div id="bloop_customfont" style="margin: 0px;"> * Keystonemiddleware is in process of being added to devstack and devstack-gate</div><div id="bloop_customfont" style="margin: 0px;"> * Global requirements update (once the 1.0.0 release occurs) will be updated to include keystonemiddleware</div><div id="bloop_customfont" style="margin: 0px;"> * Updates to the example paste pipelines to reference the new keystonemiddleware package will be proposed</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Impact for packagers (once released):</div><div id="bloop_customfont" style="margin: 0px;"> * Keystonemiddleware will need to be packaged and made available via your distribution's repositories (apt, yum, etc)</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">For the time being, we will be maintaining the current state of the middleware in the python-keystoneclient library. This</div><div id="bloop_customfont" style="margin: 0px;">will allow for a transition period and ensure that production deployments relying on the current location of the</div><div id="bloop_customfont" style="margin: 0px;">middleware will continue to work. However, the code located in the keystoneclient.middleware module will </div><div id="bloop_customfont" style="margin: 0px;">only receive security related fixes going forward. All new code development should be proposed to the new</div><div id="bloop_customfont" style="margin: 0px;">keystonemiddleware repository. </div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">We are targeting a 1.0.0 (stable) release of the new keystonemiddleware in the near term. The Keystone team will work with</div><div id="bloop_customfont" style="margin: 0px;">the OpenStack projects that consume Keystone middlewares to convert over to the new keystonemiddleware package.</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Feel free to join us in #openstack-keystone (on Freenode) to discuss the middleware, these changes, or any other</div><div id="bloop_customfont" style="margin: 0px;">OpenStack Identity related topics.</div><div><br></div></div></div></body></html>