These are no longer used and no longer necessary. Remove them.
Change-Id: Ibd7d46aefb3794dd342c8afb40dbb8d4ce00a976
Implements: blueprint remove-sqlalchemy-migrate
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
As downgrade are not supported after Kilo, we should remove them now.
Roll backs can be performed as mentioned in the below link:
http://docs.openstack.org/ops-guide/ops-upgrades.html#rolling-back-a-failed-upgrade
The DB downgrades were deprecated in Glance Mitaka release by commit
e3366afdfb.
Change-Id: I937d15d93f16a3e44a50e6ff1a469098eab67c79
Implements: blueprint remove-db-downgrade
Inspired by the nova blueprint backportable-db-migrations,
we reserve a range of migration slots to allow for idempotent
and standalone migrations to be backported to stable/grizzly
during the Havana release cycle.
Nova have reserved 10 slots and the historical ratio of
nova:glance migrations is circa 8:1. Hence the thought that
a total of 3 placeholder slots should more than suffice for
the Havana release cycle.
Change-Id: I576be7520f960e4cb4dcc6928035595fab7e459f