On Wed, May 13, 2015 at 08:10:54AM -0400, Henry Gessau wrote:
Alembic supports migration branches. The advanced services (FW/LB/VPNaaS) have
separate migration branches for their own tables. Unfortunately neutron's
alembic script is hard-coded to only support these three external services for
now. I hope to work on a more pluggable framework in the future.
I could add another entry in neutron/common/repos.py
For Kilo you could try to monkeypatch neutron's script to support your
plugin's migration. Or you can try to do something like the group-based-policy
project does, by consuming the neutron migration script[1]. (GBP also has its
own migration branch.)
Actually, these two methods doesn't have much difference. cli.py
sets 'script_location', env.py sets 'version_table' (old
python-migrate had this option in migrate.cfg). It doesn't look
like as alembic's migration branches at all, just isolated
configurations in one database.
Thank you, this is exactly what I was looking for.
--
Regards,--
Sir Raorn. --- https://plus.google.com/+AlexeyFroloff
pgpSNhfW4yxKd.pgp
Description: PGP signature
__
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
