It was deprecated during the previous cycle because of retired
WinStackers project[1].
The following pollsters are also removed because these are supported
only by Hyper-V inspector.
- disk.device.latency
- disk.device.iops
[1] 7660339b4a4d578f2615fd6c27e8c9627ab29d37
Change-Id: I872f93b945233a1288c773302be3835db2fd2e4f
The following metrics are all specific to OpenDaylight but
OpenDaylight support was already removed and we no longer need to
maintain these.
- switch.flow
- switch.table
- switch.port.*.drops
- switch.port.*.errors
- switch.port.receive.*_error
- switch.port.collision.count
Change-Id: I2f5f71d0a1ed7de0e0886e104445b087bdc05d67
The feature was deprecated during the previous cycle[1], because
the netwokring-odl plugin[2] was already retired.
[1] a92d77b1823f7d9789d07faca785299637cabaa6
[2] https://opendev.org/openstack/networking-odl
Change-Id: I3437b73dea37f600a505f908c14e54536a40f588
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: I99bf47336c8363e5f0088dd26ae066f9202b27b7
IPMI sensor 'Current' captures current & power consumption metrics.
With the help of new pollster "hardware.ipmi.power", ceilometer
ipmi agent can differentiate between current and power metrics as
both are generated from the same sensor(Current).
Power metrics are captured using a slightly different command than
other sensors which is "ipmitool get sensor 'Pwr Consumption'".
Closes-Bug: #2038425
Change-Id: I0a8af40626cd44dca9743fba63c8dbda8729d054
Opentelemetry is a standard data protocol of observability.
This patch add a new publisher about 'opentelemetry', it use
http to send data in json format to opentelemetry collector.
In the future, we can try to send data to opentelemetry by gRPC.
Change-Id: Ifa20d29d27e35d98999bf0e7ae519ebcedf811aa
This removes the monasca integration. Monasca was recently
declared as inactive project. In addition the monasca related
unit tests were very verbose and they were outputing a lot
of errors. Lately one of the unittests even started failing
randomly.
Change-Id: I468079b2a790245bd682c80d0116fb0da60d0e7c
Implementation to publish event using file publisher already exists.
Due to the missing entrypoint for file publisher, events couldn't
be written to a file.
Closes-Bug: 2033052
Change-Id: Iee69978121874263d6de67dbddd420e44b6bff4c
Problem description
===================
Today we have some hardcoded pollsters that are gathering
data from running virtual machines through libvirt or
different programs running in the compute nodes. However,
the Dynamic pollster definition does not support this kind of
operations to gather data, it only supports HTTP Rest
requests to collect data. Therefore, it is not possible to
use the dynamic pollster definition to create a YML based
pollster that runs and collects data from Libvirt in the
compute nodes.
Proposal
========
To allow host commands/scripts in the Dynamic pollsters,
we propose to add a new pollster definition using the
`os.subprocess` lib to run host commands to collect
Host/VMs data and store them in the configured backend.
This will provide more flexibility and make the
Dynamic pollsters able to be used in Ceilometer compute
instances as well.
Change-Id: I50b8dc341ce457780416b41d138e35f5a0d083b6
Depends-On: https://review.opendev.org/c/openstack/ceilometer/+/850253
... and discovery/inspector plugins depending on the pollster. These
were implemented to gather metrics via SNMP daemon in TripleO-managed
deployment but these are no longer valid since Telemetry services and
Nova were removed from undercloud.
Change-Id: If9a6b695ba799c766314a88328ea8a779407acc0
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
Co-Authored-By: Ghanshyam Mann <gmann@ghanshyammann.com>
Change-Id: Ieec37d300bca0c78f9420657066b1c60a64911e9
... because it is of no use since neutron-lbaas was retired and was
replaced by Octavia. This feature was officially deprecated during
Yoga cycle[1] so we are ready to remove it.
[1] 8917c73964eb764c3c4beb65d3713b36938181dd
Change-Id: Ic145c23cc0b0372ef78f4a45ffb084bec24936c3
This change removes the Xen support which was deprecared during
the previous cycle[1].
[1] fd0a561bea956f1b62f6ca5a27e762cb76ad9a90
Change-Id: If1675468095cbc1b9c065edb6b086e7f4afa2f3e
Resolves warnings like the following:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
Change-Id: Ie1a033f1dcb1b62bf1bc8a213b9d7ef7e4e5b299
Add two new meters called network.incoming.bytes.delta and
network.outgoing.bytes.delta that give the delta Bytes that were send or
received by an vNic.
Change-Id: Icf45a8d185cdb4a7b00a83586c98f998cbc0e928
Signed-off-by: Arnaud Morin <arnaud.morin@gmail.com>
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: I092a9bd1897bdb331c461ad85d8c58aff03e2511
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
Change-Id: I93294c42a967ca19b9b04ead9cd636b52f1cc038
The goal of this PR is to add the support for
non-OpenStack APIs into Ceilometer. An example of such
API is the RadosGW usage API.
Change-Id: If5e1c9bce9e2709746338e043b20d328d8fb4504
The Ceilosca (monasca-ceilometer) publisher has been around since
before the Mitaka release and has been used in production for years.
The MonascaPublisher acts as another Ceilometer publisher and sends
selected metrics on to the Monasca API for storage, aggregation,
alarming, etc. Once metrics are in Monasca, they may be retrieved
through the Monasca API or with the python-monascaclient. This
Ceilosca functionality is a key component for metering in several
distributions and is used in many customer installations.
With the removal of the Ceilometer v2 API (which allowed the
removal of the Ceilosca storage driver, shrinking the Ceilosca
code base) and continuing changes to Ceilometer, a tighter
integration with the ceilometer repo may be beneficial to keep
both Monasca and Telemetry in sync.
Change-Id: I2cbce160503e23dfbde375722a3bd100ec86494e
Story: 2001239
Task: 5769
This commit adds the functionality of ceilometer-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: I6e76b74b2f02251ee39025e02de44b13568ebed2
Story: 2003657
Task: 27732
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: Ifb40dd40e716c0f07cafce4425e4ac13619d2085
Depends-On: https://review.opendev.org/#/c/641878/
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: I6c7c07157327434515ccba72f332e132a8e363f5
Transformers cannot work correctly on multiple nodes without workload
partitioning, which has been removed.
The transformation of data is no more the responsability of Ceilometer. The
data storage used by default (Gnocchi), is able to handle the scenario that
Ceilometer covered by default such as computing the rate of a metric.
Change-Id: If3683318b998a37c40bc09314dd8ab3eef326ba7
Depends-On: Ifd1d04ce813028f115c19bc983e7dd1e63c6f8a5
Depends-On: I0330c09d72c20d63d08770b52d3071512a418260
* All the telemetry related projects intree tempest plugins
are now moved to telemetry-tempest-plugin
Change-Id: I57738964f65495364dcc74821634d54aea1769fd
notification agent now just asks for pipelinemanagers and gets
endpoints it should broadcast to from there. it only sets up a
listener for main queue and a listener for internal queue
(if applicable)
- pass in publishing/processing context into endpoints instead of
manager. context is based on partitioning or not
- move all endpoint/notifier setup to respective pipeline managers
- change interim broadcast filtering to use event_type rather than
publisher_id so all filtering uses event_type.
- add namespace to load supported pipeline managers
- remove some notification tests as they are redundant and only
different that it mocks stuff other tests don't mock
- change relevant_endpoint test to verify endpoints cover all pipelines
Related-Bug: #1720021
Change-Id: I9f9073e3b15c4e3a502976c2e3e0306bc99282d9
meter name in entrypoint should match actual meter name so it can
probably be enabled/filtered in polling/pipeline
Change-Id: I8ffbfc5ff65c505734ccc6c5fd4270ecf46d16e8
Closes-Bug: #1726458
oslo.cache is only used in the Gnocchi dispatcher, and not at all in tests.
Therefore it seems wrong to list it in tests.
Rather than always depending on it, let's just put it in the gnocchi flavor.
Change-Id: I8990ba139bba0d573ecd4d8567a88d92acb29605