x/vmware-nsx
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.

Closes-Bug: #1559318
Change-Id: Ie1324f8f998e1d551fc0aa3e3bc5f6a51523365a
This commit is contained in:
Abhishek Raut 2016-02-26 04:27:43 -08:00 committed by garyk
parent 74df4e4498
commit e2971f49f0
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
vmware_nsx/db/migration/alembic_migrations/versions/liberty/contract/3c88bdea3054_nsxv_vdr_dhcp_binding.py
View File

@ -31,7 +31,7 @@ revision = '3c88bdea3054'
down_revision = '393bf843b96'
# milestone identifier, used by neutron-db-manage
neutron_milestone = [migration.LIBERTY]
neutron_milestone = [migration.LIBERTY, migration.MITAKA]
def upgrade():

9
vmware_nsx/db/migration/alembic_migrations/versions/mitaka/expand/4c45bcadccf9_extend_secgroup_rule.py
View File

@ -20,12 +20,17 @@ Create Date: 2016-03-01 06:12:09.450116
"""
from alembic import op
import sqlalchemy as sa
from neutron.db import migration
# revision identifiers, used by Alembic.
revision = '4c45bcadccf9'
down_revision = '20483029f1ff'
from alembic import op
import sqlalchemy as sa
neutron_milestone = [migration.MITAKA]
def upgrade():