As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: I3cd0d2e4ce5bffd6af3cce480a5de09860f5d3f7
This is already listed in requirements.txt so it's not necessary to
repeat it here.
We also remove the Python version classifiers since they're noise:
'python_requires' does this for us in a machine-readable manner
nowadays.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Ia2c8a5792c175fb0a8762e61ff76383119251cdd
This patch adds threshold evaluator for Prometheus metrics.
Alarms are based on Prometheus query only. The library
python-observabilityclient is used for querying Prometheus.
Co-authored-by: Jaromír Wysoglad <jwysogla@redhat.com>
Depends-On: Ie7477e0b11479449f7f13c7a784737ac70059964
Change-Id: I72e124cca4398b78f7ed12e1db3f66bdbfcb196e
This job is maintained by requirements team and ensures that
requirements and constraints have proper format and do not conflict
with guidelines.
Co-Authored-By: Erno Kuvaja <jokke@usr.fi>
Change-Id: I3dd8b1b1826473495725bb8cff2c42c6aa7b35f1
Utilizing the "test-requirements.txt" for the test requirements
and building tox 'testenv' with pifpaf and gnocchi rather than
assuming they are actual lib dependencies of Aodh tests.
Change-Id: Ia8bb7c1f17a8090c4932541ac3eed3a8a73f3252
this will allow various oslo.policy scripts like
oslopolicy-policy-generator to work with Aodh.
Change-Id: I5941fe03277368f789a0e07d823ececdf86ed37e
Story: 2010559
Task: 47247
* use min version 4.2.5, for fixes [1][2][3]
* passenv fixed as space-separated list is not allowed anymore
* doc target uses requirements.txt as well as docs/requirements.txt
* skipsdist is not supported
* Add usedevelop = False so that aodh-api gets installed
Update setup.cfg: [files] -> [options]
[1] https://github.com/tox-dev/tox/issues/2754
[2] https://github.com/tox-dev/tox/pull/2824
[3] https://github.com/tox-dev/tox/pull/2828
Change-Id: I2422dc17e6c73ef346de80e57cdf61ef5d271d69
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Add release notes and update the python
classifier for the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: I94a68a6210e63831da6ec1ff165300dd9648bb43
Co-Authored-By: Ghanshyam Mann <gmann@ghanshyammann.com>
This is effectively os-testr but maintained.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I97183318f715b03f31145fa3d0f00bb7bc8a0c82
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: I62cedb56f25f1f409ed24fa3a1b1a3dbc8758e74
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: Ia0fa4ba1fecf2740a291c5a65b906b089c95404d
These translation sections are not needed anymore, Babel can
generate translation files without them.
Change-Id: I75d52a207ec280353892354cc5fd680db5843617
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: Ifc5f88dec427fe34b56b053b11ff18adf829e664
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg
- Update classifiers
- Update requirements, no need for python_version anymore
- Use newer openstackdocstheme and reno version
- Update hacking version to 3.0
- move python3 setting into toxenv, remove install_command and
move constraints into deps
Change-Id: Ibb42f8199eb4ca93e438e5e7ef5d4c4e0b35a738
Now that we no longer support older version of Python, there is no need
to use the third party 'mock' library for test mocking and can instead
use the standard library unittest mock module.
Change-Id: I1ea77249834e6c595c88f257226a483633be5f7a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
1. Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
2. Update some URLs to latest
Change-Id: I24cb8d8d084a291028a961823fcac4f09b4bf1ca
The auto-healing notifier works together with loadbalancer_member_health
evaluator.
Presumably, the end user defines a Heat template which contains an
autoscaling group and all the members in the group are joined in an
Octavia load balancer in order to expose service to the outside, so that
when the stack scales up or scales down, Heat makes sure the new members
are joining the load balancer automatically and the old members are
removed.
However, this notifier deals with the situation that when some member
fails, the stack could be recovered by marking the given autoscaling
group member unhealthy, then update Heat stack in place.
Change-Id: I6e92d1fc2125e155bb5068ff2c14fa318b126442
The loadbalancer_member_health_rule is used with
loadbalancer_member_health evaluator that was introduced here[1].
[1]: https://review.opendev.org/#/c/652622/
Change-Id: Ic1b3d429d3233be0789f173fa8d3ef5ca5522b8b
This patch is adding a new evaluator for the alarms of type
'loadbalancer_member_health' which evaluates the alarm by checking
the operating status of the members in a given load balancer pool.
A new config option 'member_creation_time' is introduced in order to
ignore the members in initialization status.
This is the first part of the auto-healing solution.
Change-Id: I57b848e6dc6aa5e79af1c17dbf1a42a9f068f174
This commit adds the functionality of aodh-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: I21e331266ab061a41d0ffe3c179b10f777af44f5
Story: 2003657
Task: 27733
This change removes the deprecated 'threshold' alarm type from Aodh.
This also removes the useless ceilometerclient dependency.
Depends-On: Id89130fd8a782dea863c85b37a919fbf0f0897dd
Change-Id: I7ccf930f2ad0316dbda0675a2ec0344e61986022
* https://review.openstack.org/#/c/526298/ moves the aodh tempest
tests and configurations in ceileometer. So we are removing the
intree tempest tests from aodh.
Change-Id: I972c53eb7c3f2b6d717220a5732b9b1fc0d33a9d
subunit-trace is not in the virtualenv and no more present into the gate
image.
This change installs it into the virtualenv.
Change-Id: Iedab49d13bc5cdbacf40db25694f1ac15eb9e6f7
The updated releasenote and requirements jobs expect requirements for
docs in one of the requirements files. Move requirements from setup.cfg
to doc/requirements.txt file.
Update also releasenotes build to use same command as in jobs - build
with warnings as errors.
See also
https://governance.openstack.org/tc/reference/project-testing-interface.html#documentation
Fix failure of building with warnings as errors:
Replace the instructions for querying for release notes for newton
with the results of a reno report because some of the broken release notes
are on branches that have been closed and we have no way to edit them.
Depends-On: I994aa3cf173ec8a9412239544e3269aca17adc25
Change-Id: If8df8a6e8cad2d9247f07c9ed7a71f29b19f7d51
This commit will prepare for implementing policies in code[1]
that mean with oslo.policy, we can define all of default rules
in code base and only update some rules via policy file if need.
To do that, we can move "rule by rule" into code base.
In this change, we will:
- Define some common rules in code base.
- Register them into policy engine to use as default policy rules
- Remove them out of policy.json file, so if operators want to
update rules, they should define them in policy file like the way
we done with config option with oslo.config.
Summary, with any rules that we defined in codebase, we no need to keep
them in policy file anymore if we don't want to customize them.
And everything still work well meanwhile we didn't define rules
in policy file with falling back to default rules.
[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Change-Id: Ide8f581b9adb6701eeb9b1f5293307dcee3dd9c3
Co-authored-By: Hieu LE <hieulq@vn.fujitsu.com>
python-subunit is not used directly anywhere
and it is dependency of both testrepository
and os-testr
(probably was used by some tox wrapper script before)
Change-Id: I5425614f54c89add268a6528ebf0daf56b07fea1
Turn on the flag in setup.cfg.
Fix some formatting issues with a couple of docstrings.
Fix some mistakes in the rst files.
Suppress warnings from Sphinx extensions that used to be suppressed by
pbr with older versions of Sphinx.
Change-Id: I549292b5e22cf8ae0f54f878793a36f2cd3b8e6c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This allows to run functional live tests without devstack.
And runs tests within the normal tox target without devstack
This increases test coverage because all backend are now tested.
Change-Id: If475b6d1f43a44540f276209a3651e7e790c2233
olso.mockpatch has been deprecated since I3efb3c64ebce396e756a47d110a74fe8604b6b72.
We now remove it in favor of native fixtures.
Change-Id: I701a106a08553b4cfb8fcc3074b9e56e1c3d4114
Ghanshyam Mann