...
Log in to the monitoring server
Edit the Cassandra configuration file at:
Code Block /etc/cassandra/conf/cassandra.yaml
Check the seeds value, which should be the IP of the monitoring VM (or the master VM in the cluster)
Code Block seeds: x.x.x.x
Edit the KairosDB properties file at:
Code Block /opt/kairosdb/conf/kairosdb.properties
Remove the this property
Code Block kairosdb.datastore.cassandra.host_list
Add this property and set the value as the IP address of the monitoring server, without the port. Note the
cql_
in the name. For example.Code Block kairosdb.datastore.cassandra.cql_host_list=10.60.10.102
Edit the watchtower properties configuration files at:
Code Block /etc/abiquo/watchtower/delorean.conf /etc/abiquo/watchtower/emmett.conf
Set the URL of the mysql server connection (as on the API server) with the IP address of the watchtower server
Set the database credentials as for the Abiquo server
Edit the watchtower properties files at:
Code Block /etc/abiquo/watchtower/delorean.
Restart the server
Stop the following services:
cassandra
and check that it is really dedkairosdb
abiquo-emmett
abiquo-delorean
Add the port of the RabbitMQ connection to the datanode services server address
Code Block abiquo.rabbitmq.addresses = 10.60.10.102:5672
Check the status of the monitoring services
Code Block systemctl status abiquo-delorean.service abiquo-emmett.service kairosdb.service cassandra.service
If they are running, stop monitoring services
Code Block systemctl stop abiquo-delorean.service abiquo-emmett.service kairosdb.service cassandra.service
Check if Cassandra is really dead
Code Block ps auwx | grep cassandra
Get the process number for Cassandra (the first number in the output of the previous command), and kill it. In this example, Cassandra is process
12345
.Code Block kill -9 12345
Stop the firewalld (and allow connections as required)
Code Block systemctl stop firewalld.service
Start
cassandra
and wait 5 minutes before continuingStart
kairosdb
and wait 1 minuteStart
abiquo-emmett
andabiquo-delorean
(the order is not important here)Start
firewalld
properties
/etc/abiquo/watchtower/emmett.properties |
The monitoring cluster of one server should now be fully functioning.
...
Enable and validate monitoring
To enable monitoring:
On the Abiquo Server and the Abiquo Remote Services servers (but not the V2V server), edit the
abiquo.properties
file and check or set the following properties:abiquo.monitoring.enabled = yestrue
abiquo.watchtower.host = 10.60.10.102{$MONITORING_IP_ADDRESS}
abiquo.watchtower.port = 36638
Restart your Abiquo Tomcat serviceservices.
To validate monitoring:
This step assumes you have followed the Abiquo quick tutorial to deploy a VM in Abiquo
Create Log in to the Abiquo UI and create a new VM and edit it
Go to Monitoring and select the Fetch metrics checkbox and the metrics to display
Save the VM Have a cup of tea or coffee while you wait for the VM and deploy it
Wait for Abiquo to obtain metrics for the VM (around 5 minutes)
On the VM icon, click the graph metrics button to display your VM metrics
...