Without explicitly closing and disposing the connections can linger in a
non-deterministic fashion and cause intermittent "too many connection"
errors in the tests.
This is effectively a "backport" of change
I8badf2a3094f2d27d381bd178c6d579f2a5c5ffe in aodh, made here for
safety despite not seeing the problem regularly in the ceilometer
tests.
The -N 100 is removed from the setup-test-env so that we are using
whatever the postgresql default is, meaning that these tests will be
better at exposing errors that users may see.
Change-Id: I694d118ff8dc2b5c8be633121fa1037130fbe874
unrestricted listing of meters can require significant memory.
this patch implements mandatory limit on meter-list
Change-Id: I8b38136c2493e75fbc7d9aef75aa055463a26319
Implements: blueprint mandatory-limit
unrestricted listing of resources can require significant memory.
this patch implements mandatory limit on resource-list
Change-Id: I5820ce759b20757febc1b92c100f584234b36b68
Implements: blueprint mandatory-limit
unrestricted listing of events can require significant memory.
this patch implements mandatory limit on event-list
sql backend requires a little rewrite due to fact that we grab data
in two steps: first we grab all events matching query, then we grab
appropriate traits (we don't use orm relationships because it's slow).
we can not just append order_by and limit to first query because we
use query in second part as well and sqlite will complain about
order_by/limit coming before join. this patch changes it to use a
subquery. based on testing, this does not appear to degrade
performance.
DocImpact
ApiImpact
Change-Id: Ib8009d6e4ab6d066ba5fca43b824c24c8cb32d4e
Implements: blueprint mandatory-limit
Ceilometer handles Designate CRUD notifications
as events, but not the exists notification.
This fix handles the exists notification as
event and sample for measurable audit interval.
Change-Id: I53d63cc4c8bcc6924afb0560bd8482d94e564895
Closes-Bug: 1474608
This makes the polling agents not use pipelines. Instead it simply sends
notifications for the notification agent to pick up and transform if
the pipeline.yaml says it should.
Inside the AgentManager and the PollingTask the data representation
is adjusted somewhat. Rather than making a single task for any given
interval, we make a single task for any name in the "sources" list.
This ought to mean (given that the interval is the same across
various sources in the default config) that we will get some I/Ox
interleaving.
At the moment all samples gathered by one pollng task are sent as an
individual notification. This is being done to minimize the apparent
surface area of this change. The expected long term change is for
single samples to be sent so as to increase granularity and
I/O interleaving.
The unit tests have been updated to reflect the new data
representation. The agent tests are fairly strongly oriented towards
testing that discovery and resource handling behave correctly. Some
additions have been made to make sure that samples traverse a fake
messaging bus as expected. Coverage of the ceilometer/agent/base has
increased from 98 to 99%. Additional functional testing should be
implemented when we have established the infrastructure for such
things.
Implements blueprint pollsters-no-transform
DocImpact
Change-Id: I25c22077e80509799713571dfd79c87fe21c8677
The hypervisor_inspector option allows the loading of various
drivers. The choice of drivers is limited to those within the
'ceilometer.compute.virt' namespace as indicated in
get_hypervisor_inspector().
Change-Id: I358b18ae190cdb578381f3af79956ace1ba97ec6
Within the VMware compute driver there are various references to
"Vsphere" when the proper product name should be "vSphere".
TrivialFix
Change-Id: Ic7e51b99cc1c88212b24d22d3adda3d872e12bbf
this patch adds support for Trove crud notifications
as events in ceilometer, and a notification plugin to
emit sample for the trove exists event.
Change-Id: I932941c88e7c8e9f059c97ec41ac098263e38803
Partially-Implements: blueprint track-dbaas-notifications
This is the initial support to migrate some basic meters to
leverage declarative approach.
Partially Implements: blueprint declarative-notifications
Change-Id: I64a4b2925981cfa14dc22ae30acd1f17821c9a2c
Now wait_for_line function behaves like all is ok even
if line hasn't been founded, but it should stop tests running.
In current CR checking of this situation is added.
Change-Id: I9f992feffd8d528e16d00269f62d24ce241f88ca
The RequestContextSerializer and JsonPayloadSerializer have been
implemented in oslo_messaging, This change remove the re-implemented
serializers in ceilometer/messaging.py
Change-Id: I871ff34a8e1a140273fd10fe1fbb539ff864c9f7
Closes-Bug: 1467524
oslo.messaging recommends that eventlet be monkey_patched for
thread to avoid spurious or unexpected lock-ups (which we have
been witnessing recently).
Change-Id: I9b2dbc09441bd2e812a44f9c6da948a6889adc29
direct publisher is mainly for testing and was used for event
pipeline to maintain consistency with previous functionality. this
patch makes notifier default to move storage load to collector
where it should be.
Change-Id: I2b12ac8afcd6e66e36d03276198f2d8e310b518f
The test_activity_filter_match_project_id tested failed, in the test
class, the filter_service_activity configure option is False, this cause
the _is_gnocchi_activity() method in gnocchi.py always returning False.
Change-Id: Ib07ca4e05a8ca5a5b0864a69062b25b8ce2506e1
Closes-Bug: #1474331
In gnocchi dispatcher, metric data will be grouped by resource_id and
counter_name before processing. But the inputted data is an unordered
list. It is better being sorted by resource_id and counter_name before
processing.
Change-Id: I8f493f720c479fd84b1a554ee5196115b992ecd1