[openstack-dev] [neutron][db] online schema upgrades
akamyshnikova at mirantis.com
Wed Jun 17 09:27:08 UTC 2015
Ihar, thanks for bringing this up!
This is very interesting and I think it worth trying. I'm +1 on that and
want to participate in this work.
In fact a lot *not strict* migrations are removed with juno_initial, so I
hope it won't be so hard for now to apply stricter rules for migration. But
what is the plan for those migrations that are *not strict* now?
I think that we should try to use Alembic as much we could as Mike is going
to support us in that and we have time to make some change in Alembic
We should undoubtedly plan this work for M release because there will be
some issues that will appear in the process.
On Tue, Jun 16, 2015 at 6:58 PM, Mike Bayer <mbayer at redhat.com> wrote:
> On 6/16/15 11:41 AM, Ihar Hrachyshka wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>> - - instead of migrating data with alembic rules, migrate it in runtime.
>> There should be a abstraction layer that will make sure that data is
>> migrated into new schema fields and objects, while preserving data
>> originally stored in 'old' schema elements.
>> That would allow old neutron-server code to run against new schema (it
>> will just ignore new additions); and new neutron-server code to
>> gradually migrate data into new columns/fields/tables while serving user
> Hi Ihar -
> I was in the middle of writing a spec for neutron online schema
> migrations, which maintains "expand / contract" workflow but also maintains
> Alembic migration scripts. As I've stated many times in the past, there
> is no reason to abandon migration scripts, while there are many issues
> related to abandoning the notion of the database in a specific versioned
> state as well as the ability to script any migrations whatsoever. The
> spec amends Nova's approach and includes upstream changes to Alembic such
> that both approaches can be supported using the same codebase.
> - mike
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev