<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 08/02/2018 09:36 AM, Chris Dent
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1808021533170.30998@cdent-a01.vmware.com">On
Thu, 2 Aug 2018, Stephen Finucane wrote:
<br>
<br>
<blockquote type="cite">Given that multiple projects are using
this, we may want to think about
<br>
reaching out to the author and seeing if there's anything we can
do to
<br>
at least keep this maintained going forward. I've talked to
cdent about
<br>
this already but if anyone else has ideas, please let me know.
<br>
</blockquote>
<br>
I've sent some exploratory email to Ian, the original author, to
get
<br>
a sense of where things are and whether there's an option for us
(or
<br>
if for some reason us wasn't okay, me) to adopt it. If email
doesn't
<br>
land I'll try again with other media
<br>
<br>
I agree with the idea of trying to move away from using it, as
<br>
mentioned elsewhere in this thread and in IRC, but it's not a
simple
<br>
step as at least in some projects we are using paste files as
<br>
configuration that people are allowed (and do) change. Moving away
<br>
from that is the hard part, not figuring out how to load WSGI
<br>
middleware in a modern way.
<br>
</blockquote>
<br>
<tt>++<br>
<br>
Keystone has been battling this specific debate for several
releases. The mutable configuration goal in addition to some much
needed technical debt cleanup was the final nail. Long story
short, moving off of paste eases the implementations for
initiatives we've had in the pipe for a long time. We started an
effort to move to flask in Rocky.<br>
<br>
Morgan has been working through the migration since June, and it's
been quite involved [0]. At one point he mentioned trying to
write-up how he approached the migration for keystone. I
understand that not every project structures their APIs the same
way, but a high-level guide might be helpful for some if the
long-term goal is to eventually move off of paste (e.g. how we
approached it, things that tripped us up, how we prepared the code
base for flask, et cetera).<br>
<br>
I'd be happy to help coordinate a session or retrospective at the
PTG if other groups find that helpful.</tt><br>
<tt><br>
</tt><tt>[0]
<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/q/(status:open+OR+status:merged)+project:openstack/keystone+branch:master+topic:bug/1776504">https://review.openstack.org/#/q/(status:open+OR+status:merged)+project:openstack/keystone+branch:master+topic:bug/1776504</a></tt><br>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1808021533170.30998@cdent-a01.vmware.com">
<br>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>