openstack/ceilometer
Code Issues Proposed changes

doc cleanup

Browse Source 
- drop ceilometer storage references
- highlight publishers
- remove old historical references

Change-Id: I1624831ba269a73ce20516abdcf6e34bad44ee35
This commit is contained in:
gord chung 2016-11-24 16:37:39 -05:00
parent 852e4b0397
commit f7b7494f83
2 changed files with 7 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/source/configuration.rst
View File

@ -201,6 +201,9 @@ the number of processing queues, at the very least, match the number of agents.
previously created queues may no longer be assigned to active agents. It previously created queues may no longer be assigned to active agents. It
is only recommended that you **increase** processing queues. is only recommended that you **increase** processing queues.
.. _pipeline-publishers:
Publishers Publishers
~~~~~~~~~~ ~~~~~~~~~~

18
doc/source/overview.rst
View File

@ -14,10 +14,9 @@ label as "metering".
As the project started to come to life, collecting an As the project started to come to life, collecting an
`increasing number of meters`_ across multiple projects, the OpenStack `increasing number of meters`_ across multiple projects, the OpenStack
community started to realize that a secondary goal could be added to community started to realize that a secondary goal could be added to
Ceilometer: become a standard way to collect meter, regardless of the Ceilometer: become a standard way to meter, regardless of the
purpose of the collection. For example, Ceilometer can now publish information purpose of the collection. This data can then be pushed to any set of targets
for monitoring, debugging and graphing tools in addition or in parallel to the using provided publishers mentioned in :ref:`pipeline-publishers` section.
metering backend. We labelled this effort as "multi-publisher".
.. _increasing number of meters: http://docs.openstack.org/developer/ceilometer/measurements.html .. _increasing number of meters: http://docs.openstack.org/developer/ceilometer/measurements.html
@ -37,13 +36,4 @@ as the variety of possibilities seemed too large for the project to ever
deliver a solution that would fit everyone's needs, from private to public deliver a solution that would fit everyone's needs, from private to public
clouds. This means that if you are looking at this project to solve your clouds. This means that if you are looking at this project to solve your
billing needs, this is the right way to go, but certainly not the end of the billing needs, this is the right way to go, but certainly not the end of the
road for you. Once Ceilometer is in place on your OpenStack deployment, you road for you.
will still have several things to do before you can produce a bill for your
customers. One of your first task could be: finding the right queries within the
Ceilometer API to extract the information you need for your very own rating
engine.
.. seealso::
* http://wiki.openstack.org/EfficientMetering/ArchitectureProposalV1
* http://wiki.openstack.org/EfficientMetering#Architecture