The metadata.instance_type from polling is set to flavor id, but from
notifications, it is set to flavor name.
Change-Id: I4f260e5c7e29fa7bf890930abc8be4ec5b611554
Closes-Bug: 1489132
The ceilometer audit events stored at the ceilometer database
currently don't have user_id/project_id associated with them
even though this information is available as part of the event
message payload. The user_id and project_id information has to
be stored as traits so that there's user/project context for each
event and these traits are required to apply RBAC-based rules
and filters on events. For eg., presence of these traits enable
db queries - like get all events for a project/user against events.
The audit event definition in the events yaml file already stores
payload.initiator.id as initiator_id but the initiator_id trait
is not a common trait across all events and thus this trait cannot
be used to apply RBAC filter against events.This changeset will
thus add user_id and project_id traits to the audit events namely
*.http.* and add useri_id and project_id as default traits for all
events.
DocImpact
Change-Id: If4034342c4e60d519f0ec96ae8895dcf78f8ad3b
blueprint: events-rbac
There is an inapt spelling in the file called
ceilometer/doc/source/webapi/v2.rst.
line194:...different meaning in Mongo DB and...
line198:...the Mongo DB will return every....
line199:See more in the Mongod DB doc.
I think "Mongo DB" and "Mongod DB" are supposed to
spelled as "MongoDB".
Change-Id: Icb72e5e5eb099a839c4ef5aba292a42976144428
Closes-Bug: #1488775
Otherwise other plugins which depend on ceilometer and want to set
configuration items may have issues with the configuration directory not
being there.
Change-Id: Id8d10c9fcdd85e2840a74dcff5245b6f44f7424b
this patch allows us to define timstamp field. the default remains
oslo.messaging timestamp located at message['timestamp']
Change-Id: I27768b22bcfd9744b3542f171ebea5c63423496d
Implements: blueprint declarative-notifications
There is a incorrect spelling of a word in thefile called
ceilometer/doc/source/releasenotes/folsom.rst(line26).
It is curently tested to work with OpenStack 2012.2 Folsom.
I think the word "curently " should be spelled as "currently".
Change-Id: I39f413e2fb6602cab828c87779826654296768f2
Closes-Bug: #1488766
This change:
* we can downscale the stack.
* use two vm instead of three to reduce the test duration
Related-bug: #1479429
Change-Id: Ifea9869cd98654d168eb8e95c6e84d3a80bc32cc
All these bugs are now fixed in wsme 0.8.0
Closes-bug: #1424642
Closes-bug: #1423634
Closes-bug: #1419110
Closes-bug: #1428185
Closes-bug: #1428628
Closes-bug: #1428658
Closes-bug: #1428624
Change-Id: Iea8507ebc54f42786a44bfcd96246b88dd998bf0
Use dummy config file so that test depends on default config opts
instead of system config file.
Change-Id: I4ffbd389f80bbdb6076cdd99d3b25ffb4a26f32e
Closes-Bug: #1482695
This change use jsonpath_rw_ext instead of jsonpath_rw
It also remove the useless attributes list by a dict in the
yaml configuration.
Change-Id: I6014181d6d4d45ffa9769da9670b11d79d6910fc
In this CR functional tox jobs with "oslo_debug_helper" have
been added. Currently we can run oslo_debug_helper only for unit
tests directory.
Change-Id: Ib6b79b8af4ca9718720a789b3e0ab6b9600a4671
This change replace jsonpath_rw per jsonpath_rw_exta
for parsing meter/event definitions.
Depends-On: I4ebf773fd8e01185d3d1946c971d98f5c15e610a
Change-Id: I2e561e7f8a1c73b1eea561614c379d5ea207a363
The loading of the jsonpath_rw parsers is expensive.
This change created them only once at startup.
Change-Id: Ie96199f0b28537a1a9fd56432bda97b97ccecee4
This change waits
* for the update of heat stack status
* less time that the scale up occur
* a bit that gnocchi measures are ingested
Change-Id: Ic347e9eda88a251859b482c90325dfb374d88cf8
This change uses 'gabbi-run -x' instead of 'testr'
to stop at the first errors.
We loose the testr report, but currentlty we have
only one scenario, this is not a big deal.
Change-Id: I9ca50592e959fec4669bef3d8e645268d2d3c3d5
Several compute pollsters will record the whole instance info in log when
polling resources usage, it is redundant and may boom the log messages.
Closes-Bug: #1487261
Change-Id: I308254eb1e63d1215c1c053aaf88093aa937df0b