<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 28, 2014 at 6:40 PM, boden <span dir="ltr"><<a href="mailto:boden@linux.vnet.ibm.com" target="_blank">boden@linux.vnet.ibm.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><br>
On 7/28/2014 8:40 AM, Denis Makogon wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">
<br>
<br>
<br>
On Fri, Jul 25, 2014 at 9:00 PM, boden <<a href="mailto:boden@linux.vnet.ibm.com" target="_blank">boden@linux.vnet.ibm.com</a><br></div><div class="">
<mailto:<a href="mailto:boden@linux.vnet.ibm.com" target="_blank">boden@linux.vnet.ibm.<u></u>com</a>>> wrote:<br>
<br>
Gents,<br>
As we discussed at the BP meeting on July 14 - I've created a new BP<br>
and BP wiki to outline the dynamic extension loading using stevedore.<br>
<br>
BP:<br></div>
<a href="https://blueprints.launchpad." target="_blank">https://blueprints.launchpad.</a>_<u></u>_net/trove/+spec/dynamic-__<u></u>extension-loading<br>
<<a href="https://blueprints.launchpad.net/trove/+spec/dynamic-extension-loading" target="_blank">https://blueprints.launchpad.<u></u>net/trove/+spec/dynamic-<u></u>extension-loading</a>><br>
Wiki:<br>
<a href="https://wiki.openstack.org/__wiki/Trove/__DynamicExtensionLoading" target="_blank">https://wiki.openstack.org/__<u></u>wiki/Trove/__<u></u>DynamicExtensionLoading</a><br>
<<a href="https://wiki.openstack.org/wiki/Trove/DynamicExtensionLoading" target="_blank">https://wiki.openstack.org/<u></u>wiki/Trove/<u></u>DynamicExtensionLoading</a>><br>
PoC code:<br>
<a href="https://github.com/bodenr/__trove/commit/__fa06e1d96e6a49a2a54057e8feb8e6__24edeaf728" target="_blank">https://github.com/bodenr/__<u></u>trove/commit/__<u></u>fa06e1d96e6a49a2a54057e8feb8e6<u></u>__24edeaf728</a><div class="">
<br>
<<a href="https://github.com/bodenr/trove/commit/fa06e1d96e6a49a2a54057e8feb8e624edeaf728" target="_blank">https://github.com/bodenr/<u></u>trove/commit/<u></u>fa06e1d96e6a49a2a54057e8feb8e6<u></u>24edeaf728</a>><br>
<br>
I've also added this to the agenda for the next BP meeting:<br></div>
<a href="https://wiki.openstack.org/__wiki/Meetings/TroveBPMeeting" target="_blank">https://wiki.openstack.org/__<u></u>wiki/Meetings/TroveBPMeeting</a><div class=""><br>
<<a href="https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting" target="_blank">https://wiki.openstack.org/<u></u>wiki/Meetings/TroveBPMeeting</a>><br>
<br>
Please feel free to add comments to wiki or via email / IRC<br>
(@boden); otherwise we can sync-up on Monday's BP meeting.<br>
<br>
<br>
The only strong concern i feel about refactoring API Extension is about<br>
deprecation of all of this in K release. Trove _already_ uses lagacy<br>
code which is not maintainable. Because WSGI ReST framework was dropped<br>
off from oslo-incubator(during IceHouse release) and Trove will migrate<br>
into Pecan before K2.<br>
<br>
So, i'd like to freeze all refactoring/re-implementation around lagacy<br>
WSGI code until Pecan support implementation will land.<br>
</div></blockquote>
<br>
You are implying that Pecan will introduce a new way to discover and load extensions? Admittedly I'm not up to speed on Pecan yet, thus any refs you can provide are appreciated.<br></blockquote><div><br></div><div>I wasn't able to find something about extension management at Pecan docs (see <a href="http://pecan.readthedocs.org/en/latest/">http://pecan.readthedocs.org/en/latest/</a>). I'm just saying that everything that would possibly be done aroung deprecated code will be eliminated once "K" branch would be opened for development. That's why i'd not suggest to work around extension (they was deprecated, see <a href="https://gist.github.com/denismakogon/a7ce440297ebe2ec65ae">https://gist.github.com/denismakogon/a7ce440297ebe2ec65ae</a>).<br>
<br></div><div>Actually i would suggest to talk about Pecan migration, instead of proposed BP.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">
<br>
Best regards,<br>
Denis Makogon<br>
<br>
Thank you<br>
<br>
<br></div>
______________________________<u></u>___________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.<u></u>__org<br>
<mailto:<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.<u></u>openstack.org</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-dev</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a>><div class="">
<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</div></blockquote><div class=""><div class="h5">
<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>