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: Id8b012dc3f187b5a4b7be73a69910fe35657a0f5
This commit is contained in:
parent
fb71133c2e
commit
19fe781f8c
|
@ -31,7 +31,7 @@ revision = '4b47ea298795'
|
|||
down_revision = 'c40fbb377ad'
|
||||
|
||||
# milestone identifier, used by neutron-db-manage
|
||||
neutron_milestone = [migration.LIBERTY]
|
||||
neutron_milestone = [migration.LIBERTY, migration.MITAKA]
|
||||
|
||||
|
||||
new_action = sa.Enum('allow', 'deny', 'reject', name='firewallrules_action')
|
||||
|
|
|
@ -21,11 +21,18 @@ Create Date: 2015-09-16 11:47:43.061649
|
|||
|
||||
"""
|
||||
|
||||
from alembic import op
|
||||
|
||||
from neutron.db import migration
|
||||
|
||||
|
||||
# revision identifiers, used by Alembic.
|
||||
revision = '458aa42b14b'
|
||||
down_revision = '67c8e8d61d5'
|
||||
|
||||
from alembic import op
|
||||
# milestone identifier, used by neutron-db-manage
|
||||
neutron_milestone = [migration.MITAKA]
|
||||
|
||||
|
||||
FW_TAB_NAME = ['firewall_rules', 'firewall_policies', 'firewalls']
|
||||
SQL_STATEMENT_UPDATE_CMD = (
|
||||
|
|
Loading…
Reference in New Issue