When an unprivileged user want to access to Gnocchi resources
created by Ceilometer, that doesn't work because the filter scope
the Gnocchi query to resource owner to the user. To fix we introduce
a new configuration option "gnocchi_external_project_owner" set by
default to "service". The new filter now allow two kind of Gnocchi
resources:
* owned by the user project
* owned by "gnocchi_external_project_owner" and the orignal project_id
of the resource is the user project.
Closes-bug: #1703824
Change-Id: I0c86736a902a21520da18550aea0a7d1549bb24e
(cherry picked from commit b0bdd43209)
test_alarms_sends_notification will hang forever if it fails.
we don't really need to test that its notification is received by
other, just that it sends a notification. drop the test so it
verifies only that.
also, uncap pbr to resolve requirements conflict
Change-Id: I99f9996e5a3dd1e652d4142c7b596ae87da5e698
(cherry picked from commit b231f83f38)
DeprecationWarning: Using the 'enforce_type' argument is deprecated in
version '4.0' and will be removed in version '5.0': The argument
enforce_type has changed its default value to True and then will be
removed completely.
This option have never been useful, and now the default is already True.
So we don't need to raise requirement for this.
Change-Id: I042a5d98748e2b2c6ee8307340aa6056bf0a1dfd
(cherry picked from commit d8e33f7880)
pike libs don't work with ocata because they require pbr>=2.0.0 and
ocata is the opposite. upper cap the libs that are conflicting.
Change-Id: I8eabc0649114f18f9f93fa342999ebd645107dc6
* Fix markup
* Add more links
* Don't include an unfinished page
Change-Id: I901f611349feecf56eb18dea425ee655549eeb43
(cherry picked from commit 62b819152b)
there is no alarm_change table, so this fails during
migration when using mysql/
Change-Id: Ia0c63681fd8b5bc692d0a52ab587a6d3e430a844
(cherry picked from commit 23552b1c07)
test.idempotent_id is being kept temporary to migrate
to new lib interface. Now idempotent_id is available as Tempest stable
interface decorators and all plugins tests using the old decorator
should be switched to new interface.
In future, Once all plugins are switched to new decorator Tempest
will remove the test.idempotent_id
Change-Id: I20ef363a008b1c01652015cc2ada69777b8859d9
Related-Bug: 1616913
- set ttl to an hour since capabilities rarely change (if ever?)
- set cachetools to 1.1.6 since it has some ttl expiration
improvements and it's a year old so why not.
- i give up trying to disable cache
Change-Id: I1b83ffd32cfd631fc340b068e71f61789388ee73
as our borderline millenial hero progressed through the land of dried
bread, he found himself at the gates of hell. the flames of unreadable
wsme code overwhelmed him. as a lazy protagonist, he decided to ignore
wsme and just deal with cleaning up gabbi. this work came a bit easier
as it was quite similar to his work in panko and thus, he took gabbi
v1.7, and drop some of the redundancy.
Change-Id: I19dfb39ea8b9a4fc4063e32ce19b62d8ce74f939
uses: new python preferred method of calling the pip module directly
attempts: to clean up (by invitation) an attempt at this by dims
When USE_PYTHON3 is specified, run the pip module for aodh installation
from the correct python version, as shown in the documentation since
python3.4 (it works with all current versions of python2 and python3).
https://docs.python.org/3.4/installing/#basic-usage
Change-Id: I02090077781bc335a0df4dc54ff37edece281210
Existing code ends up installing aodh in py2.7 environment even
when USE_PYTHON3 is specified. Since Aodh team does not want
to pull in global requirements, we cannot use setup_develop like
other projects. So let's find the pip script and run it using
the correct python3 version.
Change-Id: I538e2f430954385033c7a1869a4ccc419e9e4108
When threshold evaluator returns a trending state instead of a state,
the composite evaluator ignores it and passes the alarm to insufficient
data instead of using it.
This change fixes that.
Closes-bug: #1645344
Change-Id: I4703936e0377a466e09c97b5485191b17442b57d
It does not contain the charset anymore, for an unknown reason. It's not a
big deal though, so just fix it.
Change-Id: I0583a8cedfecb9353d23978269f8a6f1fee171a4
Previously, if an alarm had multiple trust+ actions then we would create
a new trust ID for each one. We would also create new trusts for them
all each time the alarm was updated (even for actions that hadn't
changed).
With this change, we will only use a single trust ID for each alarm that
contains one or more trust+ actions.
Change-Id: Ib556ed3248221d6efb36f2117991c47e665ce336
Partial-Bug: #1575113
Openstack common has a wrapper for generating uuids. We should
use that function when generating uuids for consistency.
Change-Id: I331fb62e6f7278cdac3852b84fb161732aaad2a3
Closes-Bug: #1082248
We are replacing all usages of the 'retrying' package with
'tenacity' as the author of retrying is not actively maintaining
the project. Tenacity is a fork of retrying, but has improved the
interface and extensibility (see [1] for more details). Our end
goal here is removing the retrying package from our requirements.
Tenacity provides the same functionality as retrying, but has the
following major differences to account for:
- Tenacity uses seconds rather than ms as retrying did.
- Tenacity has different kwargs for the decorator and
Retrying class itself.
- Tenacity has a different approach for retrying args by
using classes for its stop/wait/retry kwargs.
- By default tenacity raises a RetryError if a retried callable
times out; retrying raises the last exception from the callable.
Tenacity provides backwards compatibility here by offering
the 'reraise' kwarg.
- Tenacity defines 'time.sleep' as a default value for a kwarg.
That said consumers who need to mock patch time.sleep
need to account for this via mocking of time.sleep before
tenacity is imported.
- For retries that check a result, tenacity will raise if the retried
function raises, whereas retrying retried on all exceptions.
This patch updates all usages of retrying with tenacity.
Unit tests will be added where applicable.
Note: This change is not newton critical so projects are welcome
to hold off on committing until post-newton. Ideally this change
will merge by the first part of Ocata so dependant functionality
can land and have time to solidify for Ocata.
[1] https://github.com/jd/tenacity
Co-Authored-By: gordon chung <gord@live.ca>
Closes-Bug: #1635402
Change-Id: Ife452b18709ff34ec48a39bbe5407d69a5b2e3c2
Allow Zaqar messages to be posted to a queue under the user's own tenant
by using a Keystone trust.
Change-Id: Ia9e200ecef13ba46479a155fee064d6dded08917