The documentation is outdated in regard on how to configure the
notification driver. This patch fixes that by using the `messsagingv2'
driver.
Change-Id: Ifa36a7a8b958095281493542dd623fa59eb2e2c6
We have deprecated the agents for a while now in favor of the
ceilometer-polling tool, let's update the doc for good and remove them.
Depends-On: I4a2a982d4153a31971a5f1a1b504b96ce29236f9
Change-Id: I7447ba4f408c95b0acf1b809504ce16fff1c6e21
the db2 nosql product is not in development anymore as IBM has moved
on to an alternate solution. the existing driver code is untested
in the community and IBM products are moving off of it. this patch
marks db2 nosql driver for deprecation.
Closes-Bug: #1491819
Change-Id: Ic4e906615931143744f25d70935bdb8138a6b93a
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
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 commit integrates functionality from the `openstack.common.report`
module into Ceilometer. This enables Ceilometer services to receive
SIGUSR1 and print a Guru Meditation Report to stderr or file.
The required modules were added to 'openstack-common.conf' as well.
Change-Id: Ic59c08a610dff7140f14304a60f1c3297d190239
Implements: blueprint guru-meditation-report
This feature has implemented a different mechanism when posting samples
via API, the related configuration and API usage (a bit different than
before) should be described in doc.
Partially implements: blueprint api-no-pipeline
Change-Id: I8e29aab749aba6754b8dca4356bc0e44c673b9a7
As discussed in the Liberty Design Summit "Moving apps to Python 3"
cross-project workshop, the way forward in the near future is to
switch to the pure-python PyMySQL library as a default.
https://etherpad.openstack.org/p/liberty-cross-project-python3
Change-Id: I058419b25f55dcfd93af522aa1f5f61b8f06407e
This updates the mod_wsgi configuration and installation information
to be more in line with current usage. It also makes the
recommendation to use mod_wsgi more strongly than has been made in
the past. In general we don't want people to be running
ceilometer-api at all, but it is good for them to have the option.
Also an effort has been made to clarify the difference between rpm
and deb installations of Apache.
DocImpact
Change-Id: I11f92d91f4bdea884c266b91b52f9d012abd33b9
Partially-Implements: blueprint remove-web-eventlet
corrected typo “sripts” should be scripts
removed uppercase Ceilometer - per doc conventions
corrected capitalization of titles
Change-Id: Id2b190e68b6f6bcebbea9f1d15b577b2c1c53413
corrected spelling error - deployement
should actually be deployment
also fixed title capitalization to comply
with doc standards
Change-Id: Id5573c8d8dab1c5c9638b1d36ac223beb4e479cc
So that the openstack manuals are consistent and use the same (right)
term, this replaces the term 'metrics' with 'meters' in the help for
the config and develop docs.
DocImpact
Closes-bug: #1436371
Change-Id: Iadc81a936f75dbe619130b3434188f564b67efd5
During getting through the "System Architecture" documentation I've hit
some cosmetic issues which would be nice to have in our codebase.
Change-Id: I55179d91c95e215f7b4b05b9a19245faa42f0661
Since https://review.openstack.org/#/c/163462/ and
https://review.openstack.org/#/c/162649/4 in gnocchi, all kind of aggregations
have been moved in the same URI namespace (/v1/aggregation/...)
and we can use complex query to make aggregation across multiples metrics.
This change sync the ceilometer alarm API and Rules to match these
changes.
Change-Id: I015af585595e6880b527161fe5c8b34eeb7bfe29
Wikipedia's list of common misspellings [1] has a machine-readable
version. This patch fixes those misspellings mentioned in the list
which don't have multiple right variants (as e.g. "accension", which can
be both "accession" and "ascension"), such misspellings are left
untouched. The list of changes was manually re-checked for false
positives.
[1] https://en.wikipedia.org/wiki/Wikipedia:Lists_of_common_misspellings/For_machines
Change-Id: I9029d207b9e8f356fe71c3f20a74011c4d143bb5
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Update the 'measurements' reference in samples.py to refer to
the section that describes the supported sample types.
Change-Id: I75913cdac6780d2cb6498999830ebb3734a8457e
I've got some more substantive suggestions coming but I wanted to
get these minor tweaks out of the way first
Change-Id: I496e5ffcb2ae9ae4d13a06c78a24dbc64cbb9711
- remove contributing folder contents
- move plugins into first level
- keep testing info from 'working with source' and move to first
level
- keep a generic contributing page to point to gerrit workflow and
standard links (git repo, launchpad, etc...)
- delete everything else
- split TOC into:
- overview - general stuff
- developer - dev related stuff
- appendix - random stuff
Change-Id: I8c460a655427141eb8bb8db9d4c2ecd253eb6cb1
a large chunk of meters don't measure anything and are really
healthcheck events. these should be stored as events and not
samples. this patch adds an option to disable false meters and
warn if not disabled.
Change-Id: I654f657dd36967ad3ec99bbe06209e7745432e12