octavia

History

Michael Johnson 033c1e02ff Stop allowing the deletion of an in-use flavor Currently the API allows an operator to delete a flavor even when it is in use by a load balancer. This patch corrects this by blocking the deletion of a flavor that is currently in use by a load balancer. It also correctly handles load balancers in the "DELETED" provisioning_status. Change-Id: Ie6d4f74e36c2fb7cee4e0ff1e198602c5d8394cc Story: 2006782 Task: 37307		2019-11-18 09:54:03 +11:00
..
versions	Stop allowing the deletion of an in-use flavor	2019-11-18 09:54:03 +11:00
README.rst	Clarify that octavia-db-manage should be used	2017-01-19 00:18:49 +00:00
env.py	Fix a few nits from the main volume-based patch	2019-09-12 10:32:45 +00:00
script.py.mako	Drop support for SQL Schema Downgrades	2016-06-08 18:45:34 +03:00

The migrations in the alembic/versions contain the migrations.

Before running this migration ensure that the database octavia exists.

To run migrations you must first be in the octavia/db/migration directory.

To migrate to the most current version run: $ octavia-db-manage upgrade head