openstack/neutron-lbaas
Code Issues Proposed changes

Tag the alembic migration revisions for Mitaka

Browse Source 
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: I66961aeaa2eef586eae11ee4eb08f61ebb91e54b
This commit is contained in:
Henry Gessau 2016-03-03 20:36:59 -05:00
parent cb4ec40a62
commit c4cd13d903
2 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
neutron_lbaas/db/migration/alembic_migrations/versions/liberty/contract/130ebfdef43_initial.py
View File

@ -30,7 +30,7 @@ down_revision = 'kilo'
branch_labels = (cli.CONTRACT_BRANCH,)
# milestone identifier, used by neutron-db-manage
neutron_milestone = [migration.LIBERTY]
neutron_milestone = [migration.LIBERTY, migration.MITAKA]
def upgrade():

8
neutron_lbaas/db/migration/alembic_migrations/versions/mitaka/expand/62deca5010cd_add_tenant_id_index_for_l7_tables.py
View File

@ -22,11 +22,17 @@ Create Date: 2016-03-02 08:42:37.737281
"""
from alembic import op
from neutron.db import migration
# revision identifiers, used by Alembic.
revision = '62deca5010cd'
down_revision = '3543deab1547'
from alembic import op
# milestone identifier, used by neutron-db-manage
neutron_milestone = [migration.MITAKA]
def upgrade():