octavia/octavia/db/migration/alembic_migrations
Hervé Beraud bf460618bc Stop to use the __future__ module.
The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I193ba2193f24e6deac473423310b81a029e15e22
2020-06-02 20:32:07 +02:00
..
versions Add ability to specify TLS cipher list for pools 2020-04-07 20:59:56 -05:00
README.rst Clarify that octavia-db-manage should be used 2017-01-19 00:18:49 +00:00
env.py Stop to use the __future__ module. 2020-06-02 20:32:07 +02:00
script.py.mako Drop support for SQL Schema Downgrades 2016-06-08 18:45:34 +03:00

README.rst

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