In zed cycle, OpenStack projects and oslo lib
has dropped the py3.6 and py3.7 support
- https://governance.openstack.org/tc/reference/runtimes/zed.html
I also decrepated oslo-log < 5.0.0, so we should bump oslo.log>=5.0.0.
Because of oslo.log>=5.0.0 depends on oslo.i18n>=3.20.0 as below, so we
also need to upgrade oslo.i18n.
The conflict is caused by:
The user requested oslo.i18n>=3.15.3
python-saharaclient 1.4.0 depends on oslo.i18n>=3.15.3
castellan 0.16.0 depends on oslo.i18n>=3.15.3
keystonemiddleware 4.17.0 depends on oslo.i18n!=3.15.2 and >=2.1.0
oslo-config 6.8.0 depends on oslo.i18n>=3.15.3
oslo-concurrency 3.26.0 depends on oslo.i18n>=3.15.3
oslo-db 6.0.0 depends on oslo.i18n>=3.15.3
oslo-log 5.0.0 depends on oslo.i18n>=3.20.0
The user requested (constraint) oslo-i18n==3.15.3
The conflict is caused by:
The user requested pbr!=2.1.0 and >=2.0.0
bashate 0.5.1 depends on pbr>=1.6
fixtures 3.0.0 depends on pbr>=0.11
stestr 1.0.0 depends on pbr!=2.1.0 and >=2.0.0
testresources 2.0.0 depends on pbr>=1.8
testtools 2.4.0 depends on pbr>=0.11
python-saharaclient 1.4.0 depends on pbr!=2.1.0 and >=2.0.0
castellan 0.16.0 depends on pbr!=2.1.0 and >=2.0.0
keystoneauth1 3.4.0 depends on pbr!=2.1.0 and >=2.0.0
keystonemiddleware 4.17.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-concurrency 3.26.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-context 2.22.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-db 6.0.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-i18n 3.20.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-log 5.0.0 depends on pbr>=3.1.1
The user requested (constraint) pbr==2.0.0
The conflict is caused by:
The user requested oslo.serialization!=2.19.1 and >=2.18.0
python-saharaclient 1.4.0 depends on oslo.serialization!=2.19.1 and >=2.18.0
keystonemiddleware 4.17.0 depends on oslo.serialization!=2.19.1 and >=1.10.0
oslo-log 5.0.0 depends on oslo.serialization>=2.25.0
The user requested (constraint) oslo-serialization==2.18.0
Change-Id: I117657e9861a55a751522dba3e3b1e75a22f9711
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: Ib2101f13171940857fe81f64dd9798dfe489743a
= six (and tox): the latest versions of tox (which are
compatible with newer virtualenv[1][2]) require a newer six.
[1] https://tox.readthedocs.io/en/latest/changelog.html#v3-14-4-2020-02-13
[2] https://github.com/tox-dev/tox/pull/1519
= alembic: A newer version is required by oslo-db 6.0.0.
= oslo.service: 1.24.0 (and before 1.31.0) capped eventlet to <0.21.0,
but eventlet>0.26.0 is now required.
= cryptography: paramiko 2.7.1 requires cryptography>=2.5.0
= oslo-messaging: bumped to 10.2.0
= greenlet: bumped to 0.4.16 to be compatible with py3.9
= warlock, amqp, pycodestyle: just drop those indirect dependencies
from l-c (and in fact pycodestyle is only a dependency of a linter
for testing).
Change-Id: I26bd73463a5da9ef947f287610b0a33b73062417
Python modules related to coding style checks (listed in blacklist.txt in
openstack/requirements repo) are dropped from lower-constraints.txt
they are not needed during installation.
Change-Id: If77b416355cef83d3ef28852d61c8c2396717879
- use the the python3 guestfs bindings, not the old python2
(not availbale anymore on the newer systems);
- fix the compatibility with mysql 8, which unfortunately
removes the shortend for user creation + password setting;
- bump the values in lower-requirements.txt (also requirements.txt
and test-requirements.txt when needed) so they they work with
python 3.8 (inspired by other similar bumps).
Change-Id: Icaa3c008bbe179098244f7bb9d80790068430fe2
These translation sections are not needed anymore, Babel can
generate translation files without them.
Remove babel.cfg as well, this is the default role and not needed
anymore.
also remove Babel from requirements[1]
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014227.html
Change-Id: Iead96312102da530a006fc259bab80ad37e55b76
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we don't need it
in lower-constraints.
These changes will help us to drop `mock` from openstack/requirements
Change-Id: I6fe01260c83f0ef1c1d4ae97f633a6512ab0ec72
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
This will show other versions of the doc, too.
Change-Id: Id73bbf0a844dee39f9c72df72b1bdb49fa094806
- Add libpq-dev to bindep.txt
Apparently this is needed after some unclear change.
Without this, psycopg fails to install:
"You need to install postgresql-server-dev-X.Y for building a server-side
extension or libpq-dev for building a client-side application."
- Bump the minimum version of psycopg to 2.7.2
pysycopg 2.6.2 is not able to deal with PostgreSQL 10:
"Error: could not determine PostgreSQL version from '10.6'"
Thanks to https://review.openstack.org/643231
Change-Id: If4ecc6a80bed338a0117adee0e6d361c135d9123
Also switch to pycodestyle from pep8 which requires a bump
of the the version of flake8 too.
Skip the following checks for now:
- E123 Closing bracket does not match indentation of opening bracket's line
- E226 Missing whitespace around arithmetic operator
- E402 Module level import not at top of file
- E731 Do not assign a lambda expression, use a def
- W503 Line break occurred before a binary operator
They should be probably revisited and fixed, if possible,
or skipped individually using # noqa
The following checks reported a limited number of errors and
they were fixed directly in this review:
- E241 Multiple spaces after ','
- E501 Line too long (82 > 79 characters)
Change-Id: I1f185d2efd1adf27a26e3ac93f2e1011c0b63124
This commit adds the functionality of sahara-status CLI for performing
upgrade checks as part of the Stein cycle upgrade-checkers goal.
It only includes a sample check which must be replaced by real checks in
future.
Change-Id: Idcb8d9eaf689800812cf6087e9c5937058c89ea6
Story: 2003657
Task: 26152
Use coverage+stestr for the cover tox target.
With this change, testrepository is not required anymore.
Change-Id: Ia294ee8003ccc10104f68777bea6921ff97bacef
According to Openstack summit session [1] stestr is
maintained project to which all Openstack projects
should migrate.
Let's switch it then.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Ic580dc7ba0684087a81137771fb125f4d412d948
Signed-off-by: Charles Short <zulcss@gmail.com>
The mimimum requirement of Flask was recently bumped to 1.0.2
(https://review.openstack.org/#/c/577534/) which means that
the requirements-check job used for the sahara gate
is failing with a requirement mismatch errors.
Change-Id: I0fc7e3e8a847917be0877f71128a603d258a85ea
Fix the incorrect lower constraints so they match the requirements
lists.
Change-Id: If55b7438c95b0364d93829392a59439e553722b9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I3a1d395b43e77010bf44ba71f5bcf146c01e0098
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
zhangbailin