openstack/deb-ceilometer
Code Issues Proposed changes

Doc improvements

Browse Source 
Improve dbreco.rst based on suggestions from eglynn
Add remark about availability of compute meters in measurements.rst

Change-Id: I42cc3fe27cd9dab97c6c2353326c69577eb0f7cd
This commit is contained in:
Nick Barcet 2013-04-30 17:30:04 +02:00
parent cb7362ed04
commit f90b36d745
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/install/dbreco.rst
View File

@ -21,20 +21,20 @@ Selecting a database backend for Ceilometer should not be done lightly for
numerous reasons:
1. Not all backend drivers are equally implemented and tested. To help you
make your choice, the below indications will give you some idea of the
make your choice, the table below will give you some idea of the
status of each of the drivers available in trunk. Note that we do welcome
patches to improve completeness and quality of drivers.
2. It may not be a good idea to use the same host as another database as
Ceilometer can generate a LOT OF WRITES. For this reason it is generally
recommended, if the deployement is targeting going into production, to use
recommended, if the deployment is targeting going into production, to use
a dedicated host, or at least a VM which will be migratable to another
physical host if needed. The following spreadsheet can help you get an
idea of the volumes that ceilometer can generate:
`Google spreadsheet <https://docs.google.com/a/enovance.com/spreadsheet/ccc?key=0AtziNGvs-uPudDhRbEJJOHFXV3d0ZGc1WE9NLTVPX0E#gid=0>`_
3. If you are relying on this backend to bill customers, you will note that
its reliability is very much linked to your capacity to generate revenue,
your capacity to generate revenue is very much linked to its reliability,
which seems to be a factor dear to many managers.
The following is a table indicating the status of each database drivers:

5
doc/source/measurements.rst
View File

@ -85,6 +85,11 @@ network.outgoing.packets Cumulative packets iface ID pollster number o
======================== ========== ======== ======== ============ =======================================================
At present, most of the Nova meters will only work with libvirt front-end
hypervisors while test coverage was mostly done based on KVM. Contributors
are welcome to implement other virtualization backends’ meters or complete
the existing ones.
Network (Quantum)
=================