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
s.
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
