neutron

History

Henry Gessau 9ba57b8c23 Tag the alembic migration revisions for Mitaka Previously when we had one repo with one alembic branch we would create a milestone revision on that single branch. Now we have multiple repos and expand/contract branches for each repo. So now we tag the final revision on every branch when we make a milestone release. The database can be upgraded with the command: neutron-db-manage upgrade <milestone> where <milestone> is an alias for all the revisions for a milestone. Partial-Bug: #1552935 Change-Id: I44456a8389b761bc9e0f35845b90671daddf3b59		2016-03-07 12:50:19 -05:00
..
alembic_migrations	Tag the alembic migration revisions for Mitaka	2016-03-07 12:50:19 -05:00
models	Add tag mechanism for network resources	2016-03-02 05:43:14 +09:00
README	Support for independent alembic branches in sub-projects	2015-08-12 23:50:58 -04:00
__init__.py	Use _ from neutron._i18n	2015-12-06 19:39:04 +09:00
alembic.ini	Ease debugging alembic by passing proper scripts path in alembic.ini	2015-06-22 15:44:55 +02:00
autogen.py	Support new mitaka directory with revisions	2015-09-30 18:58:52 +02:00
cli.py	Fix branch order when upgrading to alembic milestone	2016-03-04 00:44:40 -05:00
connection.py	neutron-db-manage: add has_offline_migrations command	2016-01-22 13:55:40 +00:00

See doc/source/devref/alembic_migrations.rst

Rendered at
http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html