<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 25, 2014 at 5:50 PM, Russell Bryant <span dir="ltr"><<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">We discussed the deprecation of the v2 keystone API in the cross-project<br>
meeting today [1]. This thread is to recap and bring that discussion to<br>
some consensus.<br>
<br>
The issue is that Keystone has marked the v2 API as deprecated in Icehouse:<br>
<br>
<a href="https://blueprints.launchpad.net/keystone/+spec/deprecate-v2-api" target="_blank">https://blueprints.launchpad.net/keystone/+spec/deprecate-v2-api</a><br>
<br>
If you use the API, deployments will get this in their logs:<br>
<br>
WARNING keystone.openstack.common.versionutils [-] Deprecated: v2 API is<br>
deprecated as of Icehouse in favor of v3 API and may be removed in K.<br>
<br>
The deprecation status is reflected in the API for end users, as well.<br>
For example, from the CLI:<br>
<br>
$ keystone discover<br>
Keystone found at <a href="http://172.16.12.38:5000/v2.0" target="_blank">http://172.16.12.38:5000/v2.0</a><br>
- supports version v2.0 (deprecated) here <a href="http://172.16.12.38:5000/v2.0/" target="_blank">http://172.16.12.38:5000/v2.0/</a><br>
<br>
My proposal is that this deprecation be reverted. Here's why:<br>
<br>
First, it seems there isn't a common use of "deprecated". To me,<br>
marking something deprecated means that the deprecated feature:<br>
<br>
- has been completely replaced by something else<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
- end users / deployers should take action to migrate to the<br>
new thing immediately.<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
- The project has provided a documented migration path</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
- the old thing will be removed at a specific date/release<br></blockquote><div><br></div><div>Agree on all points. Unfortunately, we have yet to succeed on the documentation front:</div><div><br></div><div> <a href="https://blueprints.launchpad.net/keystone/+spec/document-v2-to-v3-transition">https://blueprints.launchpad.net/keystone/+spec/document-v2-to-v3-transition</a></div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
The problem with the above is that most OpenStack projects do not<br>
support the v3 API yet.<br>
<br>
>From talking to Dolph in the meeting, it sounds like the intention is:<br>
<br>
- fully support v2, just don't add features<br>
<br>
- signal to other projects that they should be migrating to v3<br></blockquote><div><br></div><div>Above all else, this was our primary goal: to raise awareness about our path forward, and to identify the non-obvious stakeholders that we needed to work with in order to drop support for v2. With today's discussion as evidence, I think we've succeeded in that regard :)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Given that intention, I believe the proper thing to do is to actually<br>
leave the API marked as fully supported / stable. Keystone should be<br>
working with other OpenStack projects to migrate them to v3. Once that<br>
is complete, deprecation can be re-visited.<br></blockquote><div><br></div><div>Happy to!</div><div><br></div><div>Revert deprecation of the v2 API: <a href="https://review.openstack.org/#/c/82963/">https://review.openstack.org/#/c/82963/</a></div>
<div><br></div><div>Although I'd prefer to apply this patch directly to milestone-proposed, so we can continue into Juno with the deprecation in master.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
In summary, until we have completed v3 support within OpenStack itself,<br>
it's premature to mark the API deprecated since that's a signal to end<br>
users and deployers that says action is required.<br>
<br>
Thoughts?<br>
<br>
[1]<br>
<a href="http://eavesdrop.openstack.org/meetings/project/2014/project.2014-03-25-21.01.log.html#l-103" target="_blank">http://eavesdrop.openstack.org/meetings/project/2014/project.2014-03-25-21.01.log.html#l-103</a><br>
<span class=""><font color="#888888"><br>
--<br>
Russell Bryant<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>