<html><body>
<p><tt><font size="2">> yeah, we're talking about thousands and thousands of rows that have to<br>
> be updated before the API can be restarted…<br>
> <br>
> > There's also a possibility of adding support for the status codes, but<br>
> > keeping the string columns in the database, and then using the nova<br>
> > object versioning to "migrate" the object schema over time to the point<br>
> > where the migration is a simple DROP COLUMN.<br>
> <br>
> I like that idea better, TBH, but we're probably talking about a<br>
> long-time deprecation here, like on the order of a couple of releases;<br>
> that would give plenty of time for the majority of the records to be<br>
> revisited and make the final migration run for a lot shorter time.<br>
> -- </font></tt><br>
<br>
<tt><font size="2">Thanks for the discussion.</font></tt><br>
<br>
<tt><font size="2">So how would this new flow work?</font></tt><br>
<tt><font size="2">In Juno would there be an additional status_int column that would be populated and (eventually) replace the existing status (as string) column?</font></tt><br>
<tt><font size="2">How would the object versioning populate the new column for the existing records?</font></tt><br>
<br>
<tt><font size="2">Any examples or details that would help explain how this could work would be appreciated.</font></tt><br>
<br>
<tt><font size="2">Lastly, is there agreement that this is an issue that needs to be addressed? Note that this seems to be a pervasive problem, I've investigated the status column in cinder and nova but I suspect that the same issue exists in other components.</font></tt><br>
<br>
<tt><font size="2">Thanks,</font></tt><br>
<tt><font size="2">Steven Kaufer</font></tt><br>
<br>
<tt><font size="2"><br>
> Kevin L. Mitchell <kevin.mitchell@rackspace.com><br>
> Rackspace</font></tt><br>
<tt><font size="2">> <br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></tt></body></html>