68 lines
3.5 KiB
XML
68 lines
3.5 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="s-ceilometer-agent-central">
|
|
|
|
<title>Highly available Telemetry central agent</title>
|
|
|
|
<para>Telemetry (ceilometer) is the metering and monitoring service in
|
|
OpenStack. The Central agent polls for resource utilization
|
|
statistics for resources not tied to instances or compute nodes.</para>
|
|
<note>
|
|
<para>Due to limitations of a polling model, a single instance of this agent
|
|
can be polling a given list of meters. In this setup, we install this service
|
|
on the API nodes also in the active / passive mode.</para>
|
|
</note>
|
|
<para>Making the Telemetry central agent service highly available in active / passive mode involves
|
|
managing its daemon with the Pacemaker cluster manager.</para>
|
|
<note>
|
|
<para>You will find at <link xlink:href="http://docs.openstack.org/developer/ceilometer/install/manual.html#installing-the-central-agent">this page</link>
|
|
the process to install the Telemetry central agent.</para>
|
|
</note>
|
|
<section xml:id="_add_the_telemetry_central_agent_resource_to_pacemaker">
|
|
|
|
<title>Add the Telemetry central agent resource to Pacemaker</title>
|
|
|
|
<para>First of all, you need to download the resource agent to your system:</para>
|
|
<screen><prompt>#</prompt> <userinput>cd /usr/lib/ocf/resource.d/openstack</userinput>
|
|
<prompt>#</prompt> <userinput>wget https://raw.github.com/madkiss/openstack-resource-agents/master/ocf/ceilometer-agent-central</userinput>
|
|
<prompt>#</prompt> <userinput>chmod a+rx *</userinput></screen>
|
|
<para>You may then proceed with adding the Pacemaker configuration for
|
|
the Telemetry central agent resource. Connect to the Pacemaker cluster with <literal>crm
|
|
configure</literal>, and add the following cluster resources:</para>
|
|
<programlisting>primitive p_ceilometer-agent-central ocf:openstack:ceilometer-agent-central \
|
|
params config="/etc/ceilometer/ceilometer.conf" \
|
|
op monitor interval="30s" timeout="30s"</programlisting>
|
|
<para>This configuration creates</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para><literal>p_ceilometer-agent-central</literal>, a resource for manage Ceilometer Central Agent service
|
|
</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para><literal>crm configure</literal> supports batch input, so you may copy and paste the
|
|
above into your live pacemaker configuration, and then make changes as
|
|
required.</para>
|
|
<para>Once completed, commit your configuration changes by entering <literal>commit</literal>
|
|
from the <literal>crm configure</literal> menu. Pacemaker will then start the Ceilometer Central Agent
|
|
service, and its dependent resources, on one of your nodes.</para>
|
|
</section>
|
|
<section xml:id="_configure_telemetry_central_agent_service">
|
|
|
|
<title>Configure Telemetry central agent service</title>
|
|
|
|
<para>Edit <filename>/etc/ceilometer/ceilometer.conf</filename>:</para>
|
|
<programlisting language="ini"># We use API VIP for Identity Service connection:
|
|
os_auth_url=http://192.168.42.103:5000/v2.0
|
|
|
|
# We send notifications to High Available RabbitMQ:
|
|
notifier_strategy = rabbit
|
|
rabbit_host = 192.168.42.102
|
|
|
|
[database]
|
|
# We have to use MySQL connection to store data:
|
|
sql_connection=mysql://ceilometer:password@192.168.42.101/ceilometer</programlisting>
|
|
</section>
|
|
</section>
|