In our efforts to clean up meters that were removed from Ceilometer
in the Rocky release (see c514916761 )
the ceilosca_pipeline.yaml was deleted. However, that file is needed
for the devstack plugin, as specified in devstack/settings .
This patch restores that file, and renames it to make the purpose
clearer.
Also added comments to the pipeline.yaml files to indicate their
purpose.
Change-Id: I28de9011d3e8c73f9d5057c8ca05cd42d3262dfc
Gathering up some configurations that have actually been used
in production as examples for user configurations of Ceilosca.
Story: 2001766
Task: 33543
Change-Id: If6eb225c74e417041a557426c796e814ffc40aba
A number of meters have been removed from Ceilometer in Rocky release.
This change updates the example configuration files to reflect it.
README.rst has been updated to reflect the current state.
Change-Id: I05650fef1cc5dc0d9e9f6e9a5aa66a5017b2377a
As of Queens the Ceilometer V2 API has been removed. Storage
driver related code in monasca-ceilometer can thus be removed.
Backport some refactoring that came up in creating
https://review.openstack.org/#/c/562400/
Realized some class names could be clearer and fit better with
Ceilometer.
Update test-requirements.txt with Rocky release of
python-monascaclient. Also include more license info.
Specify py35 instead of py34 in tox.ini (gates already using py35).
Include updates to devstack configuration to keep up with master
ceilometer. These include adding values for the [monasca] section
in ceilometer.conf and refreshing setup.cfg as well as updating
how the connection url to Monasca API is configured.
Also include some testing notes in devstack/README.md
Change-Id: I9291dfc06d67f18109a0ff66184bd418c6361977
monasca-ceilometer repo has an example copy of the ceilometer.conf
file used for devstack deployment and as an example. Ceilometer
project has made a few changes in Pike and Queens (including
removal of the famous v2 API), so some options have changed.
Also noticed a typo in devstack/plugin.sh.
Change-Id: I2dabefd825bbe131b42d435af479075f8a372e0d
Following changes are necessary to keep monasca-ceilometer
in sync with Ceilometer upstream
* Remove api/health.py (since ceilometer v2 api was removed)
* Remove storage/impl_monasca.py (since ceilometer storage drivers were removed)
* Updated opts.py and service.py (to keep in sync with ceilometer master)
* removed api, storage driver tests
* updated /etc/ceilometer/ceilometer.conf with new [monasca] options
Change-Id: I044f3e512db52a128bac8d5c5dcac76549a3b1c2
monasca-ceilometer repo now gets
copied into the vagrant VM, and
local.conf gets updated with
location and branch information,
so that any change can be
tested.
Also made following two changes:
1.)
Fix auth_url property being set in the
service_credentials section.
2.)
Create pipeline yaml with meters which
match monasca_definitions yaml.
Change-Id: I24da3b0df73079e03ff3f8a210851394a31c9c25
A few things have been updated in code but not in the READMEs
and scripting to allow a devstack deployment of Ceilosca
on top of a Ceilometer checkout. This commit should fix that.
Most notable, the devstack/plugin.sh was modified to include
copying the ceilosca_mapping directory in to ceilometer.
Change-Id: I269f5ec12c95c6ab2c0149ecc12811edbb60585e
Adding capabilities to ceilosca to be able to query metrics that
are already being collected by monasca using mappings files
there are two types of mappings:
1. Static Mapping: Currently it is used to map any static info
about ceilometer meters like the type of meter or unit
2. Extensive monasca mapping: currently it is used to map any
monasca metric to a ceilometer meter example:
meter_metric_map:
- name: "disk.device.write.requests"
monasca_metric_name: "vm.io.write_ops"
resource_id: $.dimensions.resource_id
project_id: $.dimensions.tenant_id
user_id: $.dimensions.user_id
region: "NA"
type: "cumulative"
unit: "request"
source: "NA"
resource_metadata: $.measurement[0][2]
As you can see for this mapping fields on left side of ":"
are used to map ceilometer fields and fields on right side
for referring to monasca fields
Both of these mapping files are configurable and can be set in
ceilometer configuration file
cloud_name, cluster_name, and control plane fields
are now added as dimensions by monasca publisher when
publishing metrics to monasca api which is necessary
in multi-region deployment of notification agent.
monasca publisher does not use oslo.service LoopingCall
but instead uses futurist periodics library to enable
batching.
monasca client now pages through monasca api results
if enable_api_pagination is enabled in configuration.
This flag is disabled by default but should be enabled
if monasca api supports paging using "offsets"
parameter.
Tox testing is now targeting stable/newton branch of
ceilometer.
DocImpact
Change-Id: I83b96325cb79d82858cf529935e5d699a509f6c3
- Leverages monsaca devstack and uses new devstack plugin model
to setup ceilosca.
- Also some refactoring in directory structure
Change-Id: I097c86f92e1ec09ceeb3d0d4831ff8c51c3aa1a3
notification_workers to be configurable
using API_WORKERS to facilitate multi-
threaded consumption from oslo bus.
Change-Id: I2943eade566daf360f18c8727e8c9da6de1a1047
The pipeline yaml was overwritten with the default value. This
fix it and enable the publishers to send to Monasca.
Also when installing from within VPN the get_url in Ansible
tend to timeout, the script adds a very long timeout to eliminate
the problem.
Also there is now a check to see if the role to be removed from the
monasca-vagrant was alredy removed, in that case it will not try
again. This makes the ceilosca.sh runneable several times without
the need of removing the monasca-vagrant folder. Docs updated.
Change-Id: If09cfc2e1c1a485b1794372f272f86b47ef52079
These scripts allow installtion of ceilosca on a local machine.
- Sets up devstack
- Sets up ceilosca, modifies config and copies files
- Sets up monasca on the same local box
Necessary information is in deployer/README.md
Change-Id: I2da63ee7075cee5401594408d44dd8f5881d9fe6
API unit tests are enabled by copying the
ceilometer config files in venv and using
test instance of Stevedore which allows
control over building extensions using custom
entry points.
Change-Id: I601c301d7e0353392498b374a8d6e4741487dac7
Martin Chacon Piza