Bug fixing

Bug fixing related to Openstack install and treatment of errors.

Openstack service name change

Changed the Openstack service name

QCG version fix

Fix QCG probe version to 1.0

QCG probe availability

There's a new Zabbix probe to monitor the QCG service

New release of the Mesos and OpenStack probe

OpenStack probe

• Updated to version 1.4
• Updated to provide new convention of groups and hosts (read below)

Mesos probe

• Updated to version 1.4
• CMDB integration now is mandatory, so cmdb.location property now is mandatory in the configuration
• Updated to provide new convention of groups and hosts (read below)

Groups and hosts semantics

This release changes the semantics of groups and hosts when sending metrics to the Zabbix server:

• Since CMDB integration is now mandatory for both probes, provider name will be used as group name when sending metrics to the server
• Host name will be the service ID

So for example, if we have two providers with the following services:

• IFCA
  • "s1": Mesos
  • "s2": OpenStack1
  • "s3": OpenStack2
• INFN
  • "s1": OpenStack

In this case, this means that the provider IFCA has one Mesos cluster and two OpenStack instances running while the provider INFN has just one OpenStack installation.

In this scenario the OpenStack probe will create two groups (if they don't exist) named IFCA and INFN and it will register metrics under the host name s2 and s3 for group IFCA and s1 for group INFN, meaning that metrics under the host s2 and group IFCA will be the ones related to the OpenStack1 instance running at IFCA provider. The same applies to the OpenStack2 instance in IFCA and the only OpenStack instance at INFN (in this case, the group would be INFN instead of IFCA).

The Mesos probe will do the same but given that there's only one Mesos cluster in IFCA it will create (if it doesn't exist) a group IFCA and a host with name s1 to send its metrics.

New release of the Mesos probe

• CMDB integration. If a CMDB location is passed, there's no need to provide a Mesos master URL
• IAM integration.
• Configuration folder can be specified with -l parameter but it defaults to /etc/zabbix
• Docker option added
• Category and group are configurable and group now defaults to Cloud_Providers
• Updated dependencies

Release 2 Update 3

• IAM integration of OCCI probe
• Native OpenStack probe
• IM probe

Mesos probes

Added Mesos cluster probes which includes probes for Mesos, Marathon and Chronos

Release 1 Update 2

The Zabbix probes have been updated in order to solve a couple of bugs detected and to start adding a new feature:

• Bug fix related to retrieving the config file info when the file is not available (#6)
• Bug fix related to accessing to the Zabbix wrapper API, when creating new hosts (#10)
• Start to add IAM support for authentication in the OCCI probe (not completed yet)

First Zabbix Probes Release

First release of the Zabbix Wrapper, as well as the OCCI and Heapster probes for Zabbix.