Alembic migration update/cleanup

This change updates and cleans up our alembic migration code:
- we now use an alembic migration entry point, instead of shipping
 our own db management tool
- use expand/contract alembic branches
- downgrade is not supported anymore, drop it
Change-Id: I8eb68075c720cd7252bd178c1bf08ef0947cd0d0
Closes-Bug: 1489876
This commit is contained in:
Thomas Morin
2015年09月25日 14:06:01 +02:00
parent 2e00f06f91
commit d985550e8b

View File

@@ -14,9 +14,8 @@ elif [[ "1ドル" == "stack" && "2ドル" == "install" ]]; then
elif [[ "1ドル" == "stack" && "2ドル" == "pre-install" ]]; then
_neutron_service_plugin_class_add $BGPVPN_PLUGIN_CLASS
elif [[ "1ドル" == "stack" && "2ドル" == "post-config" ]]; then
if is_service_enabled q-svc; then
bgpvpn-db-manage --config-file $NEUTRON_CONF --config-file /$Q_PLUGIN_CONF_FILE upgrade head
fi
#no-op
:
fi
if [[ "1ドル" == "unstack" ]]; then
#no-op
Reference in New Issue
openstack/networking-bgpvpn
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.

The note is not visible to the blocked user.