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: I446f303e37007f0d3f2ee73a6f87e3a7766b8e56
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: Ie6e22b0b47c5148290f7b76c95967cd9a343343c
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: Ied79c449a8bd0c53a7392afb1dee18b5e7e5d619
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Cleanup docs building:
- Remove obsolete sections from setup.cfg
- Switch to using sphinx-build
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version, use apidoc for
API docs
- Fix doc problems found
Change-Id: I1f92444a145030e7715a8d357870d712c5d3cfb1
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: I551d8eada6764516dd0612037d9e9e9e5a677347
* Intree panko tempest plugin does not contains any tempest tests
and has just dummy tempest plugin skeletion, so it is better to
remove from the project. If in future new panko tempest tests
will be written, will go to a new repo where all the telemetry
tests will resides.
Change-Id: I4f56bdac3ddd7b55ae791c9e6aafb78bc5f6e14b
This is part of a community effort to provide better user experience
for those having to maintain RBAC policy. More information on this
effort can be found below:
https://governance.openstack.org/tc/goals/queens/policy-in-code.html
bp policy-and-docs-in-code
Co-authored-By: Hieu LE <hieulq@vn.fujitsu.com>
Change-Id: I9bad70abcf5543c3e5e5da25c56c408ee3ff0346
ceilometer is deprecating collector. this adds support to push
straight from publishers instead of using direct:// publisher
hack. dispatchers also have an extra serialize/deserialize step
which can be avoided.
Change-Id: I5fa8b862cf19c524f90d34681980cbd062ad9bf1
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: I3e6e8152ef941ef884507caf50d1a80c0a8e83bd
- we don't need to prefix 'event/storage' because that's all panko
does. cleanup inline with aodh.
- test_hbase_table_utils is not used anywhere and last reference
was from icehouse.
- drop a few places that use 'event_*' prefix since it wastes line
space
Change-Id: I348f5a3dfb59682589b4912eaed4e4b8abb15ebb
This patch adds a http publisher so that notification agent can be
configured to send samples or events directly to a http endpoint.
Change-Id: Ic1b2cabb49bcdbb229a3ae65982e3b3e263407f3
No config generator hooks should ever be registered with a name that
belongs to another project. In this case, using oslo.middleware.cors
means that *every other project* that loads the middleware gets this
application's defaults when the generator is run on a system with
everything installed (such as a dev box with devstack). Use the name
of the app instead, to ensure that the defaults are only set when this
app's sample config and documentation are being generated.
Change-Id: I6a8c7d44b9db9325003ff2fdb667b0ced7739e96
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
with timedelta plugin we could create new metric for latency time of
nstance booting without using events and its transformation.
we could define new meter in meters.yaml with volume as in example::
volume:
fields: [$.payload.created_at, $.payload.launched_at]
plugin: ‘timedelta’
as a result we get volume value equal to difference between two mentioned
timestamp fields in seconds.
Change-Id: If5084cc23212a0a6bd9dac8438d5d286f3415730
The default values needed for ceilometer's implementation of cors
middleware have been moved from paste.ini into the configuration
hooks provided by oslo.config. Furthermore, these values have been
added to ceilometer's default configuration parsing. This ensures
that if a value remains unset in ceilometer.conf, it will be set
to use sane defaults, and that an operator modifying the
configuration file will be presented with a default set of
necessary sane headers.
Closes-Bug: 1551836
Change-Id: Iaab90bfa1811bf6d56696648a000f02ee3306285
In this change set, add the new methods to collect the new meters
in the LBaaS v2[1].
list_listener: list all the listeners
list_loadbalancer: list all the loadbalancers
get_loadbalancer_stats : get the statistics of the specified
loadbalancer.
[1]https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0
Co-Authored-By: Xia Linjuan <ljxiash@cn.ibm.com>
DocImpact: new metrics are introduced
Change-Id: I982f28917d1f8fd3d4352037f8832de9ef869942
Implements: blueprint lbaas-v2-enablement
This change moves our code to the new keystoneauth1 library.
This allows to wipe out all authentification code from Ceilometer.
Ceilometer become compatible with all keystone API version and
all keystone auth plugin for authentification.
This also moves the keystone project discovery to v3 API,
to fully removes the keystone v2 client from Ceilometer.
Implements blueprint support-keystone-v3
Depends-On: Ia5e924eb58aac7fd53e9fe4a3dbdee102ece3ad7
Depends-On: Ic7bbf9c98eb3f5a5d31da6f313458c4c4d62f59f
Change-Id: Id2938c2b323e935b3da35768f1f75ea3ae65bad5
Per [1] we now want to use the git repository for knowing the version
instead of just trying to modify the setup.cfg file.
[1] http://lists.openstack.org/pipermail/openstack-dev/2015-November/080692.html
Change-Id: I857b50f6b4284b44ff7a10315437b31ae2b0c8a8
Depends-On: I7860e230da5b5ee517c1568aed2127bdb9c6ee7e
This removes entirely our usage of eventlet and its ugly monkey-patching
in favor of a threaded approach.
Implements: remove-eventlet
Change-Id: Ib5f623e2d1ff9e9254601ad091bf5b53ab32000d
Since we moved all the alarming code and subsystem to the Aodh project,
remove it from Ceilometer.
Depends-On: I3983128d2d964b0f1f3326948b27f5d94df65a04
Depends-On: I99c9f2be0bbc70f289da5c2ba22698b8b7dc4495
Change-Id: Id169a914c1d1f2f5ad03ebb515d3d052204d5c5c
Added the configuration options to allow the administrator to configure
the collector to only record meter or event by setting the
meter_dispatchers and event_dispatchers configuration.
Separated dispatcher managers load the dispatchers from different
namespaces for meter/event respectively.
Doc-Impact: separated meter/event dispatchers
Change-Id: I161318f4503ce79205b54a93f2ae9b4e052f7971
Closes-Bug: #1480333
Bump preversion to mark the start of the Mitaka development branch.
The liberty release branch will be cut from the previous commit.
Change-Id: Ic1c5492eff43dc8488d2da40f54436db00795e24
Pollsters and Post Sample implementation
will publish to the notifications.sample
queue with this change.
Change-Id: Iccb9261ee805d41ed057bd0ac72306cd6a2ddaff
Closes-Bug: #1484695
Closes-Bug: #1489341
this patch adds support for a delta transformer. the transformer's
only functionality is to calculate the delta between current sample
and previous sample.
conditions:
- it will disregard any out of order samples
- a growth_only param is available to capture only positive deltas
- supports renaming to a new meter name using same schema as other
transformers.
using this transformer, we also create a cpu.delta meter which will
enable another view of cpu meter. this delta meter will allow for
(relatively) accurate cputime calculations and will cope with cputime
resets.
DocImpact
Change-Id: Iabcad20d500e3157e4d19f8b2ebffd770218165b
Closes-Bug: #1417949