openstack/octavia - octavia - OpenDev: Free Software Needs Free Tools

Author	SHA1	Message	Date
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	2 years ago
Michael Johnson	05f5257075	Fix a few nits from the main volume-based patch I had a few minor nits on the volume-based patch. This patch corrects those. Co-Authored-By: Adam Harwell <flux.adam@gmail.com> Change-Id: I5f9ce36c878973f4ed96527af6f1024a362421d8	3 years ago
Michael Johnson	5af7133a02	Align logging on oslo_log This patch aligns all of Octavia to use oslo_log instead of the built in python logging. This should provide consistent log formats. It adds a hacking check to make sure "logging" doesn't come back into the code. Change-Id: I9b76c2bb5a5c396faf85df4606f2ca00f23de913	4 years ago
Nir Magnezi	4f7c541793	Use flake8-import-order plugin This addition automates the process, as opposed to relying on review inputs. Inspired by Ib51bd97dc4394ef2b46d4dbb7fb36a9aa9f8fe3d Change-Id: I1d6051cf6678b6d5db774fc884390fec626c1f2c	5 years ago
Cao Xuan Hoang	cf240b8238	Remove white space between print () There is a white space in line [print (*, then we remove it. Change-Id: Ic35d172c1fbf8e1a8d8a8e2d7d545ffc6c1da780	6 years ago
Michael Johnson	9a30e12814	Clarify that octavia-db-manage should be used It was not clear to users that we now use octavia-db-manage for alembic actions in octavia. Users would get an exception if they tried to use native alembic due to changes to the env.py. This patch updates the README.rst and env.py to clarify that octavia-db-manage should be used. Change-Id: I97e7fce5da167875694bc1a6abc69d47b3021487	6 years ago
Fei Long Wang	9f6c6d058b	Support db-manage command for db migration blueprint: octavia-db-manage Change-Id: Ib1c8f47b6af4dd5d86acff68bc56ab660241458a	6 years ago
lungc	24e3a0da7d	PEP8 fixes, spelling fixes Change-Id: Icbc3895637e80671897d103720568067afb02b5b	8 years ago
Brandon Logan	13b015daea	Initial migration for database structure Created alembic migration script to create tables and populate lookup table values. Implements: blueprint initial-db-migration Change-Id: I9bfa7f62e707571d00f48a0f756d25f4cdd08347	8 years ago