[openstack-dev] [keystone] re-ordering of schema migrations

Russell Bryant rbryant at redhat.com
Wed Feb 27 21:21:38 UTC 2013


On 02/27/2013 01:43 PM, Dan Prince wrote:
> 
> 
> ----- Original Message -----
>> From: "Doug Hellmann" <doug.hellmann at dreamhost.com>
>> To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
>> Sent: Wednesday, February 27, 2013 12:21:14 PM
>> Subject: Re: [openstack-dev] [keystone] re-ordering of schema migrations
>>
>> On Wed, Feb 27, 2013 at 9:59 AM, Dan Prince <dprince at redhat.com>
>> wrote:
>>

>>
>> Yeah. Let's not do that, though. Let's just add new migrations as
>> necessary. That way each migration is tested, and after it is known
>> to work
>> it is not changed to something different that has to be re-tested.
> 
> 
> I don't think Keystone has reached this point either. At some point though the number or migrations becomes unwieldy and compacting things may make more sense though.

And to clarify, we have already done this a couple of times for nova:
once for Folsom and again for Grizzly.  In Grizzly we're up to 159, but
the migrate repo starts with a single migration to get up to 133.

-- 
Russell Bryant



More information about the OpenStack-dev mailing list