openstack-manuals/doc/common/section_getstart_telemetry.xml
Chandan kumar 3138f6fc0a Rename Metering to Telemetry in common guide.
backport: havana

Renamed section_getstart_metering.xml to section_getstart_telemetry.xml

Change-Id: I583524b7e5cbea48579482cca02753166c186622
2013-11-29 14:27:24 +05:30

87 lines
3.7 KiB
XML

<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="metering-service">
<title>The Telemetry Service</title>
<para>The OpenStack Telemetry service:</para>
<para>
<itemizedlist>
<listitem>
<para>Efficiently collects the metering data about the CPU
and network costs.</para>
</listitem>
<listitem>
<para>Collects data by monitoring notifications sent from
services or by polling the infrastructure.</para>
</listitem>
<listitem>
<para>Configures the type of collected data to meet
various operating requirements. Accessing and inserting the
metering data through the REST API.</para>
</listitem>
<listitem>
<para>Expands the framework to collect custom usage data
by additional plug-ins.</para>
</listitem>
<listitem>
<para>Produces signed metering messages that cannot be
repudiated.</para>
</listitem>
</itemizedlist>
</para>
<para>The system consists of the following basic
components:</para>
<itemizedlist>
<listitem>
<para>A compute agent (<systemitem class="service"
>ceilometer-agent-compute</systemitem>). Runs on each
compute node and polls
for resource utilization statistics. There may be other
types of agents in the future, but for now we will focus
on creating the compute agent.</para>
</listitem>
<listitem>
<para>A central agent (<systemitem class="service"
>ceilometer-agent-central</systemitem>). Runs on a central
management server
to poll for resource utilization statistics for resources
not tied to instances or compute nodes.</para>
</listitem>
<listitem>
<para>A collector (<systemitem class="service"
>ceilometer-collector</systemitem>). Runs on one or more
central management
servers to monitor the message queues (for notifications
and for metering data coming from the agent). Notification
messages are processed and turned into metering messages
and sent back out onto the message bus using the
appropriate topic. Telemetry messages are written to the
data store without modification.</para>
</listitem>
<listitem>
<para>An alarm notifier (<systemitem class="service"
>ceilometer-alarm-notifier</systemitem>). Runs on one or more
central management servers to allow settting alarms based on
threshold evaluation for a collection of samples.
</para>
</listitem>
<listitem>
<para>A data store. A database capable of handling
concurrent writes (from one or more collector instances)
and reads (from the API server).</para>
</listitem>
<listitem>
<para>An API server (<systemitem class="service"
>ceilometer-api</systemitem>). Runs on one or more central
management
servers to provide access to the data from the data store.
These services communicate using the standard OpenStack
messaging bus. Only the collector and API server have
access to the data store.</para>
</listitem>
</itemizedlist>
<para>These services communicate by using the standard OpenStack
messaging bus. Only the collector and API server have access
to the data store.</para>
</section>