openstack
/
ceilometer
Code Issues Proposed changes

Fix docs build error 

Change-Id: I25558ff48b6236773f765aad8d1fc150f7011aef
This commit is contained in:
zhurong 2020-04-11 00:07:40 -07:00
parent 75b9d4e914
commit 4fafac8404
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/contributor/architecture.rst
View File

@ -59,9 +59,9 @@ How is data collected?
The Ceilometer project created 2 methods to collect data:
1. :term:`Notification agent` which takes messages generated on the
1. :term:`notification agent` which takes messages generated on the
notification bus and transforms them into Ceilometer samples or events.
2. :term:`Polling agent`, will poll some API or other tool to collect
2. :term:`polling agent`, will poll some API or other tool to collect
information at a regular interval. The polling approach may impose
significant on the API services so should only be used on optimised
endpoints.

6
doc/source/contributor/overview.rst
View File

@ -26,9 +26,9 @@ Metering
If you divide a billing process into a 3 step process, as is commonly done in
the telco industry, the steps are:
1. :term:`Metering`
2. :term:`Rating`
3. :term:`Billing`
1. :term:`metering`
2. :term:`rating`
3. :term:`billing`
Ceilometer's initial goal was, and still is, strictly limited to step
one. This is a choice made from the beginning not to go into rating or billing,