<br><br>On Thursday, September 1, 2016, Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I don't read that at all as suggesting "the problem is solved, go<br>
away" but rather "help us make it better for everyone, don't just<br>
take one project off in a new direction and leave the others<br>
behind."</blockquote><div><br></div>I can clarify. I don't work directly on glance or keystone, I do oslo.db, sqlalchemy, and alembic development. If it's decided that the approach is "no special technique, just query more columns and tables in your data access layer and straddle across API versions", that does not indicate any new patterns or tools in Oslo or further up, hence "solved" in that the techniques are already available. If OTOH we are getting into triggers or this idea I have to do Python level translation events at the write side, that indicates the need for new library features and patterns. <div><br></div><div>I've been tasked with being ready to assist Nova and Neutron with online migrations for over a year. Other than helping Neutron get expand/contract going, I've not been involved at all, and not with anything related to data migrations. There hasn't been any need. <span></span><br><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
--<br>
Jeremy Stanley<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div>