The Technology Chronicle

Recently a Ceilometer proxy for Zabbix was released by OneSource. This proxy will pull all the instance information from OpenStack and populate it in Zabbix The source code can be downloaded from here: https://github.com/OneSourceConsult/ZabbixCeilometer-Proxy The basic prerequisites for the server where the proxy is running is Python and Pika library. Also there should be network connectivity from the proxy machine to your OpenStack installation.

Zabbix can be a tough cookie to crack!! And if you are planning to monitor Openstack using Zabbix, there is lot of additional work to be done .More so, if you want to go the agentless way, ie using SNMP So, here we go.I am using Ubuntu 12.04 OS, both for my Zabbix server as well as openstack nodes First you need to install the following packages using apt-get in the machine being monitored ie the openstack node

1. List the keystone tenants and search for the required tenant keystone tenant-list |grep <tenantname>  Note the id of the tenant being displayed. You need to use this id in the next command 2. Get quota details of the tenant using the following command nova-manage project quota <tenantid>

Issue:  All instances in openstack will be in paused node. You will not be able to create new instances or switch on any of the paused instances Reason:  Most often the reason will be lack of disk space in your compute node. By default the instances are created in the /var/lib/nova/instances folder of the compute node. This location is defined by the parameter "instances_path" in nova.conf of the  compute node. If your "/" partition is running out of disk space, then you cannot perform any instance related operations Solution:  Change the "instances_path" location to a different location. Ideally you could attach an additional disk and mount it to a directory and update the directory path in the "instance_path" variable.   Problem arises when you already have a number of instances  in the previous folder. You should move them over to the new location.  Also you should set the group and ownership of the new instances folder to &quo

In some scenarios, the openstack neutron-agent status will show as xxx even though you could see he neutron agents services are up and running in the network and compute nodes. Also you could see a fluctuation in the agent status if you try the agent-list command repeatedly.  Confusing, right? Actually  the problem is not in the actual agent status, but with two default configurations in neutron.conf ie agent_down_time and report_interval . It is the interval during which neutron will check the agent status. There is a bug reported against this issue https://bugs.launchpad.net/neutron/+bug/1293083 As per the details in the bug " report_interval" is how often an agent sends out a heartbeat to the service. The Neutron service responds to these 'report_state' RPC messages by updating the agent's heartbeat DB record. The last heartbeat is then compared to the configured agent_down_time to determine if the agent is up or down" The neutron agent-list comm