merge prop: <a href="https://review.openstack.org/#/c/6847/">https://review.openstack.org/#/c/6847/</a><br>now has both required +2s. I'll wait a day or two to approve just in case there are any lingering objections.<br>
<br>-tr3buchet<br><br><div class="gmail_quote">On Thu, May 3, 2012 at 10:07 AM, Dan Prince <span dir="ltr"><<a href="mailto:dprince@redhat.com" target="_blank">dprince@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
----- Original Message -----<br>
> From: "John Garbutt" <<a href="mailto:John.Garbutt@citrix.com">John.Garbutt@citrix.com</a>><br>
> To: "Dan Prince" <<a href="mailto:dprince@redhat.com">dprince@redhat.com</a>>, "Vishvananda Ishaya" <<a href="mailto:vishvananda@gmail.com">vishvananda@gmail.com</a>><br>
> Cc: <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Sent: Thursday, May 3, 2012 10:56:44 AM<br>
> Subject: RE: [Openstack] database migration cleanup<br>
><br>
> I may have missed this in the discussions, but does this impact on<br>
> upgrade?<br>
><br>
> I am guessing you have tested Essex -> Folsom upgrade, but does this<br>
> affect people upgrading from any of the Essex milestones to Folsom?<br>
<br>
</div>What this does is compact the pre-Essex (final) migrations into a single migration. Users of any of the Essex milestones would need to first upgrade to the final Essex release and then upgrade to Folsom.<br>
<br>
This seemed like a reasonable approach since most distributions release updates that contain the final releases anyway.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
> I guess the deeper question is which upgrade paths do we want to<br>
> maintain...<br>
><br>
> Thanks,<br>
> John<br>
><br>
> > -----Original Message-----<br>
> > From:<br>
> > openstack-bounces+john.garbutt=<a href="mailto:eu.citrix.com@lists.launchpad.net">eu.citrix.com@lists.launchpad.net</a><br>
> > [mailto:<a href="mailto:openstack-bounces%2Bjohn.garbutt">openstack-bounces+john.garbutt</a>=<a href="mailto:eu.citrix.com@lists.launchpad.net">eu.citrix.com@lists.launchpad.net</a>]<br>
> > On Behalf Of Dan Prince<br>
> > Sent: 02 May 2012 21:20<br>
> > To: Vishvananda Ishaya<br>
> > Cc: <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> > Subject: Re: [Openstack] database migration cleanup<br>
> ><br>
> ><br>
> ><br>
> > ----- Original Message -----<br>
> > > From: "Vishvananda Ishaya" <<a href="mailto:vishvananda@gmail.com">vishvananda@gmail.com</a>><br>
> > > To: "Dan Prince" <<a href="mailto:dprince@redhat.com">dprince@redhat.com</a>><br>
> > > Cc: <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> > > Sent: Thursday, April 26, 2012 4:14:25 PM<br>
> > > Subject: Re: [Openstack] database migration cleanup<br>
> > ><br>
> > > +1. Might be nice to have some kind of test to verify that the<br>
> > > new<br>
> > > migration leaves the tables in exactly the same state as the old<br>
> > > migrations.<br>
> ><br>
> > Hey Vish,<br>
> ><br>
> > This is an outline of what I did to test MySQL and PostgreSQL to<br>
> > ensure the<br>
> > compact migration script generates *exactly* the same schemas as<br>
> > before:<br>
> ><br>
> > <a href="http://wiki.openstack.org/database_migration_testing" target="_blank">http://wiki.openstack.org/database_migration_testing</a><br>
> ><br>
> > As things stand both MySQL and PostgreSQL are exactly the same. I<br>
> > have<br>
> > some pending changes that I've found in the schemas that need to be<br>
> > fixed<br>
> > in Folsom... but the goal here was to replicate Essex with<br>
> > migration 082 so<br>
> > that is what I did.<br>
> ><br>
> > Sqlite has a few differences (indexes for example). How important<br>
> > is it that<br>
> > the Sqlite schema be exactly the same? Unit tests are passing.<br>
> ><br>
> > Dan<br>
> ><br>
> ><br>
> > ><br>
> > > Vish<br>
> > ><br>
> > > On Apr 26, 2012, at 12:24 PM, Dan Prince wrote:<br>
> > ><br>
> > > > The OpenStack Essex release had 82 database migrations. As<br>
> > > > these<br>
> > > > grow in number it seems reasonable to clean house from time to<br>
> > > > time.<br>
> > > > Now seems as good a time as any.<br>
> > > ><br>
> > > > I came up with a first go at it here:<br>
> > > ><br>
> > > > <a href="https://review.openstack.org/#/c/6847/" target="_blank">https://review.openstack.org/#/c/6847/</a><br>
> > > ><br>
> > > > The idea is that we would:<br>
> > > ><br>
> > > > * Do this early in the release cycle to minimize risk.<br>
> > > ><br>
> > > > * Compact all pre-Folsom migrations into a single migration.<br>
> > > > This<br>
> > > > migration would be used for new installations.<br>
> > > ><br>
> > > > * New migrations during the Folsom release cycle would proceed<br>
> > > > as<br>
> > > > normal.<br>
> > > ><br>
> > > > * Migrations added during Folsom release cycle could be<br>
> > > > compacted<br>
> > > > during "E" release cycle. TBD if/when we do the next<br>
> > > > compaction.<br>
> > > ><br>
> > > > * Users upgrading from pre-Essex would need to upgrade to Essex<br>
> > > > first. Then Folsom.<br>
> > > ><br>
> > > > --<br>
> > > ><br>
> > > > I think this scheme would support users who follow stable<br>
> > > > releases<br>
> > > > as well as users who follow trunk very closely.<br>
> > > ><br>
> > > > We talked about this at the conference but I thought this issue<br>
> > > > might be near and dear to some of our end users so it was worth<br>
> > > > discussing on the list.<br>
> > > ><br>
> > > > What are general thoughts on this approach?<br>
> > > ><br>
> > > > Dan (dprince)<br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > > > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> > > > Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > > > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> > ><br>
> > ><br>
> ><br>
> > _______________________________________________<br>
> > Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> > Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br>