Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I239799d7dd8e9162d254a5cfc75cad03e8650e91
Tox trying to install latest versions for building releasenotes,
doc which may not be supported by stable and lower branches,
so should be restricted by respective version's upper-constraints.txt
Change-Id: I286c0e8d657e78b7c7ddf2a1c2dcab6197cb853e
Use the tox discovered by ensure-tox to run the tests.
It seems they have been broken for a while for a while.
Change-Id: I477b7af0a6733dd8e3d1c943f04118251c272134
Those tests are used on the stable branches too, where they should
run using Python 2 (there is a specific py3 test there).
Change-Id: I64b3e6f0edaa2cc166ebeccbba5cd2cfffb452b0
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Change-Id: Ib3847b49f41c054b998072d0fbd0648b5293af5b
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I626737549ce3aeff0eeef63c42e6330d70192a63
This commit removes .testr.conf since this repo already has
.stestr.conf. We just need .stestr.conf instead of .testr.conf.
Change-Id: I97b23b134ad055718905a20fb0294292c01e5b23
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: I8381a68dfcc59e8dd5167faae1c05d2974db1315
- Updated CONTRIBUTING.rst per goal guidelines
- Created doc/source/contributor/contributing.rst per goal guidelines
Change-Id: I524ca2f4e6e7d08f77ab904c9e079dd94f24526c
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Change-Id: I7dd841e8904a29d342e5f1968c272fafd2f5e5ac
Make sure that the job running on master are py3 based,
according the established policy.
RGW must be used to provide the Swift API on Stein,
as devstack cannot properly deploy Swift/py2
in a Python 3 environment (old issue never fully solved).
Remove all EM releases where Python 3.6 is not available
and Tempest is not supported anymore. They will be gated
by sahara and python-saharaclient stable gates if needed;
the py2 variants are kept for this reason.
At the same time, remove the py35 unit test job,
as it is not supported anymore.
If an incompatible changes breaks an older branch,
an older sahara-tests version will be pinned there.
Remove the leftover py27 unit test jobs, which were
still needed when the py2 version of sahara-tests was
used on older branches (the py3 version is always used
even when the deployment is py2).
Finally, fix a multi-line issue with a shell command
which strangely happens for the master job only.
Change-Id: Id80ef7e186f6328ab162b92eebababd7e4886560
OpenStack is dropping the py2.7 support in ussuri cycle.
sahara-tests is ready with python 3 and ok to drop the
python 2.7 support.
Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support
Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Noteworthy change:
- run sahara-scenario with Python 3 also against the older releases
(up to rocky) which are Xenial-based.
- on the other hand, make sure that the jobs use a Python 2
devstack environment when deploying the pre-Ussuri branches;
- add the missing scenario-test jobs for stein and train.
Co-Authored-By: Luigi Toscano <ltoscano@redhat.com>
Change-Id: I3666a9ed9047f7c6a358e40d2f7a1d1103f8563b
Make sure that the internally-generated test uses the same PYTHON
variable that started sahara-scenario. Otherwise, when running inside
a virtualenv, the python executable from the venv is not used.
This change allows us to enable again the Python 3 scenario test.
Change-Id: I42d16b4acf72ff279d6b31840e11f2e7f939b113
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
At the same time, fix the links that have been broken by
the separation between API v1.1 and v2.
Change-Id: Ic72c0cd85d3d42a62071825c242df599d2442f99
Unfortunately it is not possible to switch to the new, more secure, native
format of OpenSSH >=6.5, because paramiko does not support it:
https://github.com/paramiko/paramiko/issues/602
A similar change has been applied to sahara some time ago:
https://review.opendev.org/605028
Story: 2003674
Task: 35983
Change-Id: I5683245c0a9373e299a647f7f61d3e6a2de284e6
The key boot_from_volume can now be configured when defining
node group templates.
Thi change works only when API v2 is enabled.
Change-Id: I1b23c2e457ceb6cf396addd5daa6d7bd36989167
Address few previously unnoticed use cases.
- Use uri_v3 is available (in the Tempest plugin). When v2
is not available (as in modern deployments) the old value
cannot be relied upon.
- Otherwise just check whether v3 is there and adds it if not
(as it happens for example on a TripleO deployment).
Change-Id: I593faafbe6b4c547db687d4f521e2a0b412d343a
- when downloading the internal job binaries, compare it
with the original file;
- simplify the string matching for the error messages in negative
testing (job binary and node group templates). The returned string
is a bit different when using python 3 (few \n remainings, maybe
there is an interaction between string and byte arrays.)
- run the API v2 tests using Python 3. Python 3 and API v2 tests
have been both added in Stein.
- define few data strings used for testing as bytes, so that they
can work with both Python 2 and Python 3.
Change-Id: I1924239659072ec8f1ea67df8d3d5b9a2264beb8
They are really two workarounds, even though the bandit one is more likely
to stay.
- bandit: exclude 1.6.0, which has a regression in the handling of patterns.
A fix is in place in bandit master, so newer versions should work.
The version is excluded there because is not handled by global requirements.
- stestr: exclude the only py3 test. The discovery seems to work with
the current stestr master (most likely thanks to
https://github.com/mtreinish/stestr/pull/241), but a new version does
not seems in sight, so let's disable the test for now.
Change-Id: I041b5cd41b089b2c1dc043f1e252c1f6b3c29db3
- add the needed new templates for Stein (basically a copy of the Rocky
ones).
- remove the Ocata test templates.
- fix the name of the storm 1.2 image variable for stein and master.
- (minor change) fix a comments for CDH 5.11 on all supported versions.
Change-Id: I9b97c0241cdd99d5def8831de42be49e04a50465
Update the link to the relevant section of the Rally quick start guide
(with slightly better wording) and use the correct parameter of the
`rally verify start` command (--pattern replaced --regex long time ago).
Story: 2003099
Task: 23193
Change-Id: I2ae35e2a330ef4d10c359ae2231d7cc2b4ec2eb0
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I8b0459fd519dd259a2f445b22db797388202a432